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.
The whole file is a bare array of architecture records. The fields of one record are below.
architecture recordThe fields of a single architecture — one per authored file.
architectures.schema.json — change the schema, and this page changes.| Field | Type | Description |
|---|---|---|
key required
|
string | Stable selector — the value solutions reference via solution.architecture (a `key`, not an `id`). |
name required
|
string | Display name of the position. |
longName
|
string | Optional longer/qualified name. |
summary
|
string | What this position is — the structural stance in one paragraph. |
optimizes
|
string | What the position optimises for — its strength. |
tradeoff
|
string | What it gives up — its cost, one line. |
anchor
|
boolean | Marks a comparison-anchor position (a ceiling/contrast exhibit, not a serious candidate). |
status
|
string | Optional board status for the position. |
clientCopy
|
object | Client-facing register (blurb/what/wins/gives-up, …) — permissive; the shell renders it as the public copy. |
verdict
|
object | The authored verdict on the position — as-of marker plus the evidence it rests on. |
asOf
|
string | Round marker the verdict was last set (e.g. 'R4'). |
basis
|
array<string> | Finding ids the verdict rests on (resolved against research-index in the semantic tier). |