Phase 4 — Clean Cabra/OpenClaw cron, heartbeat, and tooling authority state

[marcusglee11]

Objective:
Resolve stale or ambiguous local authority surfaces identified in #108 without expanding autonomy or performing unattended automation.

Parent:

• Bring Cabra/OpenClaw to LifeOS operational readiness after update #108: Bring Cabra/OpenClaw to LifeOS operational readiness after update
• Phase 0–3 status: PASS via reconciliation comment Bring Cabra/OpenClaw to LifeOS operational readiness after update #108 (comment)

Scope:

1. Inventory all OpenClaw/Cabra cron jobs.
2. Classify each cron job:

• keep disabled
• delete stale
• repair but keep disabled
• propose re-enable, CEO approval required

3. Inspect HEARTBEAT.md.

• Populate with actual heartbeat policy/cadence if active.
• Otherwise mark explicitly non-operational / intentionally empty.

4. Inspect TOOLS.md.

• Populate with real local surfaces/path notes if authoritative.
• Otherwise mark explicitly non-authoritative template.

5. Identify stale route warnings and explain or clear them without enabling sends.

Hard constraints:

• Do not re-enable cron.
• Do not create new unattended automation.
• Do not send external messages.
• Do not expand messaging permissions.
• Do not mutate provider/model config.
• Do not restart or update OpenClaw.
• Do not delete cron/config/state unless separately approved.
• Do not modify subagent/EA authority.

Acceptance evidence:

• Before inventory of cron jobs.
• Proposed disposition for every cron job.
• HEARTBEAT.md readback and final classification.
• TOOLS.md readback and final classification.
• Stale route warning readback and disposition.
• Explicit confirmation no approval-gated action was performed.
• If file edits are proposed, provide exact patch plan first; do not apply without explicit approval.

[marcusglee11]

Verdict: APPROVE

Issues

• No blocking issues.
• Inventory/classification completed only; no implementation started.
• All 9 cron entries are reported disabled.
• Scope stayed limited to cron, HEARTBEAT.md, TOOLS.md, and stale route warnings.
• HEARTBEAT.md is classified inert/no active heartbeat tasks.
• TOOLS.md is classified placeholder/unconfigured/no live operational data.
• Stale route warnings were identified and left untouched.
• The later remove/archive wording is advisory only and is not approval to change scheduler state.

Required amendments

• None for this inventory pass.
• Before any future change, require an exact plan with paths/state surfaces, before readbacks, and per-item proposed actions.

Risk

• Low for this pass.
• Main risk is treating advisory retirement language as approval. Keep the next step plan-only.

Next instruction
APPROVED: Phase 4 inventory/classification pass accepted on #109.

Proceed to Phase 4 patch/action planning only. Do not apply changes.

The plan must include exact file paths or scheduler/state surfaces, before readbacks, proposed edits/actions by category, and a per-cron disposition. Stop after posting the plan and wait for explicit approval.

[marcusglee11]

Phase 4 patch/action plan — planning only

No implementation is authorized by this comment.

Anchors:

• Parent: Bring Cabra/OpenClaw to LifeOS operational readiness after update #108
• Child: Phase 4 — Clean Cabra/OpenClaw cron, heartbeat, and tooling authority state #109
• Phase 0–3 reconciliation: Bring Cabra/OpenClaw to LifeOS operational readiness after update #108 (comment)
• Inventory approval: Phase 4 — Clean Cabra/OpenClaw cron, heartbeat, and tooling authority state #109 (comment)

Accepted baseline:

• 9 OpenClaw/Cabra cron jobs found.
• All 9 are disabled.
• HEARTBEAT.md: inert / no active heartbeat tasks.
• TOOLS.md: placeholder / unconfigured / no live operational data.
• Stale route warnings identified and left untouched.

Exact surfaces

Files:

• /home/cabra/.openclaw/workspace/HEARTBEAT.md
• /home/cabra/.openclaw/workspace/TOOLS.md

Scheduler/state surfaces:

• OpenClaw/Cabra cron scheduler inventory for the 9 disabled jobs.
• Route/delivery metadata attached to those disabled cron jobs.

Record surfaces:

• Phase 4 — Clean Cabra/OpenClaw cron, heartbeat, and tooling authority state #109 comment thread for the action receipt.
• Optional additive evidence file only if separately approved: /mnt/c/Users/cabra/Projects/LifeOS/artifacts/evidence/cabra-readiness/<UTC_TIMESTAMP>/phase4-cron-heartbeat-tools.md

Required before-readbacks

Before any approved change, capture:

• HEARTBEAT.md path, stat, SHA256, and full readback.
• TOOLS.md path, stat, SHA256, and full readback.
• Cron inventory readback with exactly 9 jobs and all disabled.
• Per-cron stable ID, name, cadence, enabled/disabled state, delivery/route warning, and last/next run if exposed.
• SHA256 or stable identifier for the normalized cron inventory readback.

Stop if the live readback differs from the accepted baseline.

