agentic-ops-core

name	agentic-ops-core
description	Shared reference for the agentic-ops cluster: the evidence-first operator loop (resolve surface → read live state → smallest reversible action → prove it → report exact status), the surface taxonomy, the status-word vocabulary, and the secrets/PII guardrails every operator spoke obeys. USE WHEN operating any live external surface — inbox, repo, tracker, billing, docs — or before any send/push/refund/mutation in this cluster.
cluster	agentic-ops
version	1.0.0

Agentic Ops Core

Shared model for the agentic-ops cluster. Every spoke — comms, code-host, tracker, knowledge, billing, audit — runs the same loop over a different surface. Keep that loop and its vocabulary consistent here so no spoke claims state it didn't prove and no spoke widens a mutation silently.

1. The operator loop (this cluster's defining model)

Operations are read-before-write and prove-before-claim. Every spoke walks the same five steps; only the surface changes:

Resolve surface ──> Read live state ──> Smallest reversible action ──> Prove it ──> Report exact status
   (which?)            (inspect)           (draft / narrow / no-op)      (evidence)     (one status word)

1. Resolve the exact surface. Which mailbox/account, repo+branch, thread, tracker item, billing customer, or store. Ambiguity here is the #1 source of wrong actions. → every spoke opens with this.
2. Read live state before mutating. Inspect the thread, diff, ticket, invoice, or config — never act from memory when the live surface is readable. → , , .