Standards

Which measurable contract tells you what good means, what evidence counts, and when an artifact is ready to trust?

The Spine

1. Compounding Standards — understand fittings, persisted state, the Deming loop, quality tiers, and commissioning.
2. Continuous Improvement — choose a mapping, modelling, checklist, QA, or reengineering method after Performance exposes variance.
3. Wisdom Transfer Standard — gate significant artifacts across Language, System, Wiki, Standard, and Transfer.
4. KB Standards — govern names, writing, evidence, and Open Knowledge Format alignment.
5. Standard Templates — choose the production contract for the page job.
6. Information Architecture — place pages and folders without losing reader choice or graph meaning.

Zoom Out

• Up: Wiki Control Plane — routes authority, page jobs, and lifecycle.
• Across: Systems — models the relationships and feedback that standards govern.
• Proof: Performance — observes the gauge against the declared setpoint.

Changes my mind: a child route stops owning a distinct standards job.

Context

• feeds Performance — the declared contract gives the gauge its setpoint and evidence rule.
• proved-by Performance — observed output and outcomes make variance visible.
• revised-by Evolution — named authority may retain accepted evidence as a changed requirement, threshold, scope, or evidence contract.
• pairs-with Continuous Improvement — its methods diagnose and correct the producing system without assuming the setpoint must change.
• applies-to Standard Templates — production instruments carry the approved contract into repeatable work.

Questions

Next question: which setpoint or evidence gate is missing from the artifact you need to trust?

• Which observed variance belongs to execution, and which evidence would justify revising the standard?