Proposed actions by category

1. HEARTBEAT.md

• Proposed edit: documentation-only classification update.
• Target classification: non-operational / intentionally empty.
• Required meaning: no active heartbeat task is authorized; no scheduler job, unattended automation, or outbound delivery is enabled or implied; any future heartbeat cadence requires separate CEO approval.

2. TOOLS.md

• Proposed edit: documentation-only classification update.
• Target classification: non-authoritative template / unconfigured.
• Required meaning: not source of truth for live tools, providers, models, cron state, message routes, or subagent authority; do not infer runtime permissions from this file.

3. Cron disposition record

• Proposed action: record per-cron disposition in Phase 4 — Clean Cabra/OpenClaw cron, heartbeat, and tooling authority state #109 and optional additive evidence only.
• No scheduler mutation in this phase.

4. Stale route metadata

• Proposed action: classify as historical/disabled route metadata.
• No route cleanup or target changes in this phase.

Per-cron disposition

#	Cron	Stable ID	Current state	Phase 4 disposition	Future-only disposition
1	LifeOS ingestion cadence	24854304-1b50-4ae0-bc46-d1be32a5b94b	disabled	keep disabled	propose future redesign or archive/export
2	COO Brief (trial)	2c67a6e6-7d34-4681-a262-6939d2fa90d0	disabled	keep disabled; document retired if trial is inactive	propose future archive/export
3	close-hermes-bus-loop	309ba6db-4c0a-4324-bee0-bd77d4eec61e	disabled	keep disabled; document retired/pending confirmation	propose future archive/export or removal only after supersession evidence
4	Cron 4 from accepted inventory	capture in before-readback	disabled	keep disabled	propose future archive/export, redesign, or removal after identification
5	Cron 5 from accepted inventory	capture in before-readback	disabled	keep disabled	propose future archive/export, redesign, or removal after identification
6	Cron 6 from accepted inventory	capture in before-readback	disabled	keep disabled	propose future archive/export, redesign, or removal after identification
7	Cron 7 from accepted inventory	capture in before-readback	disabled	keep disabled	propose future archive/export, redesign, or removal after identification
8	Cron 8 from accepted inventory	capture in before-readback	disabled	keep disabled	propose future archive/export, redesign, or removal after identification
9	Cron 9 from accepted inventory	capture in before-readback	disabled	keep disabled	propose future archive/export, redesign, or removal after identification

Explicit non-actions

This plan does not include:

• cron re-enable
• unattended automation
• external sends
• provider/model mutation
• OpenClaw restart/update
• subagent expansion
• deletion

Stop here and wait for explicit approval.

[marcusglee11]

Verdict: APPROVE audit-only findings; REVISE before any cleanup execution

The audit-only pass is accepted as evidence for #109. No gated mutation was reported:

• no cron re-enable
• no new unattended automation
• no external sends
• no config/model/provider mutation
• no OpenClaw restart/update

Accepted findings:

• Cron inventory remains 9 jobs, all disabled.
• HEARTBEAT.md is non-operational / intentionally empty in effect, but should be made explicit in-file.
• TOOLS.md is a non-authoritative template in effect, but should be made explicit in-file.
• Stale route warnings are fail-closed historical route metadata, not active send capability.
• verify-telegram-latency-and-health-overlay has a lost/missing backing session warning.
• Stale running CLI task a0fbfffe... is outside Phase 4 — Clean Cabra/OpenClaw cron, heartbeat, and tooling authority state #109 core scope and should not be bundled into this cleanup.

Required correction to the execution plan:

• Treat all cron delete stale findings as candidate removal only, not approved deletion.
• Treat repair but keep disabled as a scheduler mutation requiring separate approval, because repair may alter payload, route, cadence, or target metadata.
• Do not combine file clarification with cron scheduler cleanup in the same first cleanup pass.

Approved next-slice recommendation:

Proceed next with files only, if the CEO explicitly approves:

1. Patch /home/cabra/.openclaw/workspace/HEARTBEAT.md to state it is intentionally non-operational and authorizes no heartbeat task, scheduler action, automation, or outbound delivery.
2. Patch /home/cabra/.openclaw/workspace/TOOLS.md to state it is a non-authoritative template and must not be used as live authority for tools, providers, models, cron, routes, sends, or subagent permissions.
3. Capture before/after readbacks and SHA256 for both files.
4. Post receipt to Phase 4 — Clean Cabra/OpenClaw cron, heartbeat, and tooling authority state #109.

Do not touch cron scheduler records in the files-only pass.

Cron cleanup should be a later, separately approved pass with:

• full UUID for all 9 jobs
• pre-cleanup scheduler export/readback
• rollback/export story before removal
• per-job action classified as one of: keep disabled unchanged, candidate removal, candidate repair while disabled, candidate redesign
• explicit route-safety statement for every retained/repaired job

Current per-cron classification for later pass:

