Traceability
Every reader concern mapped to the sections that answer it, every module traced to the spine, and withheld material as rows, never silence.
Overview · Traceability
What this page proves
This document is the package's completeness argument. It maps every reader concern we anticipated to the sections that answer it, maps every module unit to the architecture it realizes, and shows that every section of the spine is claimed by at least one document. Withheld material appears here as rows, not as silence: if something is held at a deeper tier, this page says so and says where it lives. The tier ladder itself is defined in the overview and architecture section 16.
Matrix one
The concerns of a technical reader assessing our engineering, each with where the package answers it.
| Concern | Where it is answered |
|---|---|
| Is the architecture sound? | Architecture sections 4 to 13; the eight diagrams; every unit's contract |
| Can the team explain why it is this way? | Decisions (all entries, including the superseded one); architecture sections 2 to 4; the two preempted objections in sections 10 and 11 |
| Is the data trustworthy? | Architecture sections 8, 9, and 12; the reports, coverage, and zoning-data-factory units; walkthrough scenarios 1 and 3; the honesty doctrine in the glossary |
| Is the agent safe? | Architecture section 10; the addi-agent-surface unit; diagrams 06 and 07; walkthrough scenario 2 |
| What happens when things fail? | Architecture section 3; walkthrough scenario 3; every unit's failing cases (the module pages); the fail-soft producer model in section 11 |
| Does it scale, and what is the plan? | Architecture sections 11 and 13; the limitations register (the storage swap and its trigger); the analysis-compute-engine unit |
| How is it built and delivered? | How We Build; architecture section 14 |
| What are the known limits? | The limitations register, each item with a plan or trigger; the failing cases in every unit (the module pages) |
| What is withheld, and where does it live? | Architecture section 16; the tier ladder in the overview; the withheld rows below |
| Withheld material | Held at |
|---|---|
| Component-level design, schemas, payloads, field-level contracts | Tier 2 |
| The configuration schema and validation rules | Tier 2 |
| The agent tool catalog and scope topology | Tier 2 |
| Security controls detail and the operational layer | Tier 2 |
| Source code; the zoning extraction specification and gate list | Tier 3 |
| Formulas, matching and adjustment mechanics, scoring internals, template defaults | Tier 3 |
| Prompt and doctrine contents served to the agent | Tier 3 |
| Identities of licensed data sources and providers | Tier 3 |
| Quantitative scale: coverage counts, volumes, throughput, cost structure | Tier 3 |
| Deployment identifiers, internal hostnames, credentials topology, personnel specifics | Excluded at every tier |
Matrix two
Each module unit, what it answers, and the architecture it realizes. Flags mark the open items a careful reader should know about; they are elaborated in the limitations register.
| Unit | Answers | Spine sections | Scenarios | Flags |
|---|---|---|---|---|
| intake-and-verification | How work enters, and why the front door asks nothing | 5, 7, 8, 9, 13 | 1 | none |
| buy-box | How fit is a stated policy, and the one automatic mover | 2, 7, 8 | 1 | learned preferences phased in from human decisions |
| pipeline-board | Where accountability lives between stages | 6, 7, 8, 13 | 1 | none |
| deal-workspace | How one deal's evidence is composed for a human | 5, 7, 8, 9 | 1, 2 | none |
| reports | Why analysis output is versioned, honest, and auditable | 3, 8, 9, 11, 12 | 1, 3 | none |
| underwriting-calculator | How numbers explain themselves and defaults stay labeled | 6, 7, 8, 9, 10 | 1 | none |
| addi-agent-surface | Why an agent with write access is safe here | 6, 7, 8, 10, 13 | 2 | autonomy deliberately budget-capped while trust accrues |
| coverage | How data gaps surface as honest states, not silence | 3, 7, 11, 12 | 3 | asset shape is deal-contingent, Tier 3 |
| entitlements-and-config | How one codebase becomes each tenant's product | 2, 5, 6, 7, 13 | 1 | none |
| signup-and-billing | How a tenant is born and how usage is billed | 5, 6, 7, 13 | none | billing internals held at Tier 3 |
| analysis-compute-engine | How an address becomes evidence, reproducibly | 3, 9, 11, 12, 15 | 1, 3 | storage swap designed, not executed; see the limitations register |
| zoning-data-factory | Why our zoning layer is an owned asset with an owned quality bar | 3, 9, 11, 12 | 1 | none |
Scenario key: 1 the property journey, 2 the agent's morning, 3 the bad day, all in the walkthroughs.
Matrix three
Every spine section, claimed by at least one document beyond the spine itself.