Plans before delivery
Company policy and architecture become detailed plans a team can work from and check against, written before the first commit rather than recovered afterwards.
Policy, Architecture and Audit
Decide the rule before the work. Prove it after.
Tzu is context super-management: it turns the policy and architecture a company has already agreed on into detailed plans a team can check against, and keeps the evidence that the delivered system followed them.
Policy, Architecture and Audit
Context, plans and governance evidence, decided before the work and proven after it.
Context super-management that turns company policy and architecture into detailed, checkable plans before delivery begins. It then verifies governance and keeps continuous compliance evidence across code and infrastructure.
- Context super-management: one governed source of plans, standards and decisions
- Governance verification across code and infrastructure, not documents alone
- Continuous compliance evidence, retained as an auditable record
Status
Beta
Every product delivers against a written rule, and the evidence that it did exists without anyone assembling it.
The problem
Governance that arrives too late to change anything
In most organisations the rules exist and the delivery happens, but the two meet only at review time. An architect writes a standard, a team builds for three months, and an auditor arrives afterwards to reconstruct whether the standard was followed. What that review produces is an opinion assembled by hand from tickets, commits and memory.
The cost is paid twice. Teams rework finished systems to satisfy a rule nobody applied at the start, and the organisation still cannot state, on any given day, which of its systems currently comply with which of its own decisions.
How it works
One governed source, checked in both directions
Verification against the system
Governance is verified against code and infrastructure as they actually are, not against the documents that describe how they were meant to be.
Evidence that accumulates
Compliance evidence is retained continuously as an auditable record, so proving a system followed its rules costs a query rather than a project.
Where it runs
Inside the infrastructure you already control
Tzu runs where the work runs: on your own hardware, in a cloud account you own, or inside the borders of one country when that is the requirement. Plans, decisions and evidence are the most sensitive record an engineering organisation keeps, and this product exists because that record often cannot be handed to a service somewhere else.
The constraint came first and the reach followed. A team under no such restriction gets the same product, deployed the way it prefers, with nothing given up for a limit it does not have.