Capabilities describe the work
Definitions capture the artifacts, gates, policies, screens, and evidence each product needs.
ZAK is not another workflow builder. Teams work in focused products while the platform checks authority, evidence, lifecycle gates, and receipts before high-stakes state can change.
Standards and internal policies become checks people can inspect, not documents everyone forgets.
ZAK knows who can approve, who must review, and which role is accountable for each action.
Work can only move forward through the governed execution boundary.
Each important decision leaves evidence your team can replay, seal, and audit later.
Full map: see how outside standards become internal checks, then show up inside the products teams actually use.
Full map: see how outside standards become internal checks, then show up inside the products teams actually use.
Dimmed nodes are simply outside the current path. They can still be used by another governance profile or organization setup.
Total sovereignty
In a black-box AI market, ZAK keeps the operating boundary separate from the model. Your organization chooses the AI provider, deployment model, and data custody posture. ZAK keeps the result authorized, evidenced, and inspectable.
Local model, private instance, managed provider, or global LLM.
The platform provides the checks; the model provides the cognitive work.
Data, context, and organizational intelligence are not the product.
Definitions capture the artifacts, gates, policies, screens, and evidence each product needs.
The map can show what is possible, but /zak/execute still checks passport, authority, evidence, and current governance state.
The UI reads manifests and receipts. It helps people act, but it never becomes the source of truth.