HQ hands a settled piece to a detailed session

actor

HQ, starting work; the agent leading a detailed session.

problem

A session that starts from copied context builds on stale status and misses how the target repository works, and its result does not come back to the plan.

outcome

A settled piece of the plan reaches the engineering environment as a session that names its Specs and its target, works by the target's own rules, and comes back as a pull request HQ can read.

Open questions

• non-blocking · question.sessionModels line 36 · specs/hq/session-handoff.sdp.md:36 · Which harness and models does a detailed session run on?Decider: delegatedProvisional: The session's lead chooses per task, under the orchestration aspect's rules.

rule.selects line 42 · specs/hq/session-handoff.sdp.md:42

HQ selects a settled entry from the roadmap and names the target repository, the Specs it rests on and what the session must return.

no example exercises it

rule.starts line 43 · specs/hq/session-handoff.sdp.md:43

HQ starts a project session in the target repository's checkout in the engineering environment through T3's MCP.

no example exercises it

rule.works line 44 · specs/hq/session-handoff.sdp.md:44

The session does the detailed planning, design and execution there, under that repository's own instructions, skills, tests and gate.

no example exercises it

rule.returns line 45 · specs/hq/session-handoff.sdp.md:45

The session returns the pull request's URL, head commit, and checks and reviews, plus any new standing directions, decision points and cross-project context, which HQ routes to their one home.

no example exercises it

rule.updates line 46 · specs/hq/session-handoff.sdp.md:46

HQ reviews the pull request against the named Specs and the target's gate, and names the work delivered only after it merges.

no example exercises it

rule.targetOwnsDetail line 47 · specs/hq/session-handoff.sdp.md:47

Detailed design lands in the target repository, in its own SDP corpus where it has one; this corpus names it and copies none of it.

no example exercises it

rule.targetGate line 48 · specs/hq/session-handoff.sdp.md:48

A session answers to the target repository's own tests and gate, and HQ's plan never stands in for them.

no example exercises it

rule.briefNamesSpecs line 49 · specs/hq/session-handoff.sdp.md:49

A session's brief names Specs, a Pack and the target, and carries a read-only projection of them, the context bundle (recipe 36); it copies no status and no other plan text.

no example exercises it

rule.lockedDesign line 50 · specs/hq/session-handoff.sdp.md:50

An approved part of the graph reaches the target repository as a read-only projection, regenerated from this corpus and refused by the target's gate if edited.

no example exercises it

0 unkeyed rules.

Verifier bindings

No verifier binding recorded.

Requirement drawing

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

Decisions

• An approved part of the graph reaches engineering as a read-only projection

  When a part of the graph reaches an agreed status, it is delivered to the target repository as a read-only projection: the selected Specs with their ancestors, the decisions behind them and every Spec their text mentions. The repository refines and implements against it, and its own gate refuses any edit to it.

• HQ does the core design and starts detailed work in the engineering environment

  HQ does long-term planning, high-level design and cross-project context. When a piece settles, HQ starts detailed planning and execution as sessions in the engineering environment, and does not do that work itself.

No implementation neighborhood recorded.

Runtime observation: not tracked.

Runtime observation: not tracked.

Build attestations: not tracked.

Deployments: not tracked.

Bills of materials: not tracked.