Problem
Several architecture/tooling claims are stronger or less honest than the code:
scripts/layering/check.ts says the target DAG is complete, but only the
ranked target spine is checked for back-edges; root and peripheral zones are
intentionally unranked.
CONTEXT.md describes a broader folder DAG as enforced by that script.
- The build reports
INEFFECTIVE_DYNAMIC_IMPORT for app-log.ts, because the
same module is statically imported elsewhere.
- ADR 0009 still lists shipped tvOS/capability/watchOS work as deferred.
- Completed experiment/tracker records need reconciliation.
Scope
- Make the layering model and documentation state exactly what is enforced:
global production static value-cycle rejection, R1-R3, and an explicit ranked
target spine. Classify root/peripheral zones deliberately rather than implying
they are ranked.
- Add tests that prevent future scope/claim drift. Do not create a broad
refactor merely to rank every folder.
- Remove the ineffective app-log dynamic import warning structurally; preserve
behavior and cold-start characteristics rather than adding a large comment.
- Update ADR 0009 and durable architecture/experiment wording to distinguish
shipped work from intentional deferrals.
- Reconcile completed tracker references; public Apple wire collapse remains
deferred.
Owning files
scripts/layering/model.ts
scripts/layering/check.ts
scripts/layering/model.test.ts
CONTEXT.md
src/daemon/request-platform-providers.ts
src/daemon/app-log.ts
docs/adr/0009-apple-platform-consolidation.md
docs/agents/contract-projection-output-economy-spike.md
Acceptance criteria
- Layering output/docs no longer claim broader back-edge coverage than exists.
- Root/peripheral treatment is explicit and regression-tested.
- Zero static production value cycles and zero ranked-spine back-edges remain
enforced.
pnpm build has no INEFFECTIVE_DYNAMIC_IMPORT warning for app-log.ts.
- ADR 0009 keeps only genuinely deferred items deferred.
- No new code generation, schema DSL, blanket LOC gate, or mass
utils move.
pnpm check:affected --base origin/main --run passes.
Problem
Several architecture/tooling claims are stronger or less honest than the code:
scripts/layering/check.tssays the target DAG is complete, but only theranked target spine is checked for back-edges; root and peripheral zones are
intentionally unranked.
CONTEXT.mddescribes a broader folder DAG as enforced by that script.INEFFECTIVE_DYNAMIC_IMPORTforapp-log.ts, because thesame module is statically imported elsewhere.
Scope
global production static value-cycle rejection, R1-R3, and an explicit ranked
target spine. Classify root/peripheral zones deliberately rather than implying
they are ranked.
refactor merely to rank every folder.
behavior and cold-start characteristics rather than adding a large comment.
shipped work from intentional deferrals.
deferred.
Owning files
scripts/layering/model.tsscripts/layering/check.tsscripts/layering/model.test.tsCONTEXT.mdsrc/daemon/request-platform-providers.tssrc/daemon/app-log.tsdocs/adr/0009-apple-platform-consolidation.mddocs/agents/contract-projection-output-economy-spike.mdAcceptance criteria
enforced.
pnpm buildhas noINEFFECTIVE_DYNAMIC_IMPORTwarning forapp-log.ts.utilsmove.pnpm check:affected --base origin/main --runpasses.