KF-3009 · Architectural Crosswalks and Traceability

The navigation layer of the Knowledge Foundry Reference Architecture — how the whole fits together

Reference Architecture (Navigational) · Draft · v0.1 · 18 min read

Principle (KF-1000) → Methodology (KF-2000) → Reference Architecture (KF-3000)
        → Domains (KF-3001–3005) → Integration (KF-3006) → Conformance (KF-3007) → Authority (KF-3008)
        → ▸ Crosswalks and Traceability (KF-3009) → Implementation (KF-4000)

The architecture is complete at KF-3008. Principles, 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 →, reference architecture, integration, conformance and authority together provide everything essential. This document therefore introduces no new architectural domain and no new first-order concept. It performs a different role: it is the architecture’s synthesis — the atlas that accompanies the constitutional text. The constitution defines the rules; the atlas helps readers see where everything sits and how the parts relate, without creating new law.

Purpose

The Architectural Crosswalks and Traceability document provides the navigational layer of the Knowledge Foundry Reference Architecture. It maps architectural concepts, responsibilities and relationships across the architecture, clarifies document ownership, and demonstrates how the architecture forms a coherent, navigable and traceable system whose architectural integrity can be understood without duplicating its normative content.

This is navigation, not architecture. Every entry below points to a home document that owns the concept; KF-3009 owns only the relationships between the documents — the map, the crosswalks, the traceability matrices and the relationship catalogue. Where a crosswalk here and a home document appear to differ, the home document governs and this document is corrected.

Navigational Principle

Every architectural concept has one authoritative home. Relationships may be described elsewhere, but normative ownership is never duplicated. KF-3009 exists to preserve that discipline.

That single rule governs the whole document. It is why KF-3009 can map, cross-reference and trace freely without ever becoming a competing source of truth: it describes where things live and how they relate, and defines only the relationships themselves.

Figure 1 · The Master Traceability

The single diagram that explains the entire architecture — the programme’s architectural signature. It threads every layer, from the obligations the Canon imposes to the reliance the institution is finally warranted in placing:

Canonical Principles
        ▼ obligate
Architectural Obligations
        ▼ realised by
Capabilities
        ▼ delivered through
Services
        ▼ operate over
Lifecycle
        ▼ made consequential by
Authority
        ▼ enforced through
Controls
        ▼ emit
Evidence
        ▼ accumulates as
Traceability
        ▼ reconstructed as
Conformance
        ▼ warrants
Institutional Reliance

This figure is referenced throughout the document, and §11 reads it in full.

What this document does and does not own

KF-3009 defines no new ontology, no new lifecycle, no new authority and no new governance mechanism. It is the architecture’s index, atlas and navigation layer. What it does own — because these are relationships, not concepts — are: the Concept-Ownership register (§4), the Relationship Catalogue (§10), and the master traceability matrices (§§6–9). These were already promised to KF-3009 by the closing sections of KF-3002–3005 (“KF-3009 preserves traceability from principle through capability, service, record and control”).

1 · Introduction

Scope. The reading guide, the architecture map, concept ownership, the relationship catalogue, and the principle / obligation / lifecycle / materiality crosswalks, plus reference indexes and reserved extensions.

Audience. Every reader of the Reference Architecture, especially those arriving after KF-3000 who need to orient before going deep, and maintainers who must keep the series coherent as it evolves.

Relationship to the Reference Architecture. KF-3009 sits beside KF-3000 as its companion: KF-3000 opens the architecture, KF-3009 helps navigate it. It is the document every future reader should read second.

2 · How to Read the Architecture

Different readers enter at different places. This is the shortest path to what each needs:

No reader should have to read the series front to back to become productive; each path above is sufficient to act, and the crosswalks below fill in the rest on demand.

3 · The Architecture Map

