Start Phase 3
Phase 2 traced sanctions through the zero-code wrapper, so there is no common/telemetry.py yet; note that build step 1 writes it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Opus 5.5
parent
c06d6be4ce
commit
574d7f4038
@@ -2,9 +2,11 @@
|
||||
|
||||
*Part of `docs/roadmap/` — see [`intro.md`](intro.md) for platform/background context and [`summary.md`](summary.md) for how every phase fits together. Prev: [`phase-2.md`](phase-2.md) · Next: [`phase-4.md`](phase-4.md)*
|
||||
|
||||
**Status:** Not started
|
||||
**Status:** In progress
|
||||
|
||||
**Message:** Depends on Phase 2's `common/telemetry.py` bootstrap existing first.
|
||||
**Message:** Started 2026-10-12. Phase 2 got `sanctions` tracing through zero-code
|
||||
`opentelemetry-instrument`, so no `common/telemetry.py` exists yet. Build step 1
|
||||
writes that bootstrap by hand, in the code, to replace the wrapper.
|
||||
|
||||
**Time-box:** 2–3 evenings. This is the biggest phase and the heart of the task.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user