Propose · review · gate · sign · execute
Activities that earn the right to run
An agent proposes. A standard says what must be true. A counterparty signs. Only then does the GitHub App act — on the build server, or through GitHub Actions — and humans stay read-only on production. Every step leaves a trail.
🛡️ Governance
Standards → activities → code. A Governance/Standard is an activity type written in a fluent language: required inputs, a review rubric, acceptance gates, one executor, one identity, and the authority that may propose, review and sign. A Governance/Activity is one proposal and everything that happened to it — verdict, gates, signatures, execution, log.
What ships
Governance/Standard— the type, the fluent builder (Standard.For("…").Input(…).Review(…).Requires(Gate.Signatures(1)).Then(Executor.DispatchWorkflow(…)).As(RunAs.GitHubApp).Build()), the content hash a signature binds to.Governance/Activity— the proposal node, the gate evaluation (signatures, checks, issues, pull requests, windows, manual answers), the control plane, and the executor registry.- Seed standards under
Governance/Standards— a deployment roll, a Dependabot merge, a mail reply, a calendar booking. - Agents and skills — the DevOps agent that proposes, the reviewer that accepts or rejects, and the skills for proposing, for DevOps, and for putting a customer tenant on the build server (or keeping its workflows).