Relay

spec:architecture.relay

Use Case / Behavior · featurescoped floor ready

Next rung defined: nothing blocks; it waits only for the author's statement.

Packs: none

Design: 3 design entries · 3 pinned declarations · no decisions

specs/architecture/relay.sdp.md

No open questions and no blocking questions; implementation binding none, verifier binding none, and expected-outcome oracle none.

Intent

outcome: Other providers' models work on one task beside Claude.

Behavior

rule line 19 · specs/architecture/relay.sdp.md:19: Relay runs jobs from inside the Claude harness in T3.

1 unkeyed rule.

Design

id line 23 · specs/architecture/relay.sdp.md:23: component:orchestration.relay
no citation recorded
context line 24 · specs/architecture/relay.sdp.md:24: orchestration
no citation recorded
uses line 25 · specs/architecture/relay.sdp.md:25: component:engineering.claude-harness — it runs inside the harness.
no citation recorded

Verification

Verifier bindings

No verifier binding recorded.

Design view

Requirement drawing

Declared verifying examples: no declared verifying example.
Satisfying or referencing units: no recorded binding.
Test or oracle bindings: no recorded binding.

Requirement drawing for spec:architecture.relay

Arrows: refines (declared).

The diagram as text

spec:architecture.relay: Relay · declared Spec · no satisfying binding
spec:hq.headquarters: HQ plans and designs across every project, and starts the engineering work · declared Spec
spec:architecture.relay refines spec:hq.headquarters · declared — one of the systems HQ's design names

Mermaid source

Copyable source; the Studio draws static SVG.

Preferred and chosen syntax: requirementDiagram; exact refines, satisfies and verifies, with claim words in nodes and per-edge comments.

Mermaid source for Requirement drawing for spec:architecture.relay

requirementDiagram
  requirement n0 {
    text: "Relay · declared Spec · no satisfying binding · spec:architecture.relay"
  }
  requirement n1 {
    text: "HQ plans and designs across every project, and starts the engineering work · declared Spec · spec:hq.headquarters"
  }
  %% claim: declared; reason: one of the systems HQ's design names
  n0 - refines -> n1

Decisions

No decision record named.

Runtime

No implementation neighborhood recorded.

Runtime observation: not tracked.

Evidence

Runtime observation: not tracked.

Build attestations: not tracked.

Deployments: not tracked.

Bills of materials: not tracked.

Impact

Relations of spec:architecture.relay

Arrows: refines (declared).

The diagram as text

spec:architecture.relay: Relay
spec:hq.headquarters: HQ plans and designs across every project, and starts the engineering work
spec:architecture.relay refines spec:hq.headquarters · declared — one of the systems HQ's design names

Mermaid source

Copyable source; the Studio draws static SVG.

Preferred syntax: flowchart. Chosen syntax: labelled flowchart, preserving exact relations, claims and folds.

Mermaid source for Relations of spec:architecture.relay

flowchart TB
  n0["HQ plans and designs across every project, and starts the engineering work · spec:hq.headquarters"]
  n1["Relay · spec:architecture.relay"]
  n1 -->|"refines · declared — one of the systems HQ's design names"| n0

Rests on

refines · spec:hq.headquarters · stated defined, floor ready

Rested on by

No Spec rests on this Spec.

Relations

Relation and direction	Other end	Claim	Reason	Exercised keys
refines · outgoing	HQ plans and designs across every project, and starts the engineering work `spec:hq.headquarters` · resolves	declared	one of the systems HQ's design names	None

Bindings

Implementation binding: none

Design reference: none

Verifier binding: none

Expected-outcome oracle: none

Runtime observation: not tracked.

Run results: not recorded in the graph.

Findings

None.

Composing (0)

Composing needs the script.