Zyeta Enterprise operations

Diagrams

Six diagrams, each generated from a JSON source in enterprise/diagrams/ and validated by the diagram CLI before it is published. The images below are exported from the same SVG the interactive artifact renders, so a change to the source changes both.

node enterprise/diagrams/build.mjs    # validate → render → export

Team hierarchy and repository roles

Team hierarchy tree Open interactive ↗
Tree diagram of teams and their repository roles
Child teams inherit the parent's access and can never have less — which is why engineering sits at read.

Enterprise control plane

Zyeta enterprise control plane architecture Open interactive ↗
Architecture diagram: organization, repository and distribution boundaries
Three boundaries carry the design: the organization owns identity and approval, the repository only accepts a verified change, distribution ships proven bytes.

Merge gate

Merge gate — pull request to release workflow Open interactive ↗
Workflow diagram: verification and security tracks converging on human approval
Verification answers "does this change work"; security answers "is it safe to ship". Neither can be skipped by claiming the other passed.

Release lifecycle

Release lifecycle lifecycle Open interactive ↗
Lifecycle diagram: release states from tag to attestation
A bad release is superseded, never rewritten: tags are immutable, and the notifier manifest is what actually protects users.

Release approval sequence

Release approval sequence sequence Open interactive ↗
Sequence diagram: tag, approval gate, publication and attestation
Provenance reads the tagged blob, not the uploaded file, so a swapped asset is rejected instead of silently attested.

Thirty-day rollout

Thirty-day rollout timeline Open interactive ↗
Timeline diagram: thirty-day governance rollout
Dates are illustrative; the order is the requirement. Rulesets land after the checks they require have reported once.