Skip to content

Operational Checks

Lifecycle class: recurring read-only verification.
Authority: BluTown / Gas Town runtime governance.
Default mode: inspect only; no mutation, no cleanup, no restart, no push.

Heartbeat checks exist to detect drift, blockage, and degradation early. They do not create workarounds.

Preconditions

Before running heartbeat:

  • verify active repo / workspace
  • verify runtime identity via gt prime
  • verify task context via bd where applicable
  • query directives with qmd
  • check Cedar policy before any escalation or mutation
  • record evidence path / timestamp

If any authority is unavailable, report COMMAND_GAP, POLICY_GAP, or RIG_GAP.

GitLab

Check:

  • MR conflicts
  • failed or blocked pipelines
  • stale drafts
  • approval blockers
  • protected branch drift
  • release branch divergence

GitLab merge requests can be blocked by conflicts, approvals, or failed CI, so heartbeat should report the blocker class rather than attempting repair. oai_citation:0‡GitLab Docs oai_citation:1‡GitLab Docs oai_citation:2‡GitLab Docs

Platform

Check:

  • OpenClaw health
  • Gas Town runtime status
  • Beads persistence
  • QMD directive integrity
  • Dolt latency / availability
  • convoy queue health
  • active bead consistency

Forbidden during heartbeat:

  • restart-first recovery
  • direct Dolt filesystem edits
  • manual SQL mutation
  • duplicate queue / ledger creation

Drupal

Check:

  • DDEV health
  • Drush status
  • module integrity
  • config drift
  • route failures
  • cache-rebuild readiness
  • local service availability

DDEV provides direct project-scoped Drush access for Drupal projects, and Drush core:status reports Drupal and environment status. Use these as read-only diagnostics unless a mutation packet authorizes repair. oai_citation:3‡DDEV Docs oai_citation:4‡DDEV Docs oai_citation:5‡Drush

Governance

Check:

  • ContractPlane SDK reachability
  • compliance-engine health
  • Cedar evaluation path
  • cedar-policies availability
  • policy decision logging
  • trace / receipt emission
  • schema validation status

Cedar is the authorization policy authority; heartbeat should verify that authorization decisions can be evaluated, not bypass or replace policy. oai_citation:6‡Cedar Policy Language Reference Guide oai_citation:7‡Cedar Policy Language Reference Guide

Product

Check:

  • ContextControl authority health
  • runtime diagnostics
  • asset delivery
  • AG-UI / SSE surface availability
  • evidence export path
  • cache / token-budget signals
  • customer-facing route health

Output contract

Every heartbeat must produce:

```heartbeat_receipt: status: PASS|DEGRADED|BLOCKED|DRIFT_DETECTED timestamp_utc: "" operator: "" runtime_identity: "" checked_surfaces: [] failures: [] drift: [] evidence: [] mutations_performed: false next_packet: ""