• 24854304... LifeOS ingestion cadence: candidate removal; keep disabled until separately approved.
• 2c67a6e6... COO Brief (trial): candidate removal; keep disabled until separately approved.
• 309ba6db... close-hermes-bus-loop: keep disabled unchanged.
• 325a45f3... COO E2E cheap-default: candidate removal; keep disabled until separately approved.
• b468fcdd... coo-heartbeat: candidate redesign/repair while disabled; no repair yet.
• bde2edb1... COO E2E debug: candidate removal; keep disabled until separately approved.
• d3bb4ce7... verify-telegram-latency-and-health-overlay: candidate removal/archive; keep disabled until separately approved.
• d84897ee... Reading Status Ping: candidate removal; keep disabled until separately approved.
• db161705... Check Hermes review on agent-comms issue 18: candidate repair while disabled; no repair yet.

Explicit non-actions maintained:

• no cron re-enable
• no unattended automation
• no external sends
• no provider/model mutation
• no OpenClaw restart/update
• no subagent expansion
• no deletion
• no cron scheduler mutation
• no route/target mutation

Stop and wait for explicit CEO approval before files-only cleanup or any cron scheduler action.

[marcusglee11]

Phase 4 bounded implementation receipt

Authorization source: Telegram approval, Approved: fix #109 bounded slice yourself.

Scope executed:

• Captured before readbacks for HEARTBEAT.md, TOOLS.md, and OpenClaw/Cabra cron inventory.
• Applied documentation-only classification edits to:
  • /home/cabra/.openclaw/workspace/HEARTBEAT.md
  • /home/cabra/.openclaw/workspace/TOOLS.md
• Re-read files and cron inventory after edits.

File evidence:

• HEARTBEAT.md
  • before sha256: dac422286075ba178e9bae58154cc0ae8749a66854e438c9c58e8eb91f22c126
  • after sha256: 1bc14c150623293c2658df3dde5566389f8728895e00b98a081adc9b89b7d9a5
  • final classification: non-operational / intentionally empty
  • final meaning: no active heartbeat task is authorized; no scheduler job, unattended automation, outbound delivery, or send authority is implied; future heartbeat activation requires separate CEO approval.
• TOOLS.md
  • before sha256: 78f3e26b8625ea283c615cec291d4978da5f9f01df730628c5c42094418b8dc2
  • after sha256: dbee1d5e4589f81ba621bdce8685df6a967bce246caab0e5dd5959407eb67ae4
  • final classification: non-authoritative template / unconfigured
  • final meaning: not authoritative for live tools, providers/models, cron state, routes, send permissions, node access, or subagent/EA authority.

Cron inventory readback:

• Total jobs: 9
• Enabled jobs: 0
• Disabled jobs: 9
• Baseline matched accepted inventory; no stop condition triggered.

Per-cron disposition:

#	Stable ID	Name	State	Delivery/route note	Disposition
1	24854304-1b50-4ae0-bc46-d1be32a5b94b	LifeOS ingestion cadence	disabled	none -> last; fail-closed route warning	keep disabled; historical/disabled route metadata only
2	2c67a6e6-7d34-4681-a262-6939d2fa90d0	COO Brief (trial)	disabled	explicit Telegram route	keep disabled; retired trial pending future archive/export decision
3	309ba6db-4c0a-4324-bee0-bd77d4eec61e	close-hermes-bus-loop	disabled	explicit Telegram route	keep disabled; retired/pending confirmation
4	325a45f3-79dc-4521-9587-ca3bf59f739a	COO E2E cheap-default 20260219T055029Z	disabled	none -> last; fail-closed route warning	keep disabled; test artifact candidate for future archive/export
5	b468fcdd-5ff7-423d-b55c-e0b360a55cfd	coo-heartbeat	disabled	none -> last; fail-closed route warning	keep disabled; no heartbeat authority active
6	bde2edb1-7221-447b-a55a-743622a100ae	COO E2E debug	disabled	none -> last; fail-closed route warning	keep disabled; test artifact candidate for future archive/export
7	d3bb4ce7-f586-41f9-a6fc-4c7d7aa29bfb	verify-telegram-latency-and-health-overlay	disabled	explicit Telegram route; one-shot past job	keep disabled; stale verification job candidate for future archive/export
8	d84897ee-2908-4c8a-8806-1422690e7a34	Reading Status Ping (every 3 min)	disabled	none -> whatsapp:+61476261117	keep disabled; retired/pending future archive/export decision
9	db161705-3037-40c3-8b0f-93926af74a28	Check Hermes review on agent-comms issue 18	disabled	announce -> last; fail-closed route warning	keep disabled; stale watcher candidate for future archive/export

Stale route metadata disposition:

• Classified as historical/disabled route metadata.
• No route cleanup or target changes performed.

Explicit non-actions confirmed:

• Did not enable cron.
• Did not delete cron.
• Did not create unattended automation.
• Did not send external messages except this GitHub issue receipt.
• Did not change routes or messaging permissions.
• Did not mutate provider/model config.
• Did not restart or update OpenClaw.
• Did not modify subagent/EA authority.