Authors move one Spec from intent to reviewed evidence

outcome

Give an agent or human one graph-first path for creating, enriching, binding, and reviewing a Spec without inventing a parallel workflow.

rule line 29 · specs/consumers/authoring-on-ramp.sdp.md:29

An author starts from the build-backlog and drift-alarm recipes, reads carrying Specs for law, and edits the canonical carrier.

rule line 30 · specs/consumers/authoring-on-ramp.sdp.md:30

Cheap capture starts with sdp new spec (or the equivalent hand-authored idea carrier) in the family found through concept search; the scaffolder emits envelope, Intent outcome, and the kind's bare typed heading, never invented content, and for constraint emits envelope, title, and Intent only with no twin section. Every later readiness edit is preceded by the promotion-preflight recipe and remains a human statement.

rule line 31 · specs/consumers/authoring-on-ramp.sdp.md:31

The skill teaches question keys and their optional fields through spec:model.open-question-keys and spec:model.open-question-fields, rule keys and an example's exercises through spec:model.rule-keys, and optional relation reasons through spec:model.relation-reasons.

rule line 32 · specs/consumers/authoring-on-ramp.sdp.md:32

The skill teaches the least design two parties need to agree: keyed Design entries for shared names and shapes, code spans for pinned declarations, rule keys for outside citations, one prose owner for why, and no derived counts, delivery state or implementation sequence authored as design.

rule.designRounds line 33 · specs/consumers/authoring-on-ramp.sdp.md:33

The skill teaches design in rounds over a design slice: what each rung's design typically settles, that a detail only the builder reads and a question only the builder answers belong to the build, and how a reviewer reads the design columns beside each rung; no check reads this guidance.

no example exercises it

rule line 34 · specs/consumers/authoring-on-ramp.sdp.md:34

The skill points behavior and example authors to spec:carrier.gherkin-authoring for the lawful Gherkin alternative and Pack authors to spec:carrier.markdown-pack-authoring for namespace routing, framing and ordered membership.

rule line 35 · specs/consumers/authoring-on-ramp.sdp.md:35

