Context
Consolidated follow-up from @neo-gemini-3-1-pro's review of PR #10782 (commentId IC_kwDODSospM8AAAABBTjRVg, Approve+Follow-Up status). PR #10782 ships persistent-process management substrate for the swarm-heartbeat daemon (#10781); this follow-up addresses the 3 doc-side items that don't gate the merge but should land for substrate-completeness.
Filed as ONE consolidated ticket per feedback_workflow_discipline_over_velocity — the 3 items share a substrate (operator-doc) and reviewer; one ticket is cleaner than 3 separate.
The 3 follow-up items
1. Slot-rule discriminator retrofit
learn/agentos/wake-substrate/PersistentProcessManagement.md was authored before the cycle-2 V1 (#10764, merged) authoring guide retrofit reached operational steady-state. The new doc doesn't apply the 3-axis slot rule (trigger-frequency × failure-severity × enforceability) + 5-disposition taxonomy + substrate-vs-discipline tagging that V1 added to skill-authoring-guide.md.
Per V1 MACHINE-ENFORCEABLE-CANDIDATE / DISCIPLINE-ONLY tagging convention:
- §2 Empirical-prerequisites =
MACHINE-ENFORCEABLE-CANDIDATE (could be hook-checked)
- §3 macOS install procedure =
DISCIPLINE-ONLY (operator-judgment)
- §4 Uninstall =
DISCIPLINE-ONLY
- §5 Linux sibling (out-of-scope-for-v1) =
DISCIPLINE-ONLY
- §6 Troubleshooting table = each gotcha tagged per shape
2. AGENTS_STARTUP.md §9 Workflow Skills entry
Currently swarm-heartbeat is not listed in AGENTS_STARTUP.md §9 trigger table. Verify-before-assert pending: confirm whether §9 is the right home — swarm-heartbeat is a daemon (operator-managed process), not an agent-invocable skill. May be that §9 is the wrong location and the operator-doc cross-link should live in a different §.
If §9 IS the right home: add a row mapping the persistent-process-management trigger condition to the doc.
If NOT: identify the correct home (AGENTS_STARTUP.md §0 Critical Gates? AGENTS.md §22 Mailbox Check Protocol? Separate operator-runbook section?).
3. pull-request-workflow driver-mode cross-link
When an agent is in driver-mode lease (per #10763 Leased Driver Pattern), they may invoke high-authority recovery actions or interact with the wake substrate. The pull-request-workflow.md skill payload doesn't currently cross-link to PersistentProcessManagement.md for awareness of operator-discipline considerations during merge cycles.
Specific add: 1-2 line cross-reference in the Driver-Mode-related section of pull-request-workflow.md (or appropriate adjacent section), pointing to PersistentProcessManagement.md for night-shift readiness context.
Architectural Reality
learn/agentos/wake-substrate/PersistentProcessManagement.md (NEW, will be merged via PR #10782)learn/agentos/wake-substrate/com.neomjs.swarm-heartbeat.plist.template (NEW, will be merged via PR #10782)AGENTS_STARTUP.md §9 Workflow Skills (existing trigger table).agents/skills/pull-request/references/pull-request-workflow.md (existing payload).agents/skills/create-skill/references/skill-authoring-guide.md (cycle-2 V1 #10764 authoring discipline source)
Acceptance Criteria
Out of Scope
- Re-engineering the wake-substrate operator-doc — additive-only
- Authoring new skills — this is doc-substrate + workflow-payload edits
- Linux systemd sibling (already AC3 of #10781 as out-of-scope-for-v1)
Avoided Traps
- Filing 3 separate tickets when the substrate is shared — consolidating reduces filing-overhead + reviewer-load + clarifies the "Approve+Follow-Up" closure shape
- Auto-adding to
AGENTS_STARTUP.md §9 without verification — verify-before-assert says check whether the substrate fits §9 before adding (per feedback_verify_before_assert.md umbrella)
- Bundling with PR #10782 — separate PR is workflow-cleaner; PR #10782 already approved-with-follow-ups, doesn't need to wait
Related
- Predecessor PR: #10782 (the substrate this follows up)
- Predecessor ticket: #10781 (which #10782 closes)
- Parent epic: #10671 (substrate-restart recovery)
- Reviewer: @neo-gemini-3-1-pro (per IC_kwDODSospM8AAAABBTjRVg)
- Cycle-2 V1 source: #10764 (slot-rule authoring discipline this retrofit applies)
Origin Session ID: 23b9cbcd-4938-4a46-b21a-0d48dd12e7e7
Retrieval Hint: query_raw_memories(query="PR 10782 doc follow-ups slot-rule retrofit AGENTS_STARTUP §9 pull-request driver-mode cross-link 10781")
Context
Consolidated follow-up from @neo-gemini-3-1-pro's review of PR #10782 (commentId IC_kwDODSospM8AAAABBTjRVg, Approve+Follow-Up status). PR #10782 ships persistent-process management substrate for the swarm-heartbeat daemon (#10781); this follow-up addresses the 3 doc-side items that don't gate the merge but should land for substrate-completeness.
Filed as ONE consolidated ticket per
feedback_workflow_discipline_over_velocity— the 3 items share a substrate (operator-doc) and reviewer; one ticket is cleaner than 3 separate.The 3 follow-up items
1. Slot-rule discriminator retrofit
learn/agentos/wake-substrate/PersistentProcessManagement.mdwas authored before the cycle-2 V1 (#10764, merged) authoring guide retrofit reached operational steady-state. The new doc doesn't apply the 3-axis slot rule (trigger-frequency × failure-severity × enforceability) + 5-disposition taxonomy + substrate-vs-discipline tagging that V1 added toskill-authoring-guide.md.Per V1
MACHINE-ENFORCEABLE-CANDIDATE/DISCIPLINE-ONLYtagging convention:MACHINE-ENFORCEABLE-CANDIDATE(could be hook-checked)DISCIPLINE-ONLY(operator-judgment)DISCIPLINE-ONLYDISCIPLINE-ONLY2.
AGENTS_STARTUP.md§9 Workflow Skills entryCurrently
swarm-heartbeatis not listed inAGENTS_STARTUP.md§9 trigger table. Verify-before-assert pending: confirm whether §9 is the right home —swarm-heartbeatis a daemon (operator-managed process), not an agent-invocable skill. May be that §9 is the wrong location and the operator-doc cross-link should live in a different §.If §9 IS the right home: add a row mapping the persistent-process-management trigger condition to the doc. If NOT: identify the correct home (
AGENTS_STARTUP.md§0 Critical Gates?AGENTS.md §22 Mailbox Check Protocol? Separate operator-runbook section?).3.
pull-request-workflowdriver-mode cross-linkWhen an agent is in driver-mode lease (per #10763 Leased Driver Pattern), they may invoke high-authority recovery actions or interact with the wake substrate. The
pull-request-workflow.mdskill payload doesn't currently cross-link toPersistentProcessManagement.mdfor awareness of operator-discipline considerations during merge cycles.Specific add: 1-2 line cross-reference in the Driver-Mode-related section of
pull-request-workflow.md(or appropriate adjacent section), pointing toPersistentProcessManagement.mdfor night-shift readiness context.Architectural Reality
learn/agentos/wake-substrate/PersistentProcessManagement.md(NEW, will be merged via PR #10782)learn/agentos/wake-substrate/com.neomjs.swarm-heartbeat.plist.template(NEW, will be merged via PR #10782)AGENTS_STARTUP.md§9 Workflow Skills (existing trigger table).agents/skills/pull-request/references/pull-request-workflow.md(existing payload).agents/skills/create-skill/references/skill-authoring-guide.md(cycle-2 V1 #10764 authoring discipline source)Acceptance Criteria
PersistentProcessManagement.md: each section tagged + slot-rule rationale documented at topAGENTS_STARTUP.md§9 verified empirically — either add row OR document why this substrate doesn't fit §9 (with cross-link to correct home)pull-request-workflow.mdcross-link added (1-2 lines, low-collision-risk insertion)Out of Scope
Avoided Traps
AGENTS_STARTUP.md §9without verification — verify-before-assert says check whether the substrate fits §9 before adding (perfeedback_verify_before_assert.mdumbrella)Related
Origin Session ID: 23b9cbcd-4938-4a46-b21a-0d48dd12e7e7
Retrieval Hint:
query_raw_memories(query="PR 10782 doc follow-ups slot-rule retrofit AGENTS_STARTUP §9 pull-request driver-mode cross-link 10781")