Spec Tech

You are authoring the technical spec — the how, downstream of the product spec (/spec-product) and upstream of per-slice design (/design). The entity engine (TOML+MD tiers, relations, show command) is documented in [[mem.concept.doctrine.entity-engine]].

Structural. Doctrine manages specs as first-class entities — a tech spec is the same three coordinated writes as a product spec: scaffold with spec new (subtype/title/slug only), hand-edit the spine and flat fields into spec-NNN.toml, then spec req add its requirements. Use show to read the reassembled whole, validate for FK integrity, list for the corpus (flags in --help; verb model in using-doctrine.md). Identity, the relational spine, and flat fields (incl. c4_level, [[source]] anchors) live in spec-NNN.toml, the narrative in spec-NNN.md; requirements are peer entities (REQ-NNN) membered via members.toml; tech-only spec→spec edges are written with doctrine spec interactions add/remove (not hand-authored). There is no CLI flag for the spine — it is authored TOML, and spec validate is the integrity gate.