Binding is taught for code, test and oracle anchors in the constant form and the comment form, following spec:decisions.anchor-comment-form and spec:decisions.anchor-binding-grain. The constant builders are codeAnchor, specTest and specOracle; a code anchor's satisfies is optional and plural, a test anchor's verifies is non-empty and plural, and an oracle anchor has one models target. The skill teaches references as the code-to-design binding that claims no realization, and names the two silent non-binding hazards, a constant builder without a Protocol builder binding and a comment that does not open with /**.

rule line 36 · specs/consumers/authoring-on-ramp.sdp.md:36

The skill teaches the collective promise test for satisfies and the one-way meaning of references, following spec:decisions.anchor-binding-grain; every promise is realized by the satisfying units together, and each satisfying unit realizes at least one promise.

rule line 37 · specs/consumers/authoring-on-ramp.sdp.md:37

Structural binding is taught through component, uses and optional role on a code anchor, and optional layer and context on a component: anchor, in either form, following spec:decisions.architectural-annotation. The skill teaches closed graph-ID targets, at most one component per source, no implements field, cycles as data, and no conferral of intent, delivery facts or readiness by structural fields.

rule line 38 · specs/consumers/authoring-on-ramp.sdp.md:38

The executable transition is taught as parent example space, child bound point, generated contracts, the oracle bound by a specOracle anchor, and one generated-registrar activation beside the authored suite's top-level specTest anchor, with bindExample named as the low-level adapter and a mutation-probed red result required before the human states ready.

rule line 39 · specs/consumers/authoring-on-ramp.sdp.md:39

Contract-generation refusals are diagnosed through sdp build; query-time validation does not claim to report codegen findings.

rule line 40 · specs/consumers/authoring-on-ramp.sdp.md:40

Verifier-binding queries report graph-visible anchors; the specTest anchor remains the sole has-verifier source, and the graph cannot detect a generated contract or registrar that no authored suite activates.

rule line 41 · specs/consumers/authoring-on-ramp.sdp.md:41

An anchor carries identity, an optional label, its flavor's targets and optional structure, never intent; a code anchor with neither satisfies nor references is identity-only and lawful. A Markdown deliverable binds through the document-realization convention: the suite asserting the shipped document carries the code anchor, and blast radius stays coverage-unknown for the Markdown file.

rule line 42 · specs/consumers/authoring-on-ramp.sdp.md:42

Design Review supplies context for the human readiness statement without becoming a workflow gate.

13 unkeyed rules.

Verifier bindings

• test:protocol.authoring-on-ramp · skill-asset checks verify the authoring on-ramp · anchored · test anchor binding present · test/skills.test.ts:276

  External run evidence from test/skills.test.ts

  Test anchors: test:protocol.adopter-on-ramp, test:protocol.authoring-on-ramp, test:protocol.delivery-session-on-ramp, test:protocol.graph-first-planning, test:protocol.reading-on-ramp, test:protocol.studio-on-ramp, test:protocol.vault-on-ramp. Specs verified by those bindings: spec:consumers.adopter-on-ramp, spec:consumers.authoring-on-ramp, spec:consumers.delivery-session-on-ramp, spec:consumers.graph-first-planning, spec:consumers.reading-on-ramp, spec:consumers.studio-on-ramp, spec:consumers.vault-on-ramp.

  Run 1: external run evidence from vitest 4.1.10

  Build: CI 391 · Branch: cursor/media-plan-and-articles-09b1 · Commit: 076cd4f1f85640d8236e5cca1bffffa68ab79a33 · Start: 2026-10-31T15:32:20.471Z · Stop: 2026-10-31T15:34:02.073Z

  Name	Suite	Result	Duration
  discovers the design slice's summary and detail parameter	not recorded	passed	6.44 ms
  teaches the named-file exception to both carrier-watch descriptions	not recorded	passed	1.2 ms
  teaches the optional priority field in the Pack manifest envelope	not recorded	passed	0.84 ms
  teaches design rounds and curates bindings by responsibility	not recorded	passed	3 ms
  presents the Protocol engine roles and reviewed boundary as worked examples for adopters	not recorded	passed	1.27 ms
  routes the next work and reviews through roadmap and proposal recipes	not recorded	passed	3.89 ms
  keeps planning truth in graph homes and session routing advisory	Protocol skill assets	passed	1.46 ms
  rejects missing planning guidance: An open question goes	Protocol skill assets	passed	2.07 ms
  rejects missing planning guidance: A deferral is	Protocol skill assets	passed	1.1 ms
  rejects missing planning guidance: An unsettled fact	Protocol skill assets	passed	0.94 ms
  rejects missing planning guidance: A ruling that awaits	Protocol skill assets	passed	0.96 ms
  rejects missing planning guidance: A statement a test checks	Protocol skill assets	passed	0.95 ms
  rejects missing planning guidance: Derive a count	Protocol skill assets	passed	1.75 ms
  rejects missing planning guidance: Group a body of work	Protocol skill assets	passed	1.11 ms
  rejects missing planning guidance: Hold advisory priority	Protocol skill assets	passed	1.96 ms
  owns skills under .agents and exposes them to Claude through one relative symlink	Protocol skill assets	passed	0.39 ms
  ships every skill folder in the package and indexes it in the help	Protocol skill assets	passed	1.08 ms
  uses the repository's two-field single-file convention	Protocol skill assets	passed	2.36 ms
  keeps every skill graph-first and the authoring law linked to carrying Specs	Protocol skill assets	passed	3.17 ms
  names the complete closed graph schema in the shape section	Protocol skill assets	passed	1.04 ms
  routes delivery sessions through the five advisory graph shapes	Protocol skill assets	passed	0.97 ms
  documents only valid CLI verbs and keeps root-specific exclusions intact	Protocol skill assets	passed	3.67 ms
  uses the local runtime or package runner instead of a colliding global binary	Protocol skill assets	passed	1.67 ms
  contains no contradictory shortcuts for readiness or verifier realization	Protocol skill assets	passed	1.36 ms
  states no recipe-catalog size in an on-ramp	Protocol skill assets	passed	13.37 ms
  maps a task to every catalog recipe in one sheet	the graph-reading on-ramp	passed	5.28 ms
  links the Specs that own the graph contract, the claims and the sink	the graph-reading on-ramp	passed	0.74 ms
  teaches every Markdown section owner and links the carrying grammar	adopter teaching	passed	1.1 ms
  teaches open-question home	adopter rule meanings	passed	1.35 ms
  teaches blocking floor	adopter rule meanings	passed	1.06 ms
  teaches blocking deferral	adopter rule meanings	passed	0.98 ms
  teaches deferral trigger	adopter rule meanings	passed	0.85 ms
  teaches deferral precondition	adopter rule meanings	passed	0.76 ms
  teaches independent defined floor	adopter rule meanings	passed	0.96 ms
  teaches complete example children	adopter rule meanings	passed	1.06 ms
  teaches example vocabulary agreement	adopter rule meanings	passed	0.81 ms
  teaches physical entry line	adopter rule meanings	passed	0.69 ms
  teaches one leading prose owner	adopter rule meanings	passed	0.88 ms
  teaches Note is refused	adopter rule meanings	passed	1.08 ms
  teaches ready reads parent	adopter rule meanings	passed	1.08 ms
  teaches ready waits for defined parent	adopter rule meanings	passed	1.4 ms
  teaches unsettled constraint home	adopter rule meanings	passed	1.17 ms
  teaches unsettled blocking check	adopter rule meanings	passed	1.89 ms
  teaches bounded relation	adopter rule meanings	passed	1.07 ms
  teaches bounded defined allowed	adopter rule meanings	passed	1.1 ms
  teaches bounded ready waits	adopter rule meanings	passed	1.08 ms
  teaches pending decision below ready	adopter rule meanings	passed	1.03 ms
  teaches shaping relation	adopter rule meanings	passed	1.06 ms
  teaches owner states ready	adopter rule meanings	passed	1.02 ms
  teaches checked statement home	adopter rule meanings	passed	1.13 ms
  teaches checking example relation	adopter rule meanings	passed	1.12 ms
  teaches example test binding	adopter rule meanings	passed	1.08 ms
  teaches derived verifier fact	adopter rule meanings	passed	1.82 ms
  teaches verifier existence versus passing	adopter rule meanings	passed	6.32 ms
  teaches CI owns outcomes	adopter rule meanings	passed	1.42 ms
  teaches no authored checked status	adopter rule meanings	passed	7.3 ms
  teaches fresh derived counts registers scope	adopter rule meanings	passed	1.32 ms
  teaches census source	adopter rule meanings	passed	6.12 ms
  teaches open-question register source	adopter rule meanings	passed	1.36 ms
  teaches dependency register source	adopter rule meanings	passed	1.99 ms
  teaches mention register source	adopter rule meanings	passed	1.22 ms
  teaches delta scope source	adopter rule meanings	passed	1.18 ms
  teaches no quoted counts	adopter rule meanings	passed	1.13 ms
  teaches operator-selected policy	adopter rule meanings	passed	1.84 ms
  teaches per-file policy parameters	adopter rule meanings	passed	1.1 ms
  teaches separate policy findings	adopter rule meanings	passed	1.1 ms
  teaches policy failures	adopter rule meanings	passed	1.13 ms
  teaches watch policy rereads	adopter rule meanings	passed	1.08 ms
  teaches Constraints leading-prose exception	adopter rule meanings	passed	1.07 ms
  teaches one primary owner	adopter rule meanings	passed	1.07 ms
  rejects the opposite teaching for independent defined floor: defined floor does not read the parent's readiness	adopter rule meanings	passed	1.23 ms
  rejects the opposite teaching for independent defined floor: defined floor does not read the parent's readiness	adopter rule meanings	passed	1.23 ms
  rejects the opposite teaching for example vocabulary agreement: complete and match the parent's example vocabulary, when it has one	adopter rule meanings	passed	2.27 ms
  rejects the opposite teaching for ready reads parent: ready floor does read the parent's readiness	adopter rule meanings	passed	1.17 ms
  rejects the opposite teaching for physical entry line: a wrapped or indented continuation is refused	adopter rule meanings	passed	1.18 ms
  rejects the opposite teaching for one leading prose owner: Leading prose may stand under that owner or under Example space, not both	adopter rule meanings	passed	1.13 ms
  rejects the opposite teaching for Note is refused: The parser reads - Note: x as a key and refuses it	adopter rule meanings	passed	1.1 ms
  rejects the opposite teaching for open-question home: An open question goes under Intent's ### Open questions.	adopter rule meanings	passed	1.07 ms
  accepts a harmless open-question instruction frame	adopter rule meanings	passed	1.14 ms
  defined examples ignore parent readiness but read its vocabulary: matches=true	adopter rule meanings	passed	2.35 ms
  defined examples ignore parent readiness but read its vocabulary: matches=false	adopter rule meanings	passed	0.44 ms
  teaches the Intent grammar row	adopter rule meanings	passed	0.76 ms
  teaches the Intent grammar row	adopter rule meanings	passed	0.63 ms
  teaches the Behavior grammar row	adopter rule meanings	passed	0.55 ms
  teaches the Rule grammar row	adopter rule meanings	passed	0.61 ms
  teaches the Workflow grammar row	adopter rule meanings	passed	0.54 ms
  teaches the Workflow grammar row	adopter rule meanings	passed	0.64 ms
  teaches the Contract grammar row	adopter rule meanings	passed	0.63 ms
  teaches the Example space grammar row	adopter rule meanings	passed	0.57 ms
  teaches the Example space grammar row	adopter rule meanings	passed	0.51 ms
  teaches the Constraints grammar row	adopter rule meanings	passed	0.54 ms
  teaches the Constraints grammar row	adopter rule meanings	passed	0.53 ms
  teaches the Constraints grammar row	adopter rule meanings	passed	0.55 ms
  teaches the Model grammar row	adopter rule meanings	passed	0.5 ms
  teaches the Model grammar row	adopter rule meanings	passed	0.55 ms
  teaches the Design grammar row	adopter rule meanings	passed	0.5 ms
  teaches the Design grammar row	adopter rule meanings	passed	0.55 ms
  teaches the Decision grammar row	adopter rule meanings	passed	0.61 ms
  teaches the Decision grammar row	adopter rule meanings	passed	0.53 ms
  teaches the UI grammar row	adopter rule meanings	passed	0.51 ms
  teaches the Verification — <mode> grammar row	adopter rule meanings	passed	0.51 ms
  teaches the Verification — <mode> grammar row	adopter rule meanings	passed	0.52 ms
  teaches the Verification — <mode> grammar row	adopter rule meanings	passed	0.5 ms
  keeps graph-reader verifier teaching about existence and CI outcomes	adopter rule meanings	passed	0.86 ms
  keeps session teaching advisory and separate from permission	adopter rule meanings	passed	0.53 ms
  the README teaches commit pin	adopter install and upgrade guidance	passed	0.33 ms
  the README teaches npm script approval	adopter install and upgrade guidance	passed	0.28 ms
  the README teaches npm git approval	adopter install and upgrade guidance	passed	0.29 ms
  the README teaches pnpm repository approval	adopter install and upgrade guidance	passed	0.27 ms
  the README teaches pnpm 10 exact approval	adopter install and upgrade guidance	passed	0.26 ms
  the README teaches installed CLI check	adopter install and upgrade guidance	passed	0.25 ms
  the README teaches vitest subpath requirement	adopter install and upgrade guidance	passed	0.25 ms
  the README teaches recipe subject as params	adopter install and upgrade guidance	passed	0.23 ms
  refuses wrapped continuation	taught grammar agrees with parser behavior	passed	1.49 ms
  refuses indented continuation	taught grammar agrees with parser behavior	passed	0.25 ms
  allows leading prose under either owner and refuses it under both	taught grammar agrees with parser behavior	passed	1.11 ms
  refuses Note as a plain Rule entry	taught grammar agrees with parser behavior	passed	0.29 ms
  refuses Note as a plain Workflow entry	taught grammar agrees with parser behavior	passed	0.17 ms
  refuses Note as a plain Contract entry	taught grammar agrees with parser behavior	passed	0.13 ms
  refuses Note as a plain Verification — manual entry	taught grammar agrees with parser behavior	passed	0.6 ms
  refuses unique Model terms duplicates	taught grammar agrees with parser behavior	passed	0.53 ms
  refuses unique Design keys duplicates	taught grammar agrees with parser behavior	passed	0.16 ms
  refuses unique UI keys via Design form duplicates	taught grammar agrees with parser behavior	passed	0.14 ms
  refuses single Intent actor duplicates	taught grammar agrees with parser behavior	passed	0.53 ms
  refuses single Intent problem duplicates	taught grammar agrees with parser behavior	passed	0.17 ms
  refuses single Intent outcome duplicates	taught grammar agrees with parser behavior	passed	0.12 ms
  refuses single Intent value duplicates	taught grammar agrees with parser behavior	passed	0.12 ms
  refuses single Constraints statement duplicates	taught grammar agrees with parser behavior	passed	1.38 ms
  refuses single Constraints flavor duplicates	taught grammar agrees with parser behavior	passed	0.23 ms
  refuses single Constraints target duplicates	taught grammar agrees with parser behavior	passed	0.17 ms
  refuses single Constraints measurableBy duplicates	taught grammar agrees with parser behavior	passed	0.12 ms
  refuses single Decision context duplicates	taught grammar agrees with parser behavior	passed	0.26 ms
  refuses single Decision decision duplicates	taught grammar agrees with parser behavior	passed	0.11 ms
  allows Behavior alone and refuses a second primary owner	taught grammar agrees with parser behavior	passed	0.51 ms
  allows Rule alone and refuses a second primary owner	taught grammar agrees with parser behavior	passed	0.2 ms
  allows Workflow alone and refuses a second primary owner	taught grammar agrees with parser behavior	passed	0.14 ms
  allows Contract alone and refuses a second primary owner	taught grammar agrees with parser behavior	passed	0.22 ms
  allows leading prose in Design and refuses it in Constraints	taught grammar agrees with parser behavior	passed	0.21 ms
  allows the taught repeatable Intent entries	taught grammar agrees with parser behavior	passed	0.22 ms
  allows the taught repeatable Decision entries	taught grammar agrees with parser behavior	passed	0.16 ms
  extracts the key the skill's marker carries and resolves the address the skill gives it	the taught question marker	passed	12.24 ms
  leaves the address unresolved when the key stands outside the brackets	the taught question marker	passed	7.39 ms
  creates the anchored suite before generating, and the build places the registrar beside it	the reviewed skill teaching	passed	23.37 ms
  keys a step in the vocabulary, as the step-key law and the contract generator agree	the reviewed skill teaching	passed	12.4 ms
  owns publishing in one reader section that agrees with each verb's flags	the reviewed skill teaching	passed	3.85 ms
  names the vault's owned folder, the person's notes and the roots a vault run removes	the reviewed skill teaching	passed	0.76 ms
  teaches entry addresses, term addresses and anchored source citations as the engine derives them	the reviewed skill teaching	passed	16.18 ms
  states what an empty or ready answer establishes and no more	the reviewed skill teaching	passed	1.94 ms
  teaches a refused bundle as the end of pagination, as recipe 36 refuses	the reviewed skill teaching	passed	11.52 ms
  keeps corpus rules in one section whose composed rules file runs as taught	the reviewed skill teaching	passed	10.59 ms
  points every skill at the installed upgrade guide and triggers authoring on upgrades and rules	the reviewed skill teaching	passed	1.91 ms
  orders the reader as a task route and leaves recipe contracts to the catalog	the reviewed skill teaching	passed	3.36 ms
  states the graph's flat topology and which node types carry lines, as the graph does	the reviewed skill teaching	passed	15.04 ms
  is its own shipped skill, which the reading skill points to	the Studio on-ramp	passed	0.97 ms
  starts from what the agent holds	the Studio on-ramp	passed	0.32 ms
  teaches the publishing run as the studio and generate verbs take it	the Studio on-ramp	passed	1.86 ms
  teaches stamping and the preview workflow as the workflow declares them	the Studio on-ramp	passed	5.73 ms
  has the preview's run evidence checked against the stamp, never assumed to match it	the Studio on-ramp	passed	2.7 ms
  maps each task to a page the Studio writes, and states what a page does not	the Studio on-ramp	passed	52.89 ms
  receives the composing panel's hand-off through the proposal check	the Studio on-ramp	passed	9.59 ms
  cites resolving Studio Specs for law and leaves flags to each verb's help	the Studio on-ramp	passed	648.7 ms
  is its own shipped skill, which the reading skill points to	the vault on-ramp	passed	1.44 ms
  places the vault where the command accepts it	the vault on-ramp	passed	6.47 ms
  keeps the person's notes outside the folder the command owns	the vault on-ramp	passed	0.67 ms
  teaches synchronizing and watching as the verbs and the failed index state them	the vault on-ramp	passed	0.61 ms
  names every refusal the guard prints and how to recover from it	the vault on-ramp	passed	0.93 ms
  converts a note's links back to the addresses the vault wrote, then checks the proposal	the vault on-ramp	passed	17.21 ms
  takes the proposal's base from the graph the person read, never from the latest synchronization	the vault on-ramp	passed	4.62 ms
  cites resolving vault Specs for law and leaves flags to the verb's help	the vault on-ramp	passed	97.29 ms

Requirement drawing

• Declared verifying examples: no declared verifying example.

Decisions

• Bindings are optional, plural, and may reference a design

  On a code anchor, satisfies is optional and plural; on a test anchor, verifies is plural and non-empty. The constant form accepts one ref(…) or a fresh array literal of them. Each resolving target confers its fact, and implemented stays a whole-Spec fact. An anchored edge references runs from a CodeNode to a Spec, from references?: readonly SpecId[] on a code anchor; it may target any Spec, decisions included, confers no delivery fact, moves no readiness floor, and the drift alarm ignores it. It says this code answers to that design without claiming to realize it: the unit follows the design without realizing any of its promises, or realizes part of a Spec whose remaining promises no unit yet realizes, so a change to the design asks the code to follow. A design that builds on existing code states that by a typed relation to the Spec the code satisfies, never by a reference from the code. A target named in both satisfies and references is an error. An identity-only code anchor, with no satisfies and no references, is lawful: it mints a CodeNode for structure and for byFile, and nothing else.

• The comment form is a second anchor representation

  An anchor has two extracted representations that feed one closed envelope, the constant form as ruled and a comment form. The comment form is a top-level /** … */ block in a .ts or .tsx file carrying reserved camelCase, TSDoc-compatible tags; @sdpAnchor <id> opens it, and the id's namespace selects the flavor exactly as the constant builders do. Comment prose still authors nothing: only the reserved tags are read, and a comment that does not open with /** is never read. Trust is by reserved grammar, not by builder import, so no import is required. The same id in two forms is a duplicate id. The package also ships a zero-dependency subpath @libar-dev/software-delivery-protocol/anchors exporting the id builders and the three anchor builders and nothing else, for runtimes that may import but must not load node:* modules or ts-morph; the extractor trusts that specifier as a Protocol builder module.

