solutions file

AssembledAssembled output

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.

The assembled output — this is the file the cockpit reads. You don't edit it; you edit the authored source, and the build produces this (node _methodology/contract/assemble.mjs assemble data).

Assembled — The Phase-4 candidate compositions. Authored as one YAML shard per solution; assembled into the served JSON at build time. 3 fields.

File shape

The whole file is one of these two shapes — pick whichever the instance ships:

A bare array of solution records.

An object wrapping the records:

Field	Type	Description
`_comment`	string	Free-text authoring note; ignored by the kernel.
`_comment_optional`	string	Secondary free-text authoring note; ignored by the kernel.
`system` required	array<solution>	The solution records, when the file wraps them under `system` rather than shipping a bare array.

Each entry is one solution record — its full field schema is on the authored source page.

← Back to the reference