# Deep Code Archaeology (Katra3D §35)
Before replacing any significant path, the following is inspected and the
findings recorded in `docs/archaeology/`:
1. current Wine code for the surface;
2. Proton-specific integration;
3. vkd3d-proton;
4. relevant Vulkan behavior;
5. Linux kernel facilities;
6. Windows API documentation;
7. observable native behavior (where legal and practical);
8. commit history;
9. relevant bug reports;
10. historical workarounds;
11. the **residual behavior relied upon by games** — which becomes a test.
Code and runtime evidence take precedence over comments and architecture
documents.
## Workaround protocol (§3.1)
When an upstream workaround is encountered:
1. determine the observable behavior it preserves;
2. create a test for that behavior (a court);
3. preserve the residual;
4. implement it cleanly within Katra3D — or keep the upstream
implementation as a fallback if replacing it earns nothing.
## Status
`docs/archaeology/` currently contains the process definition and the
pending-work list. As each hot path is targeted (starting with the Phase 1
Pareto), its archaeology notes land here before any code is written.