Skip to content

v1.2 - Operational Discipline

Choose a tag to compare

View all tags
@jbrick2070 jbrick2070 released this 12 Apr 09:24
· 5 commits to main since this release
v1.2
2754ec4

v1.2 - Operational Discipline

14 new protocol rules derived from real production failures.

New Rule Categories

  • Operational Discipline (9-14): Completion verification, heartbeat, mirror freshness, env health, artifact manifests, iteration tagging
  • Session/Task Lifecycle (15-18): Session start/end, task ownership with TTL, file intent, atomic fixes
  • Conflict Resolution (19-22): Env change notification, canonical timestamps, dispute resolution, priority interrupt

Every rule traces to a specific failure during the OldTimeRadio v2.0 project (Claude + Antigravity on RTX 5080).

Service Restart Policy (Rule 20)

  • Projects define a RESTART_POLICY in HANDSHAKE.md with triggers, no-restart conditions, and exact restart procedure
  • Operator agents execute restarts autonomously -- human never restarts the service manually
  • Integrates with ENV_CHECK: failed health check triggers restart, re-check, then proceed or escalate
  • Rule Zero: source code changed = restart, config/data changed = no restart
  • Hot reload attempted first; full kill-wait-relaunch as fallback

Git Push Protocol (Rule 21)

  • 5-method escalation: GitHub API (most reliable) > git+token > git+SSH > Windows MCP > human command block (last resort)
  • Full GitHub API recipe with code: blob > tree > commit > update ref
  • Token management: never commit tokens, never log to shared files
  • Lockstep verification mandatory after every push
  • Common failure mode fixes (index.lock, credential prompts, BOM, timeouts)
Assets 2
Loading