Runtime Handoff
Generated from workflows/modes/runtime-handoff.md, the mode contract the HELIX skill loads. Edit that file, not this page.
Use when a workflow mode concludes that the next step is execution, source control, packaging, or a long-lived operator loop. HELIX does not own those surfaces; the runtime does.
- Name the implementation-ready plan, explicitly selected work item, or
artifact gap that is ready for runtime action. Follow
workflows/references/work-item-first.md: a plan can govern the whole goal without tracker acquisition. Planning readiness does not authorize execution. After implementation is authorized, continue through verified completion, preserving continuation evidence across interruptions. - Name the domain lane and scope instance the runtime should preserve. Carry
the token estimate, total spending ceiling, and available metering or
enforcement limits from
workflows/references/work-item-first.mdin the existing execution contract; include verification and review in that ceiling. - Name existing acceptance mappings, test-source citations and run reports for
completion under the verification practices. For affected runtime boundaries, include
observable end-to-end evidence against the running system when feasible, plus a claims-vs-reality
check with zero phantom claims. See the in-tree
workflows/concerns/verification/practices.md, or thereferences/concerns/verification/practices.mdfloor — resolved via §Catalog Resolution (the floor always resolves). - For data-backed products, require governed sample or seed data with
synthetic non-PII values and enough variation to exercise schema-relevant
states. See the in-tree
workflows/concerns/sample-data/practices.md, or thereferences/concerns/sample-data/practices.mdfloor — resolved via §Catalog Resolution (the floor always resolves). - Do not prescribe runtime commands from the skill body. Point to the runtime’s install or operator guide for concrete execution, source control, packaging, or loop commands.
Source-Code Boundaries
For handwritten source, require modularity-and-encapsulation evidence: adopted module map, concrete boundary-check command and supported negative controls, semantic review of public APIs/type ownership/invariants, and existing-debt/exception dispositions. Do not hand dependent feature work off as ready without these prerequisites. Bounded adoption work may create them.
OpenTelemetry Diagnostics
Apply selected o11y-otel practice sections, including agent run diagnostics
where commands/tests need persistent evidence. Preserve applicability without
silently re-selecting concerns. Require safe run/attempt evidence references,
verification outcome and capture limits at execution closeout; a quiet console
is not a pass. Shared schemas stay in Contracts, with actual OTel receiver proof
for claimed integrations. See workflows/references/agent-diagnostics.md.
UX coverage
For affected interactive UI work, apply ux-interaction-patterns and the selected component owner. Use workflows/references/ux-evidence.md: a missing STP UX Coverage map is an adoption/readiness gap, not retroactive invalidity. Require populated AC mappings and review exclusion reasons. For planning/readiness, check named planned tests, commands, component gaps and evidence capture; do not demand future passing results. For implementation/completion claims, check actual test source and observed runtime results; SDK audit evidence cannot prove interaction flows.
Innsigle seal: model-primary by HELIX
The signature covers the markdown source of this page, not these HTML bytes. This page quotes that seal; verify it against the source file.
- Composition
- model-primary
- Issuer
- HELIX
helix - Signing key
ed25519:b0865d76d834a52c48506414d16f4e5a(build key)- Signed source
reference/workflow-modes/runtime-handoff.md- Signed
- 2026-11-16T15:52:45Z
- Content digest
sha256:68d58275…17108284
This build key is endorsed by the human key for build signing; the signature is not a detector and not a truth guarantee.
Raw attestation JSON
{
"payload": {
"innsigle": "1",
"type": "https://innsigle.dev/claim/colophon/v1",
"issued_at": "2026-11-16T15:52:45Z",
"issuer": {
"id": "helix",
"name": "HELIX",
"key_id": "ed25519:b0865d76d834a52c48506414d16f4e5a",
"key_url": "https://documentdrivendx.github.io/helix/.well-known/innsigle/keys.json"
},
"subjects": [
{
"uri": "https://documentdrivendx.github.io/helix/reference/workflow-modes/runtime-handoff/",
"digest": {
"alg": "sha256",
"value": "68d582754ba19d28a82269aa2174937853fed3f59aa878f8fd2a18ea17108284"
}
}
],
"colophon": {
"schema_version": "1",
"composition": "model-primary",
"ingredients": [
{
"kind": "model",
"name": "Claude",
"role": "draft"
},
{
"kind": "tool",
"name": "sloptimizer",
"role": "rewrite"
},
{
"kind": "human",
"name": "operator",
"role": "structure-edit"
}
],
"notes": null
}
},
"payload_encoding": "json",
"signatures": [
{
"key_id": "ed25519:b0865d76d834a52c48506414d16f4e5a",
"alg": "ed25519",
"sig": "UsCRmGeiiMadjDlS_AjqmMiFVs-E4Cur_WEP3TDz54uvKtmPDw9JU-JveclbNg5ux2x944OZPFOowbmRLFxXAA",
"signed_at": "2026-11-16T15:52:45Z"
}
]
}