Skip to main content
Version: 2.2 (current)
MCF 2.2 – Documentation·Last updated: 2026-02-13

Chapter 35: Appendices and Tools

What this chapter does
  • Collects supporting tools and references.
  • Provides structured access to templates.
  • Anchors tools to Canon concepts.
  • Frames appendices as supporting material.
What this chapter does not do
  • Does not add new Canon rules.
  • Does not replace chapter guidance.
  • Does not guarantee completeness.
  • Does not serve as operational policy.
When you should read this
  • When locating tools used in chapters.
  • When referencing templates or checklists.
  • When onboarding new teams.
  • After reviewing core chapters.
Derived from Canon

This chapter is interpretive and explanatory. Its constraints and limits derive from the Canon pages below.

Key terms (canonical)
  • Evidence
  • Evidence quality
  • Decision threshold
  • Optionality preservation
  • Strategic deferral
  • Reversibility
Minimal evidence expectations (non-prescriptive)

Evidence used in this chapter should allow you to:

  • document tool purpose and scope
  • show alignment with Canon terms
  • explain how tools are applied
  • justify tool selection

Appendices and tools are supporting artifacts, not sources of authority. This chapter explains how to use tools without turning them into substitutes for evidence or Canon.

Why This Matters In Phase 5​

Phase 5 is where tools often become institutionalized. That creates risk: tools can be mistaken for rules, and examples can be mistaken for obligations. The framework depends on preserving the boundary between Canon (normative) and Book (explanatory). Tools are optional accelerators, not compliance guarantees.

What “Good” Looks Like (Explanatory)​

Tools are used responsibly when:

  • Their purpose and scope are explicit and evidence-aligned.
  • They clarify decision inputs rather than prescribe outcomes.
  • They remain replaceable without changing Canon semantics.
  • They are governed by the same boundaries and auditability rules.

Good tooling reduces ambiguity without creating new rules.

Typical Failure Modes​

Tooling failures often come from boundary drift:

  • Tool elevation: templates treated as Canon rules.
  • Checklist compliance: evidence reduced to box-ticking.
  • False certification: tools interpreted as proof of maturity or readiness.
  • Scope creep: examples used as mandatory processes.

These failures undermine decision integrity and misrepresent the framework.

Evidence You Should Expect To See​

Evidence that tools are being used correctly includes:

  • Clear mapping between tool outputs and decision thresholds.
  • Traceable decisions that cite evidence, not template completion.
  • Explicit statements that tools are optional and replaceable.
  • Governance review when tools influence irreversible commitments.

If tools cannot change decisions, they should not be treated as evidence.

Common Misuse And Boundary Notes​

Boundary violations are most visible in tool claims:

  • Presenting tools as certification or compliance mechanisms.
  • Using tool completion as a substitute for evidence.
  • Treating diagrams as Canon without citation or governance.

Use /docs/book/boundaries-and-misuse to keep tools within the Book layer. Canon definitions and boundaries remain authoritative.

Cross-References​

  • Book: /docs/book/decision-logic, /docs/book/governance-and-roles, /docs/book/failure-modes, /docs/book/boundaries-and-misuse
  • Canon: /docs/canon/definitions, /docs/canon/framework-boundaries, /docs/canon/governance-boundaries, /docs/canon/versioning-termination
Last updated on