KF-5001 · Canonical Vertical Slice

One governed knowledge object, walked from capture to retirement — the "Hello, World!" of Knowledge Foundry

Exemplar (Illustrative) · Draft · v0.1 · 11 min read

Instantiates, on one Operational Knowledge Object:
   Canon (KF-1000) · Lifecycle (KF-2001) · Materiality (KF-2003)
   · Reference Architecture and its domains (KF-3000–3005)
   · Integration (KF-3006) · Conformance (KF-3007) · Authority (KF-3008)

Programming has a tradition: before the language reference, a tiny complete program — “Hello, World!” — proves the language, compiler and runtime work together, and lets a newcomer see the whole shape of a thing before learning its parts. This document is that program for Knowledge Foundry.

It takes one Operational Knowledge ObjectOperational Knowledge Object — the unit of design: a versioned representation together with its attached evidence, justification and acceptance-state (KF-1101). The system governs the object, never "knowledge itself". Vocabulary → and follows it from the moment it enters the system to the moment it leaves, showing at every step which services act on it, which records it leaves behind, which gates and controls it must pass, who holds the authority to make it consequential, and how its conformance can later be reconstructed. The reader never has to swap objects out of mind.

This document teaches Knowledge Foundry, not the four-day week. The subject is incidental. A reader should finish understanding how governed knowledge works — not holding a view on working hours. Like KF-3009, KF-5001 introduces no new architectural concept; it only instantiates concepts defined in their home documents, cited as it goes.

The example is a Knowledge Brief — a governed statement that answers one consequential question — because a brief is the simplest object that still exercises the whole architecture: several kinds of evidence, genuine counter-evidence, an authority that must accept reliance, and a life that continues after acceptance.

1 · The Object

Knowledge Brief KB-4DW-01 — “Should our organisation move to a four-day working week?”

That single classification — A3 — will quietly govern how deep every later step must go. Hold it in mind; §6 returns to it.

2 · The Guided Journey

The object advances one lifecycle stage at a time (KF-2001). At each stage below: what happens to the brief · the services that act (KF-3003) · the records it emits (KF-3004) · the gate and controls it passes (KF-3005) · the conformance dimension it exercises (KF-3007 §6). Every record named is emitted by the act itself — nobody stops to fill in a separate form (KF-3006 §9).

Capture — state: Candidate

The question is posed and candidate material is admitted: the Iceland public-sector trials, the UK 2022 pilot, two single-firm case studies, several peer-reviewed studies, and our own retention and output data. Capture is deliberately permissive — nothing is trusted yet — but one thing cannot be deferred: origin. Each source is recorded with where it came from. Services: Object Registry (SVC-01), Provenance (SVC-15). Records: Identity Record (KB-4DW-01), Intake Record, Provenance Seed. Gate: GATE-REG-01; controls: identity resolution and duplicate detection (CTRL-ID-01/02). Dimension: Structural. Authority: Creation (the Steward) — light, because nothing is yet relied upon.

Structure — state: Structured

The raw material is given form: the question, the candidate claims, the sources and their relationships are made inspectable. The object can now be reasoned about. Service: Representation (SVC-02). Records: Structured Representation, Metadata, Relationship Map. Gate: GATE-STR-01. Dimension: Structural.

Evaluate — state: Evaluated

Each piece of evidence is assessed for quality — and they are not equal. The Iceland and UK pilots are large and externally evaluated; the single-firm cases are vivid but weak; our internal data is primary but short-horizon. The counter-evidence is admitted here, not buried: reverted pilots, volunteer-firm self-selection, coverage costs in customer-facing roles. Services: Evaluation (SVC-04), Evidence (SVC-03). Records: Evidence RecordsEvidence record — the durable record that a material obligation or decision was discharged; wherever possible emitted by the governed act itself (KF-3004 §5.2). Vocabulary →, Quality Assessment, Evaluation Verdict, Counter-evidence Records. Gate: GATE-EVA-01; controls: evidence presence, evaluation completion, counter-evidence visibility (CTRL-EVD-01/03, CTRL-EVA-01). Dimension: Evidence.

Justify — state: Justified

The reasoned case is assembled. Claims are linked to their supporting and defeating evidence; assumptions are written down (“our role mix resembles the pilot firms; productivity means output-per-week; the window is ≥ 6 months”); an epistemic status is set:

Warranted for a bounded trial among knowledge-worker teams under the stated assumptions — not yet warranted for permanent, organisation-wide adoption. Counter-evidence and the sector-dependence claim remain attached.

Service: Justification (SVC-05). Records: Justification Record, Assumption Record, Rationale Record, Epistemic Status Record. Gate: GATE-JUS-01; control: justification completeness (CTRL-JUS-01). Dimension: Evidence. Because the object is A3, this stage also draws an independent reviewer (§6) — an A1 note would not have.

Accept — transition; state: Accepted

Now the decisive act, and the one the whole architecture is built around: justification is not acceptance. The brief is well-warranted, but warrant is not reliance. The Executive Committee — not the author, not the reviewer — decides that the organisation will rely on it, and fixes the scope of that reliance: a six-month trial for knowledge-worker teams, not permanent adoption. Service: Authority and Acceptance (SVC-06). Records: Acceptance Record, Scope-of-Reliance Record. Gate: GATE-ACC-01; controls: authority mandate and acceptance validity (CTRL-AUT-01, CTRL-ACC-01). Dimension: Authority. The acceptance record — naming the authority, the scope and the date — is the evidence that acceptance occurred (§4).

Operationalise — state: Operational

The accepted brief is turned into something the organisation can act on: a recommendation to run a six-month four-day-week trial for knowledge-worker teams, measured on output-per-week and retention, linked back to the warrant that justifies it. Services: Operationalisation (SVC-12), Release (SVC-10). Records: Actionable Form, Warrant Linkage, Release Record. Gate: GATE-REL-01. Dimension: Governance.

Govern — state: Governed

The object is given an owner and a review schedule so its legitimacy is maintained, not assumed. Currency conditions are set: a new major study or the trial’s own results will trigger review. Service: Stewardship and Review (SVC-07). Records: Stewardship Assignment, Review Schedule. Gate: GATE-REV-01. Dimension: Governance.

Apply — state: in use → outcomes

The recommendation informs the actual trial decision. Its use is recorded, and the trial’s results — output held steady, retention rose, two client-facing teams struggled — return as outcomes. Service: Application and Outcome (SVC-13). Records: Application Record, Explanation Record, Outcome Record, Feedback. Gate: GATE-APP-01. Dimension: Behavioural.

Evolve — state: Next Version

The trial’s outcomes are new evidence. The brief re-enters at Evaluate, its claims are re-justified against real internal data, and — because a new version does not inherit warrant — it passes through Acceptance again. Version 2 recommends extending the trial for knowledge-worker teams and excluding client-facing teams pending a different approach. Service: Version and Lineage (SVC-09). Records: Version Record, Change Record, Lineage Record. Gate: GATE-EVO-01. Dimension: Lifecycle. The predecessor is not overwritten; v1 and v2 are linked.

Supersede / Retire — state: Historical

A year on, the brief is folded into a broader Flexible Working Framework that governs four-day weeks, hybrid and compressed hours together. KB-4DW-01 is superseded — its successor linked, its history preserved append-only. Had the idea been abandoned instead, it would have been retired with the reason recorded. Either way, nothing is erased: the organisation can still reconstruct, years later, what it once decided and why. Service: Retirement and Preservation (SVC-14), with Version and Lineage (SVC-09). Records: Supersession Link (or Retirement Record), Historical Object Record. Gate: GATE-RET-01. Dimension: Traceability.

What only the whole journey shows. Every record above was emitted by doing the step, not by a separate filing exercise — the journey is the evidence trail. And the six lifecycle invariantsLifecycle invariant — one of the six continuously checkable properties of an object at every instant: single identity, attributable transitions, justified transitions, inspectable transitions, provenance always present, lineage preserved (KF-2001). Vocabulary → held at every step: one identity throughout, every transition attributed and justified and inspectable, provenance present from Capture, lineage preserved through Evolve and Supersession.

3 · The Same Story as a State Machine

Candidate ─▶ Structured ─▶ Evaluated ─▶ Justified ─▶═ ACCEPTED ═▶ Operational
                                                                      │
                                            Governed ◀────────────────┘
                                                │ Apply → outcomes
                                                ▼
                                            Next Version ──▶ (re-Accept) ──▶ Operational
                                                │
                                                ▼
                                            Historical  (superseded, lineage preserved)

