From scattered institutional memory to judgment available when the decision needs it.
Before, teams reconstruct the evidence, precedent, and authority behind every consequential decision. After, governed role judgment is available inside the decision workflow, with provenance and human ownership attached.
- Someone hunts for the policy, the precedent and the prior determination.
- The rationale behind the last decision is reconstructed from memory.
- The decision then waits again for an approval slot.
- Prior reasoning is structured once and reused under governance.
- Evidence and its provenance travel with the answer.
- Review and escalation sit inside the workflow, not after it.
The business consequence is fewer repeat reconstructions and decisions organized around evidence rather than calendars.
How the change happens: Ingest, Twin, Operate.
Only after the change in operating state does the product matter.
Ingest
Authorized enterprise evidence enters under the permissions and controls of the selected deployment architecture, and is reconstructed into structured decision episodes.
Twin
Episodes become a governed, role-specific judgment model: principles, thresholds, exceptions, precedent, authority boundaries and escalation rules, connected by the Role Wisdom Graph.
Operate
The twin becomes available through One-Press Huddle and other governed interfaces. Each response carries evidence, provenance, permission and policy context, and resolves to Recommend, Escalate or Safe Decline.
Ingest
Evidence is designed to enter under the permissions and controls of the deployment pattern selected during pilot scoping.
Sources
- Prior decisions and their outcomes
- Policies, standards and procedures
- Committee minutes and determinations
- Approved communications and memos
- Systems of record and structured data
Decision Episodes
- The question that was asked
- The evidence that was considered
- The constraints that applied
- The authority that decided
- The outcome and the rationale
Controls at intake
- Source-level entitlements preserved
- Classification retained with the record
- Provenance attached to every episode
- Perimeter set by the deployment pattern chosen during pilot scoping
Twin
Episodes become a governed, role-specific judgment model connected by the Role Wisdom Graph.
What the twin encodes
- Principles the role applies consistently
- Thresholds that change the answer
- Exceptions and the conditions that justified them
- Precedent and how it was weighted
- Authority boundaries and delegated limits
- Escalation rules and named validators
What the twin is not
- Not a clone of a specific person
- Not a digital replica or voice copy
- Not an autonomous employee
- Not a document search interface
- Not a decision maker: a human owns the decision
Operate
The twin becomes usable through One-Press Huddle and other governed interfaces.
Evidence is sufficient, policy checks pass and the answer stays inside the role's authority.
The decision exceeds the role's authority or needs a named human validator before it moves.
Evidence or permission is insufficient. The platform says so and routes the decision to a human.
Every response carries evidence, provenance, permission and policy context. Where evidence or permission is insufficient, the design calls for a Safe Decline rather than an unsupported answer.
Start with the decision that waits most often.
In one working session, we map where a recurring decision stalls today, which role holds the judgment, what evidence and approvals govern it, and what the accountable after state should be.