Spec Studio

HQ runs in an isolated environment that infra manages

spec:hq.environmentUse Case / Behavior · featuredefined floor ready

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

Packs: none

Design: no design entries · no pinned declarations · 1 decision

Findings: no errors, no warnings

design/hq/hq/environment.sdp.md

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

Intent
actor
The owner, and the agents working in HQ.
problem
HQ was bootstrapped in the same context as the work it plans, so its sessions inherit everything around them.
outcome
HQ runs in an isolated environment that infra provisions and manages, and a blank session there can read the plan and work from it.
assumptions
  • A blank session is the honest test, because what a blank session cannot do is what an outside project would miss.
Behavior
rule.infraManages line 28 · design/hq/hq/environment.sdp.md:28
Infra provisions and manages HQ's environment: its harnesses, its skills and its configuration.

no example exercises it

rule.ownProfiles line 29 · design/hq/hq/environment.sdp.md:29
HQ keeps its own harness profile, as its dedicated Codex home stands apart from the engineering profile.

no example exercises it

rule.hqReads line 30 · design/hq/hq/environment.sdp.md:30
A session in HQ reads this plan, Kontrapunkt and what infra deploys to HQ; it reaches an engineering repository only through a detailed session.

no example exercises it

0 unkeyed rules.

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:hq.environment

Arrows: refines (declared).

The diagram as text
  • spec:hq.environment: HQ runs in an isolated environment that infra manages · declared Spec · no satisfying binding
  • spec:hq.headquarters: HQ plans and designs across every project, and starts the engineering work · declared Spec
  • spec:hq.environment refines spec:hq.headquarters · declared — gives HQ's isolation its home
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.

Decisions

  • Infra is super isolated and manages the isolated HQ

    HQ is isolated in the owner's sense: it keeps long-term planning, high-level design and cross-project context apart from detailed planning and execution, which it initiates as sessions in the engineering environment. Infra is super isolated and manages the isolated HQ. Deployment and access boundaries are designed in infra, and the owner's use of 'isolated' does not itself select a machine, kernel or network policy.

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:hq.environment
  • E3: constrainedBy · declared — the requirement says infra manages this environment
The diagram as text
  • spec:decisions.isolated-infra-manages-hq: Infra is super isolated and manages the isolated HQ
  • spec:hq.environment: HQ runs in an isolated environment that infra manages
  • spec:hq.headquarters: HQ plans and designs across every project, and starts the engineering work
  • spec:hq.isolation: HQ works apart from detailed work, and infra manages its environment
  • spec:hq.session-handoff: HQ hands a settled piece to a detailed session
  • spec:hq.environment constrainedBy spec:hq.isolation · declared — the requirement says infra manages this environment
  • spec:hq.environment decidedBy spec:decisions.isolated-infra-manages-hq · declared — the ruling makes infra the manager of this environment
  • spec:hq.environment refines spec:hq.headquarters · declared — gives HQ's isolation its home
  • spec:hq.session-handoff dependsOn spec:hq.environment · declared — the handoff starts from an isolated HQ
Mermaid source

Copyable source; the Studio draws static SVG.

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

Rests on

Rested on by

Distance 1

Distance 2

Distance 3

Distance 4

Distance 5

Distance 6

Relations

Relation and directionOther endClaimReasonExercised keys
constrainedBy · outgoingHQ works apart from detailed work, and infra manages its environment
spec:hq.isolation · resolves		declaredthe requirement says infra manages this environmentNone
decidedBy · outgoingInfra is super isolated and manages the isolated HQ
spec:decisions.isolated-infra-manages-hq · resolves		declaredthe ruling makes infra the manager of this environmentNone
refines · outgoingHQ plans and designs across every project, and starts the engineering work
spec:hq.headquarters · resolves		declaredgives HQ's isolation its homeNone
dependsOn · incomingHQ hands a settled piece to a detailed session
spec:hq.session-handoff · resolves		declaredthe handoff starts from an isolated HQNone

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.