🛡️ 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.
• Governance/Proposal — the proposal intake: a proposer creates one in their OWN space ({you}/_Proposals/{id}); once the STANDARD's authority.proposers admits them it files the activity as system on their behalf, with a Viewer grant on it for them.
• 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).

Contents

Where to start

• Design — the architecture: events, standards, gates, signatures, one executing identity.
• Guide — proposing, reviewing, signing, and reading an activity.