DOCS
What ZAK does.
Capability envelope: constitutional law, executors, receipts — and explicit non-claims.
More concretely:
ZAK does four things — and only these four things.
ZAK records reality
ZAK ingests facts from authority systems:
- • what code changed (GitHub)
- • who gained access (Okta)
- • what was approved (Jira)
- • what ran or broke (AWS)
It does not interpret them.
It does not prioritize them.
It does not react automatically.
It records them immutably.
Think of ZAK as a flight recorder, not a pilot.
ZAK evaluates decisions against constitutions
When a decision is about to be made (or was just made), ZAK:
- • evaluates it against the active constitution
- • checks invariants, boundaries, and guarantees
- • determines what is allowed, constrained, or blocked
This is not judgment.
This is mechanical evaluation.
Like a compiler checking code against a spec.
ZAK produces receipts
For every governed action, ZAK can produce:
- • the constitution version + hash
- • the authority signals in effect
- • the model and execution context
- • the CD tests that back the guarantees
- • a replayable decision trace
This is the core value.
ZAK answers "can you prove this was acceptable at the time?"
ZAK creates institutional memory
Over time, ZAK becomes the place where an organization can say:
- "This is what we enforced"
- "This is what changed"
- "This is why it was allowed"
- "This is what we relied on"
Not opinions.
Not summaries.
Evidence.
What ZAK explicitly does not do (and why that matters)
ZAK does not:
- • choose what you should do
- • optimize behavior
- • recommend policies
- • auto-correct mistakes
- • replace human judgment
Because the moment it does, it becomes:
- • disputable
- • subjective
- • legally ambiguous
- • impossible to defend later
Institutions don't get sued for decisions.
They get sued for not being able to explain them.
ZAK exists for the explanation.
The one-sentence answer (keep this handy)
If someone asks:
"So what does ZAK actually do?"
You answer:
ZAK doesn't make decisions.
It makes decisions provable, replayable, and defensible — across time, people, and systems.
If they still don't get it after that, they're not your customer.
Why this framing is powerful
This answer:
- • shuts down "why doesn't it auto-fix…" requests
- • aligns legal, engineering, and platform teams
- • positions ZAK alongside GitHub, not above it
- • makes the product boringly indispensable
You're not building intelligence.
You're building accountability infrastructure.
And that's why this will be needed sooner than people think —
because AI scales decisions faster than institutions can explain them.
You're building the thing that lets them keep up.