2.5 KiB
2.5 KiB
11 - Architecture Turnaround Package
Purpose
This folder is the execution-oriented continuation of the baseline note:
That baseline note answers:
- what the project is today;
- where the main architectural fragility sits;
- what direction is safe.
This package answers the next question:
- how the team should design the architectural turnaround without breaking the current exact-data baseline.
Package Contents
- 01 - project_architecture_baseline_map.md
- 02 - state_and_transition_contracts.md
- 03 - capability_contract_spec.md
- 04 - coverage_evidence_truth_gate.md
- 05 - assistantService_extraction_map.md
- 06 - phase_acceptance_matrix.md
- 07 - external_reference_appendix.md
Architectural Objects Of Planning
This package makes five objects explicit:
state modeltransition modelcapability contract modelcoverage / evidence / truth gateassistantService extraction plan
These are the objects that should now drive refactoring discussions.
How To Use The Package
Read in this order:
- baseline note in
docs/ARCH/11 - unified_project_architecture_and_reference_update_plan_2026-04-15.md 01 - project_architecture_baseline_map.md02 - state_and_transition_contracts.md03 - capability_contract_spec.md04 - coverage_evidence_truth_gate.md05 - assistantService_extraction_map.md06 - phase_acceptance_matrix.md07 - external_reference_appendix.md
Planning Rules
- Do not treat this package as a rewrite plan.
- Do not dissolve
AddressQueryServiceinto generic chat logic. - Do not move state back into transcript-only memory.
- Do not let answer wording substitute for policy/runtime fixes.
- Use scenario-based acceptance as the primary gate for all phases.
Expected Outcome
When this package is fully operational, the project should stop being described as:
- "a big custom assistant service with many heuristics"
and start being described as:
- "a stateful exact-data assistant with explicit transition contracts and isolated truth gating."