• Architectural significance is annotated where it is realized

  Architectural significance is annotated on the anchor of the unit that realizes it. A code anchor may carry role, the architectural pattern the unit plays; a component: anchor may additionally carry layer, one of edge, application, domain, adapter, or infrastructure, and context, its bounded context. The component: anchor is anchored architecture: it is the declared component, and there is no separate architecture file, because the anchor sits where the component is realized. It is not the original design's declared Component that could exist before code; an unrealized component lives in Specs and never as an invented CodeNode. A role is a free, corpus-owned vocabulary whose taxonomy the census renders with counts from the graph; service, decider, projection, read-model, codec, contract, barrel, and utility are the lineage set, not a closed list. layer is a closed set, and a value outside it is an envelope error; layer or context on a non-component anchor is an envelope error. All three attributes are optional, and omission is lawful.

• component:protocol.cli · entry points, shared build and publication · src/cli/build-command.ts:32 · layer edge · context protocol

  Uses

  • component:protocol.adapters · external runtime and source adapters · src/adapters/vitest.ts:23 · layer adapter · context protocol
  • component:protocol.codegen · contracts and registrar output · src/codegen/contracts.ts:633 · layer application · context protocol
  • component:protocol.extract · the carrier and source pipeline · src/extract/index.ts:192 · layer application · context protocol
  • component:protocol.graph · the one graph and its semantic decisions · src/graph/schema.ts:34 · layer domain · context protocol
  • component:protocol.import · canonical conversion with a fidelity boundary · src/import/import.ts:45 · layer application · context protocol
  • component:protocol.model · the authored contracts and stable ids · src/model/anchors.ts:100 · layer domain · context protocol
  • component:protocol.projections · read-only output, layout and owned publication · src/projections/design-review.ts:29 · layer edge · context protocol
  • component:protocol.reader · the typed graph contract and body evaluator · src/reader/reader.ts:671 · layer application · context protocol
  • component:protocol.validate · one finding currency and ordered checks · src/validate/validators.ts:72 · layer domain · context protocol
• impl:protocol.authoring-on-ramp · asserts realization of the shipped graph-first authoring skill document · test/skills.test.ts:76

  Uses

  None.

• impl:protocol.spec-scaffolder · scaffolds an honest idea-rung Markdown Spec through sdp new spec · src/cli/new-spec-command.ts:348

  Component: component:protocol.cli · entry points, shared build and publication · src/cli/build-command.ts:32 · layer edge · context protocol

  Uses

  None.

Runtime observation: not tracked.

Runtime observation: not tracked.

Build attestations: not tracked.

Deployments: not tracked.

Bills of materials: not tracked.