TSZ Architecture
Use for ownership-boundary work. Default direction: solver-first semantics, thin
checker, syntax parser, symbol/flow binder, output-only emitter.
Rules
- Read
AGENTS.md and docs/plan/ROADMAP.md for conformance, emit,
performance, architecture, LSP/WASM, Sound Mode, or DRY cleanup work.
- Inspect overlapping PRs/issues.
- State:
When <structural condition>, tsc does X; tsz does X through <owner>.
- No fixture paths, user names, source snippets, rendered strings, or single
test names as decision inputs.
- Prefer one query/boundary helper over local checker branches.
Owners
- Scanner: tokens and interning.
- Parser: syntax-only AST.
- Binder: symbols, scopes, hoisting, flow graph.
- Solver: relations, evaluation, inference, instantiation, operations,
narrowing, semantic caches.
- Checker: orchestration, diagnostics, source spans.
- Emitter: JS/DTS output and transform scheduling.
- LSP/WASM/CLI: API consumers.
Boundary Workflow
- Classify as
WHAT (solver/query boundary) or WHERE (checker location/
diagnostic orchestration).
- Search existing boundaries:
rg "struct .*Request|RelationRequest|query_boundaries|TypeData" crates/tsz-checker/src crates/tsz-solver/src
- Put checker-facing semantic adapters under
crates/tsz-checker/src/query_boundaries/.
- Avoid new checker
TypeKey matching, direct CompatChecker, raw interning,
or type-shape recursion.
- Add owning-crate tests and adjacent cases varying names/wrappers.
Guards
python3 scripts/arch/arch_guard.py
scripts/arch/check-checker-boundaries.sh
python3 scripts/arch/test_arch_guard.py
Use targeted cargo nextest run; wrap heavy runs with scripts/safe-run.sh.
PR notes: structural rule, owner layer, adjacent matrix, guard/tests, temporary
debt/removal condition.
1---2name: tsz-architecture3description: Preserve TSZ architecture boundaries while changing checker, solver, binder, emitter, LSP, WASM, or CLI code. Use when planning semantic fixes, moving logic across query boundaries, handling architecture guard failures, ratcheting boundary debt, or reviewing changes for solver-first and no hardcoding rules.4---56# TSZ Architecture78Use for ownership-boundary work. Default direction: solver-first semantics, thin9checker, syntax parser, symbol/flow binder, output-only emitter.1011## Rules1213- Read `AGENTS.md` and `docs/plan/ROADMAP.md` for conformance, emit,14 performance, architecture, LSP/WASM, Sound Mode, or DRY cleanup work.15- Inspect overlapping PRs/issues.16- State: `When <structural condition>, tsc does X; tsz does X through <owner>.`17- No fixture paths, user names, source snippets, rendered strings, or single18 test names as decision inputs.19- Prefer one query/boundary helper over local checker branches.2021## Owners2223- Scanner: tokens and interning.24- Parser: syntax-only AST.25- Binder: symbols, scopes, hoisting, flow graph.26- Solver: relations, evaluation, inference, instantiation, operations,27 narrowing, semantic caches.28- Checker: orchestration, diagnostics, source spans.29- Emitter: JS/DTS output and transform scheduling.30- LSP/WASM/CLI: API consumers.3132## Boundary Workflow33341. Classify as `WHAT` (solver/query boundary) or `WHERE` (checker location/35 diagnostic orchestration).362. Search existing boundaries:37 `rg "struct .*Request|RelationRequest|query_boundaries|TypeData" crates/tsz-checker/src crates/tsz-solver/src`383. Put checker-facing semantic adapters under39 `crates/tsz-checker/src/query_boundaries/`.404. Avoid new checker `TypeKey` matching, direct `CompatChecker`, raw interning,41 or type-shape recursion.425. Add owning-crate tests and adjacent cases varying names/wrappers.4344## Guards4546```bash47python3 scripts/arch/arch_guard.py48scripts/arch/check-checker-boundaries.sh49python3 scripts/arch/test_arch_guard.py50```5152Use targeted `cargo nextest run`; wrap heavy runs with `scripts/safe-run.sh`.5354PR notes: structural rule, owner layer, adjacent matrix, guard/tests, temporary55debt/removal condition.
tsz-org