KF-5000 · Exemplars & Case Studies
Worked instantiations of the architecture — illustrative, not normative
Purpose
The KF-5000 series shows the Knowledge Foundry architecture at work on concrete Operational Knowledge ObjectsOperational 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 →. Its documents teach and demonstrate; they do not legislate. Like the KF-0000 navigation series, KF-5000 introduces no new architectural concept — every element it shows is defined in its home document (Canon, Lifecycle, MaterialityMateriality — the degree to which an object, claim, decision or transition may affect consequential action, reliance, obligation, exposure, representation or preservation (KF-2003). Vocabulary →, and the KF-3000 series) and is only instantiated here.
The series exists because an architecture is easier to trust once it has been seen to run. A reader who has followed one governed object from capture to retirement understands the whole shape of the system before studying any single part in depth.
The distinction the series preserves
- KF-5001 · Canonical Vertical Slice is illustrative: a domain-neutral object (a four-day-week Knowledge Brief) constructed to make every architectural stage visible. It proves the parts fit together and that the architecture is subject-independent. It does not validate the architecture — a constructed object cannot surprise its designer.
- KF-5002+ · Case Studies are evaluative: real domain instantiations — beginning with MacroLab’s Singapore Business Impact Assessment — in which the architecture meets uncontrolled reality. These are where the architecture is stress-tested, and where the Draft for Experiment documents (KF-2003, KF-3007, KF-0002) are eventually validated before baselining.
The order is deliberate: understand the architecture on the canonical slice; then evaluate it on real cases. MacroLab is thereby positioned as a case study of Knowledge Foundry, not as its defining example.
Contents
| ID | Title | Kind |
|---|---|---|
| KF-5001 | Canonical Vertical Slice — the four-day-week Knowledge Brief | Illustrative exemplar |
| — | Teaching & Learning Domain — any subject as a governed knowledge domain | Illustrative sketch |
| KF-5002+ | Case Studies (MacroLab Singapore Business Impact Assessment, and others) | Evaluative case studies |
An illustrative teaching-and-learning domain
Illustrative, not validated — a sketch of what the discipline looks like applied to a taught subject.
Any course can be treated as a governed knowledge domain rather than a folder of slides recreated each term. Take any subject — Corporate Finance is used here only as an illustration; the shape is the same for public health, contract law or machine learning.
The subject becomes an Operational Knowledge Object domain: the canonical concepts and the explanations that carry them; the evidence behind each claim; worked examples and the assessment tied to stated learning outcomes; and the research and revisions that keep it current. Each element has provenance, an accountable owner, and a governed way of changing.
What changes for the institution: every cohort improves the same asset instead of rebuilding it, so departmental knowledge accumulates rather than resetting; teaching and research feed one another; a claim relied on in a lecture can be traced to its source and its justification; and what the department knows survives the turnover of who happens to teach it. The aim is that students reason from a trusted, inspectable domain — and that AI used in the course is grounded in approved, governed material rather than whatever it happens to generate.
This is a sketch of intent, not a validated result. Like every exemplar here, it illustrates the architecture; it does not prove it. Validation comes only from a real course governed this way — the kind of first case the programme is built to invite.
Relationship to the rest of the programme
KF-5000 sits beside KF-4000 (Implementation): where KF-4000 defines how the architecture is built in a deployment, KF-5000 shows how it behaves on individual objects. Both are downstream of the architecture and neither may revise it. For where every concept is defined, see KF-3009 (Crosswalks) and KF-0002 (Controlled Vocabulary).