The authoritative one-page orientation. (Its standalone pull-out is KF-0001 · Architecture Map; this is the same map, seated in its atlas.)

                      KF-L001 · Literature Landscape
                                 │ evidence
                                 ▼
                          KF-1000 · Canon
                                 │ principles
                                 ▼
              KF-2000 · Methodology
        (2001 Lifecycle · 2002 Practices · 2003 Materiality)
                                 │ methods
                                 ▼
                 KF-3000 · Reference Architecture
                                 │ domains
   ┌─────────────────────────────┼─────────────────────────────┐
   │  3001 Principles · 3002 Capabilities · 3003 Services       │
   │  3004 Records    · 3005 Control                            │
   │  ───────────────────────────────────────────────────────  │
   │  3006 Integration   ◀ how it works                         │
   │  3007 Conformance   ◀ how we know                          │
   │  3008 Authority     ◀ who may make it consequential        │
   │  3009 Crosswalks    ◀ how it all fits (this document)      │
   └─────────────────────────────┬─────────────────────────────┘
                                 │ realised by
                                 ▼
                 KF-4000 · Knowledge Operating System
                                 ▼
                       a domain deployment — a university course · a professional body · a decision system

  Programme-wide navigation:  KF-0001 Map · KF-0002 Controlled Vocabulary

Read by architectural layer, the same series stacks into four bands:

  Constitution   │ KF-1000
  ───────────────┼───────────────────────
  Method         │ KF-2000  (2001–2003)
  ───────────────┼───────────────────────
  Architecture   │ KF-3000–3009
  ───────────────┼───────────────────────
  Implementation │ KF-4000

4 · Concept Ownership

The rule that keeps the architecture free of duplicated definitions: every concept has exactly one primary home. When a concept appears in several documents, one owns it and the others reference it.

Where two documents touch one concept, one holds the authoritative treatment and the other holds an adjacent or derived view — the same single-owner discipline the record model applies to data (KF-3004 §7).

5 · Concept Relationship Crosswalk

For each core concept: what it depends on, what it supports, and where it is referenced. This is the “if I change this, what else is affected?” table.

6 · Principle Traceability (constitutional matrix)

Every Canonical Principle is realised somewhere in the architecture. This matrix is the constitutional traceability the Canon requires (KF-1301): a principle with no realisation would be an aspiration, not an obligation.

7 · Obligation Traceability (complete lineage)

One level below principles. Each material obligation can be traced along a single lineage from constitutional source to demonstrated conformance — the chain KF-3007 reconstructs:

Canonical Principle
      ▼ handed to method (KF-1301)
Architectural Obligation
      ▼ realised by
Architecture   (capability · service · gate · control · record)
      ▼ instantiated in
Implementation (KF-4000)
      ▼ emits
Evidence   (event-native)
      ▼ reconstructed as
Conformance

Worked lineage — justified transition. Principle VIII → obligation “no state advances without recorded warrant” → realised by Justification Service (SVC-05), GATE-JUS-01 and the justified-transition invariant → instantiated by a deployment’s justification store → emits the justification and transition records → reconstructed by KF-3007 Test 4 as the claim “this transition carried its warrant.” No link in this chain is optional for a material obligation; the depth of each is graded by assurance class (KF-2003).

This lineage is the minimum reconstruction path required for any material conformance claim. Additional evidence may exist, and higher assurance classes require more of it, but no conforming implementation may omit one of these architectural stages — a claim with a broken link in the chain is Not Assessable (KF-3007 §13).

8 · Lifecycle Crosswalk

Each lifecycle stage, read across its architectural participants. This is the single-page operational reference for “what does this stage require?”

Every row’s evidence is emitted by the act (event-native), and its conformance is assessed on the KF-3007 Authority, Lifecycle and Evidence dimensions.

9 · Materiality Crosswalk

How assurance class propagates through the architecture — the single value that grades authority, evidence, review, monitoring and conformance at once (KF-2003; KF-3007 §11; KF-3008 §12).

The six lifecycle invariants hold identically across every row; only the depth above that floor scales.

10 · The Relationship Catalogue

The permanent home of the canonical relationship vocabulary first stated in KF-3006 §4.1. The relationships defined below constitute the canonical architectural vocabulary for expressing relationships throughout the Knowledge Foundry programme. New relationship types shall not be introduced unless adopted into this catalogue. Every architectural diagram in the programme draws its arrows from here, so that a relationship always means one thing. These are collected, not invented here.

Three structural relationships support composite decisions and grading: references (decision → authoritative record, without copying it), attributed-to (transition → actor / authority), and graded-by (obligation depth → assurance class). Supersession and governance oversight are read as instances of traces (lineage) and constrains (policy) respectively, not as separate primitives.

11 · Reading the Master Diagram

