Governed standards, controlled explanations, synthetic examples, and learning paths. Content marked Preview is not yet an accepted standard.
Public or controlled learning resources for understanding the framework, language, standards, and practice.
Inspect current definitions, principles, learning paths, synthetic examples, Practice Mat guidance, and versioned standards. Each resource identifies whether it is explanatory, Preview, candidate, or accepted.
No customer evidence or private organizational knowledge belongs in this library.A governed record owned by the customer and created from that company’s authorized evidence and decisions.
Trace approved knowledge to its source evidence, Steward disposition, organizational scope, effective version, superseded understanding, related Decisions, and permitted audience.
The customer controls access, retention, classification, permitted AI use, and authoritative status.Markdown with a defined role and scope can carry approved knowledge into an organization’s permitted AI environment without surrendering governance. Each output is designed to retain its audience, provenance, version, classification, effective date, and evidence links.
A frontline worker, supervisor, executive, or 5AO receives the context appropriate to the work and authorization.
A role manifest defines the intended reader, authorized scope, necessary context, excluded information, and actions the output may support. The same source can produce different governed views without changing the underlying record.
Role scope limits exposure; it does not rewrite the source or manufacture authority.The reader can distinguish accepted knowledge from assumptions, unresolved questions, and superseded understanding.
Every output carries provenance, status, version, effective date, confidence, unresolved Questions, and links back to the governed records that support it.
A polished explanation must never conceal uncertainty or convert a candidate into accepted knowledge.Controlled Markdown remains useful across approved tools instead of trapping organizational knowledge in one interface.
A governed Markdown package includes content people can read plus a structured manifest that approved AI tools can read. This preserves audience, version, classification, citations, and evidence references.
Portability applies only to approved content moving into an environment permitted by the customer.The company governs access, retention, permitted use, and the authoritative status of its knowledge.
The customer names the owner, approving authority, audience, retention rule, release channel, AI permissions, and withdrawal or supersession process for each controlled output.
5 Angles supplies the governance pattern; the company retains sovereignty over its knowledge.The Knowledge Library is more than document retrieval. It preserves the Decisions, Commitments, evidence, versions, relationships, and accepted Outcomes that explain how the organization’s understanding developed.
Separate Reality, Signal, evidence, claim, candidate, and accepted object.
Follow one synthetic observation from the moment an individual notices Signal through evidence registration, AI proposal, and Steward acceptance. Inspect which fields and authority change at each state.
Boundary: evidence supports an understanding of Reality; it never becomes Reality itself.Understand how Discussion becomes an authorized Decision and possible Commitment.
Walk through a Discussion that transforms assumptions into shared expectations, an authorized choice, and either a recorded Commitment or a governed Decision to remain at Peace.
Boundary: QBox records authority; it does not create or transfer organizational authority.Follow changing Customer and Supplier roles across Commitments, processes, companies, and the Tower.
Inspect a relationship map in which the same team is a Supplier in one Commitment and a Customer in the next. See how expectations, acceptance, Quality, and Value remain attached to the correct relationship.
Boundary: Customer and Supplier are contextual roles. They are not permanent labels.Make Customer expectation, Supplier acceptance, evidence, measurement, and boundaries explicit.
Examine a Value Contract containing the named Customer, accountable Supplier, expected condition, acceptance test, timebox, evidence requirement, and change history.
Boundary: a Commitment requires a named accountable individual with proper organizational authority.Trace finished execution to Customer expectation and accepted Value.
Use a worked example to distinguish activity, finished execution, Quality, Potential Value, and Realized Value. Inspect the baseline, counterfactual, measurement period, attribution, confidence, and Customer acceptance.
Boundary: Potential, Committed, and Realized are mutually exclusive states. They are not amounts to stack.Review candidates and exceptions without inventing authority.
Practice accepting, correcting, rejecting, deferring, merging, splitting, and Requesting Evidence on synthetic candidate objects while preserving the source and every disposition.
Boundary: AI proposes; an authorized Steward governs what becomes an accepted object.Understand what may move upward and what must remain within the company.
Compare a company record with its separately approved Tower output. Inspect provenance, classification, aggregation, authorization, and the information deliberately excluded from portfolio movement.
Boundary: raw evidence, PII, IP, prompts, and rejected candidates remain inside the company boundary.Practice a thoughtful path from Story through returned witness.
Follow a complete Kata: witness Signal, tell the Story, inspect evidence, discuss choices, make an authorized Decision, execute in Reality, and return to bear witness.
Boundary: the Dojo supports thoughtful choice; it is not a coercive script and execution occurs in Reality.A future governed network for learning, practice, contribution, qualification, and institutional capability. Its detailed structure and availability remain under development.