Every arrow is a governed transition: recorded, attributed, justified. There are no silent moves — that is the single difference between this and a document that merely changes status.

4 · Conformance, Demonstrated

Long after the decision, someone asks: was this brief properly governed? KF-3007 answers it against the object, through four tests:

• Constitutional coverage — every act traces to a Canonical PrincipleCanonical Principle — an enduring obligation true of any governed knowledge system, admitted only if it survives the two-question test (KF-1000 Part III). Vocabulary →: the object was governed not as knowledge but as an OKOOKO — the unit of design: a versioned representation together with its attached evidence, justification and acceptance-state (KF-1101). The system governs the object, never "knowledge itself". Vocabulary → (I), engineered as a lifecycle (II), accepted by collective authority (III), justified before reliance (VIII).
• Operational coverage — every transition has a trigger, an authority, criteria and a recorded outcome; every gate evaluated explicit exit conditions.
• Integrity coverage — the six invariants held; counter-evidence stayed attached; evidence was proportionate to A3.
• Reconstructability — the material claims can be rebuilt from the record.

A worked Conformance ClaimConformance claim — an assertion that an object is governed, accepted, current or reliable, reconstructable to the depth its reliance requires (KF-3007). Vocabulary →.

Claim: “The acceptance of KB-4DW-01 held sufficient authority for A3 reliance.” Supported by: the Acceptance Record (authority = Executive Committee; scope = six-month trial; date), the Authority Mandate Record confirming the Committee’s remit for A3 decisions, and the independent-review record required at A3. Assessment: Constitutional + Operational + Integrity + Reconstructability all satisfied. Finding: Conformant, at high confidence — the evidence is complete, event-native and independently corroborated (KF-3007 §13.3).

Had the independent review been missing, the same reconstruction would have returned Not Assessable for that claim — never a silent pass.

5 · Authority, Demonstrated

The acceptance was made by the Executive Committee, and the architecture can resolve that authority all the way down (KF-3008 §5.1):

Decision: accept KB-4DW-01 for a six-month trial
     ▲ resolves to
Acceptance Authority
     ▲ carried by
Role: Executive Committee
     ▲ defined by
Governance Structure
     ▲ constituted by
The Institution

Because the object is A3, three authority conditions applied that a lower class would not have required: the accepting authority was confirmed, an independent review stood between justification and acceptance, and separation held — the People & Operations lead who evaluated and justified the brief was not the body that accepted it (KF-3008 §11). Authority here is not seniority: the Committee’s right to accept rests on its mandate for consequential decisions, not on rank.

materialityMateriality — the degree to which an object, claim, decision or transition may affect consequential action, reliance, obligation, exposure, representation or preservation (KF-2003). Vocabulary →-demonstrated">6 · Materiality, Demonstrated

Everything above was shaped by one value set at the very start: A3 Consequential. Materiality never changed the path — an A0 note and an A4 board paper cross the same gates — but it set the depth at each one (KF-2003; KF-3001 IC-23):

The six invariants held identically at both classes. Only the depth above that floor scaled. This is the whole of materiality in one object: same architecture, same guarantees, proportionate effort.

7 · The Point — Generality

Nothing in the journey depended on the four-day week. Swap the subject and every stage, service, record, gate, authority and conformance test is unchanged:

Knowledge Foundry does not govern management, medicine, engineering or economics. It governs Operational Knowledge Objects. The subject matter changes; the architecture does not.

That is what the slice exists to prove — and why the architecture, not the example, is the thing to remember.

8 · Using This Exemplar

Every architecture document can point to the same running object rather than inventing its own:

Status and Honest Limits

This is a canonical illustration, and it illustrates — it does not validate. A constructed object confirms the architecture on an object built to succeed; it cannot surprise us, and surprise is what an experiment is for. The documents still marked Draft for Experiment (KF-2003, KF-3007, KF-0002) therefore remain provisional until one real, uncontrolled object has been run and allowed to break something. KF-5001 makes the architecture legible; it does not close that experiment. That is the honest boundary of a “Hello, World!” — it proves the parts fit together, not that they survive the world.