Figure 1 (near the front of this document) is the single diagram that explains the entire architecture: it threads every layer, from the obligations the Canon imposes to the reliance the institution is finally warranted in placing. Every earlier diagram in the series is a segment of it — KF-3006 Figure 1 is its Principles-to-Conformance span; KF-3008 Figure 1 is its Authority-to-Reliance span. Read whole, it is the architectural argument of Knowledge Foundry in a single column, and the reason the series ends here, with synthesis rather than another framework. It is the programme’s architectural signature — the figure future presentations, papers and talks should reach for first.

12 · Reading Paths (recommended order by role)

• Executive / sponsor — KF-0001 → KF-1000 (purpose) → Figure 1 → KF-3009 §14.
• Reader (general) — KF-0001 → KF-3000 → KF-3006 → this document.
• Architect — KF-3000 → KF-3001 → KF-3002 → KF-3003 → KF-3004 → KF-3005 → KF-3006.
• Implementer — KF-3006 → KF-3003 → KF-3005 → KF-3007 → KF-3008 → KF-4000.
• Governance officer — KF-1000 → KF-2001 → KF-2003 → KF-3008 → KF-3007.
• Researcher — KF-L001 → KF-1000 → KF-3000 → KF-3006.

13 · Reference Tables

13.1 Document Index

13.2 Figure Index

13.3 Concept Index and Glossary

For any term’s authoritative definition, see the primary home in §4; for controlled definitions, required distinctions and the user-facing vocabulary, see KF-0002 · Controlled Vocabulary. KF-3009 does not redefine terms; it locates them.

14 · Architectural Evolution

The architecture is designed to change without losing coherence. Two distinct governance modes keep evolution disciplined — and the distinction between adding architecture and changing it is itself load-bearing.

14.1 Controlled Extension (new concepts)

Adding to the architecture. The numbering space is reserved rather than filled ad hoc:

• KF-3010+ — reserved for future architectural domains, admitted only if they pass the KF-3000 Architectural Admission Test and own a concept no existing document owns.
• Deeper treatments — a dedicated temporal or dependency model, say — would extend, not revise, the existing domains, and would be traced here.
• Discipline — no new document may duplicate a concept owned in §4; a proposed addition that would must instead amend the owning document. This is the Navigational Principle applied to growth.

14.2 Controlled Revision (existing concepts)

Changing what already exists. Revision follows the inheritance rule the Canon fixes: a lower level may change how it satisfies a higher one, but may not silently revise the higher one.

• Amend at the home — a concept is revised only in its owning document (§4); every secondary reference then inherits the change.
• Constitutional amendments — a change to a Canonical Principle is made against the Landscape’s evidence and propagated downward (KF-1000); it is never overridden quietly in a lower document.
• Re-trace after revision — when any home document changes, the crosswalks here and the conformance completeness check (KF-3007 §7.1) are re-run to confirm coverage still holds.

The series is considered conceptually complete at KF-3008; anything beyond elaborates, operationalises or validates that core. Extension adds a new home; revision changes an existing one; neither duplicates a concept already owned.

15 · Summary

The Knowledge Foundry Reference Architecture is intentionally modular. Architectural understanding therefore depends not only on the individual documents but on the relationships that bind them together. This document provides those relationships — the map, the ownership boundaries, the crosswalks, the relationship catalogue and the master traceability — ensuring that the architecture may continue to evolve while remaining coherent, navigable and traceable.

The series answers six questions in order: what is the architecture (KF-3000), what are its domains (KF-3001–3005), how do they operate together (KF-3006), how is its integrity demonstrated (KF-3007), who may legitimately make it consequential (KF-3008), and how does the whole fit together (KF-3009). Ending with synthesis rather than another specialised framework is the point: the last document is the one that makes all the others easier to understand and maintain.

Together these documents establish a complete architectural lineage from constitutional principle to institutional reliance. KF-3009 closes the Reference Architecture by making that lineage explicit, navigable and maintainable.

Closing Statement

KF-3009 is the atlas to the constitution. It creates no law and owns no concept save the relationships among the rest. Its success is measured not by what it adds but by what it makes navigable: an architect, an implementer, a reviewer or a governance officer should be able to enter the architecture anywhere, find where every concept lives, follow any obligation from principle to conformance, and trust that the whole remains one coherent, traceable system. With it, the Reference Architecture is not merely a set of documents — it is a map of a single governed knowledge systemGoverned knowledge system — a socio-technical system that holds operational knowledge objects and governs their transition from one justified state to another across modalities (KF-1001). Vocabulary →, and a means of keeping it coherent as it evolves.