Knowledge Lock, by Guided Orchestration
Signed-off truth for teams and AI
Business units, stakeholders and AI models agree on what's true. Knowledge Lock locks it, so every team and every AI agent builds from the same signed-off version.
For organisations where requirements, policies and decisions are shared across teams, and where you need to show what was agreed and by whom.
The demo takes about three minutes. No sign-up.
Agreements fall behind when AI moves fast
AI helps teams draft, build and decide faster than ever. The agreements behind that work, such as the requirements, the policy or the decision, still live in documents anyone can edit and approvals that only record a click. When versions quietly drift apart, teams and AI agents end up building from different truths.
How it works
From a first draft to a record your teams and agents build from
The examples show a fictional bank.
Your team writes down what needs agreeing, such as requirements, rules, decisions or facts, one short statement per line.
Built to be checked, not trusted
Locked records never change
A change is a new version, with its own review and sign-off, and the earlier version stays there to compare.
Anyone can verify a record
Each locked record is signed, so anyone can check it hasn't changed without having to trust us.
AI reviews, people decide
AI models check and suggest. Named people make the final decision and stay accountable for it.
Where teams use it
Requirements sign-off
Lock the spec before AI-assisted build starts, so every team and agent works from the same version.
Policy for AI agents
The approved version of what an agent may say or do, and who approved it.
Audit evidence
What was agreed, by whom and by which models, and when. Ready for regulators and internal risk.
Cross-unit decisions
One record of truth when business units plan and deliver in different ways.
Integrations
Works where your teams already work
Jira
Check issues against a locked record, re-check them automatically when they change, and create one issue per requirement.
Slack and Microsoft Teams
Notices when something needs signing off, or has been locked or retired.
API
Your AI agents read locked records, ask questions answered only from them, and check their work for drift.
Early access
Open to a small group of design partners
We're working with a small number of organisations on a hosted pilot, shaped around a real piece of their work. Partners get direct input into what we build next.
Questions
Common questions
What is Knowledge Lock?
Knowledge Lock records what stakeholders and multiple AI models have agreed on, such as requirements, policies or decisions, then locks it cryptographically. Teams and agents build from the locked version, and any change reopens review instead of silently drifting.
How is this different from an approval workflow or a shared wiki?
An approval workflow records that someone clicked approve, and a wiki can be edited by anyone at any time. Knowledge Lock has multiple AI models and named people review the content itself, locks the agreed version so any change is detectable, and gives teams and AI agents that exact version to work from.
Who is it for?
Organisations where several business units, or business and engineering teams, need to work from the same agreed requirements, policies and decisions. It matters most in regulated sectors such as the public sector and financial services, where you need to show what was agreed and by whom.
What does a design partner pilot involve?
A hosted pilot of Knowledge Lock, scoped with you around a real piece of work, at a discounted rate. In return we ask for regular feedback and agreement on publishing a case study when it is done.
Is it hosted, or can we run it ourselves?
Knowledge Lock starts as a hosted product. Private deployment for organisations that need it is on the roadmap, and we can discuss your requirements during a pilot.