The field reference — generated from the contract/ schema, so the docs and the system never drift apart. 8 base schemas, 312 fields, 1 instance extension(s).
Each schema file gets its own page. Ordered by the funnel sequence — the five phases in which an engagement builds its data (requirements first, decisions last), not alphabetically.
_site/) — never hand-edited; produced from shards or a research profile.
architectures.schema.json
Authored
architectures file
The architectures (positions) — the spine of distinct structural stances a solution can fill (e.g. complete solution → in-house build). The board groups solutions by architecture via solution.architecture → architectures[].key. A bare array of architecture records. Instance extensions narrow via allOf + $ref to this $id with unevaluatedProperties:false.
12 fields →decisions.schema.json
Authored
decisions file
The decisions / values layer — the side-ledger of open forks that accrues across ALL phases (Plan 15 MR-4: decisions are not a phase). A fork narrows the live solution space; its options prune a typed reference set (Plan 15 MR-1: architectures | solutions | fillers, instance-declared). Instance extensions narrow via allOf + $ref to this $id with unevaluatedProperties:false.
59 fields →data/solutions/<key>.yaml
Authored
solutions file
Phase-4 candidate compositions — the filled, scored architectures. A solutions file is EITHER a bare array of solution objects (e.g. skischule's solutions-platform.json) OR an object wrapping them under `system` (demo/template/ehimare). Both shapes are blessed; pick whichever the instance ships. The per-solution shape is $defs/solution. Instance extensions narrow via allOf + $ref to this $id and add their own keys with unevaluatedProperties:false.
72 fields → Assembleddata/solutions.json →
fillers.schema.json
Authored
fillers file
The building blocks that fill gaps a core solution leaves — the dockable components a solution's coverage references via `part:<id>`/`aug:<id>`. Backs the 'Building blocks by job' view. Instance extensions narrow via allOf + $ref to this $id with unevaluatedProperties:false.
23 fields →research/landscape-results.json
Authored
landscape file
The raw, un-scored tool survey — every candidate seen, with its gate verdicts. Backs the Tools view; scoring happens later in solutions/matrix. Typically GENERATED from a richer research profile (not hand-maintained). Instance extensions narrow via allOf + $ref to this $id with unevaluatedProperties:false.
Source files → Generateddata/landscape.json →
data/rounds/<id>.yaml
Authored
research-index file
The append-only research ledger backing the Deep-dive → Report view — what was surveyed, round by round, plus the per-position/per-assist research state. Append-only `rounds[]` is what makes the iterative loop (Plan 15 MR-4) representable: new evidence is added, never overwritten. Instance extensions narrow via allOf + $ref to this $id with unevaluatedProperties:false.
Source files → Assembleddata/research-index.json →
Each engagement extends the base schemas with its own fields (allOf + unevaluatedProperties: false) — the fields on these pages come in addition to the respective base.