Skip to main content

Operator Quick Reference

This page fits on one screen. It answers the most common operator questions in one place.

Where am I?

git rev-parse --show-toplevel
# → D:/Projects/ASF50-Platform/ASF50

git branch --show-current
# → feature/asf50-docs-portal-v1 (or main / repair / …)

git rev-parse HEAD
# → 1cf7b5db32302ec39daa39631638e508676994c7

What goal is running? What state is it in?

.\scripts\goal-runner\program-status.ps1
.\scripts\goal-runner\goal-status.ps1 -GoalId <GOAL_ID> -RuntimeRoot …

Look for current_state in the JSON output.

What does the agent need from me?

.\scripts\goal-runner\goal-gate.ps1 -Action list -RuntimeRoot …

For each open gate, the gate's scope and reason tell you what is required.

Should I click Merge?

No — not from chat. Merge only after:

  1. The orchestrator has emitted a MERGE_APPROVAL gate at the exact PR head.
  2. You have submitted an approving GitHub review.
  3. The orchestrator has ingested the review.

Then the autopilot performs the governed merge.

When do I sign?

When the orchestrator emits a PRODUCTION_PROMOTION gate. Sign offline with:

ssh-keygen -Y sign -f ~/.ssh/asf50_owner_ed25519 -n <namespace> <payload.txt>

The orchestrator verifies with ssh-keygen -Y verify before consuming the gate.

Where is the canonical runtime?

D:\Projects\ASF50-Platform\ASF50\scripts\goal-runner\local\runtime\goal-state.sqlite3

This is the local-dev runtime. Production deployments move the runtime root outside the repo.

What must never be modified directly?

  • goal-state.sqlite3 (and any other runtime DB).
  • Historical receipts (evidence/IMP-XX/...).
  • Historical gates (evidence/IMP-XX/...).
  • Production promotion evidence.
  • Frozen baseline surfaces (see agent-harness/governance/).
  • git reset, git restore, git clean, git stash, git prune.

How do I know production is live?

.\scripts\goal-runner\goal-status.ps1 -GoalId ASF50_PROGRAM_COMPLETION_001 -RuntimeRoot …

Look for current_state: PROGRAM_PRODUCTION_CERTIFIED. Alternatively, the production ticket consumption receipts in evidence/<GOAL_ID>/deployment_health.txt.

What is the next owner gate?

.\scripts\goal-runner\goal-gate.ps1 -Action list -RuntimeRoot …

The first open gate is the next owner action.

Decision table

SymptomAction
Open MERGE_APPROVAL at exact headApprove in GitHub UI.
Open PAID_MODEL_DISPATCH_APPROVALRun goal-gate.ps1 -Action approve -Source owner-cli ….
Open PRODUCTION_PROMOTIONSign the ticket offline; submit to the orchestrator.
subject_sha mismatchRe-base the work; re-open the PR; re-issue the gate.
ticket replay errorThe ticket has already been consumed; issue a fresh ticket.
CI failureInspect .github/workflows/ history; fix or rerun.
Agent over-stopReject the over-stop and re-dispatch.
Adapter timeoutRe-dispatch; check network.
Runtime split-brainRun goal-doctor.ps1; reconcile.
Deviation detectedAcknowledge; open repair goal.
Stale gateRe-issue the gate at the current HEAD.