Zyeta enterprise operations
How a change becomes a published, attested release — and who is allowed to make each move. Every diagram here is generated from the JSON sources in enterprise/diagrams/, so a diagram cannot drift from the description without the build failing.
- Required checks
- 20 contexts on main
- Controls
- 38 each with evidence
- Environments
- 4 1 human-gated
- Agent merge rights
- 0 by design
- Plan
- Team $4 / user / month
Start here
Four layers
The repository already verified changes and published releases well. What was missing was identity, approval and proof. Those are the three layers added on top of the existing pipeline, not a replacement for it.
┌─ L4 Oversight ──────────────────────────────────────────────────────────┐
│ drift check · audit log · spend limits · agent register │
├─ L3 Identity & approval ────────────────────────────────────────────────┤
│ org settings · teams · rulesets · environments · CODEOWNERS │
├─ L2 Security gates ─────────────────────────────────────────────────────┤
│ codeql · dependency review · sbom · action pins · push protection │
├─ L1 Existing verification & delivery (unchanged) ───────────────────────┤
│ ci.yml · release.yml · dsh.yml · Pages / Cloudflare deploys │
└──────────────────────────────────────────────────────────────────────────┘
Two rules that explain most of the design
- Agents and humans take the same path. An agent opens a pull request; a human approves it; the ruleset does not care who authored it. There is no "trusted automation" bypass, because that bypass is what a compromised agent uses.
- One gate, one owner, one piece of evidence. A control nobody can point at a run for is a wish. Every row in the control matrix has an evidence command, and
verify.shturns "we think it is configured" into a pass or a fail.
How this site is built
Content is markdown in enterprise/site/content/; the builder is a zero-dependency Node script. Diagrams come from enterprise/diagrams/*.json via the diagram CLI.
node enterprise/diagrams/build.mjs # JSON → validated HTML + PNG
node enterprise/site/build.mjs # markdown → site/dist
Adding a page is one file: drop content/<name>.md with a frontmatter block, rebuild, and it appears in the sidebar in order sequence with previous/next links.