Skip to main content
If reality changes, the Canon changes.

​
Purpose

The Canon exists to keep Lucia aligned across:

​
Update Triggers

Update the Canon when:
  • a feature ships
  • a route changes
  • a webhook provider changes
  • an environment changes
  • a model changes
  • an eval reveals a regression
  • a product decision is made
  • a workflow changes
  • a known limitation is resolved
  • a future plan becomes implemented

​
Three-Axis Truth Record

Do not compress truth state, capability maturity, and evidence freshness into one label. Record each axis that applies.

​
1. Canonical claim/action truth state

Use the vocabulary defined in Truth State Doctrine:
confirmed is an evidence qualifier or a domain-specific status, not a replacement for one of these canonical states. not yet done means there is no evidence for Completed (verified); use Requested or In Progress when either is known. done, handled, and resolved require verified completion.

​
2. Capability maturity

Use the capability labels that are actually supported:
A capability may carry more than one supported label. For example, configured does not prove implemented, and implemented does not prove tested. A tested claim must name its scope and evidence. deferred and future must never read as available capability.

​
3. Evidence freshness

Any statement that says or implies current, now, or live must carry a bounded evidence record. A claim of verification must also carry its verification date:
Never leave volatile current truth undated, unowned, or unscoped. A historical record keeps its event date and original context; when later evidence supersedes it, link the newer record instead of rewriting history into an undated present.

​
Carried update rules

These rules were set by Canon Wave 1 (2026-08-12) and Canon Wave 3 (2026-09-10) and bind every canonical page from those dates on.
  1. Every current claim carries as_of and last_verified. A page that states or implies current, now, or live carries both in its frontmatter; a row or claim with its own date overrides the page date only for itself.
  2. Historical baselines are titled and dated as historical. They never use undated words such as “current,” “today,” or “now.” A superseded record stays; the newer record is linked, not written over it.
  3. Date every claim by evidence, never by a status. A commit SHA, a served tag, a deploy receipt, or a dated founder ruling dates a claim. A Linear status does not. Work at its gate or awaiting the founder’s verdict is written as such, never as settled truth.
  4. Evidence order when claims conflict: founder rulings on the controlling record → the owning repository source and exact deployed-runtime evidence → accepted completion, integration, CI, and deployment receipts → existing Library canon → git history and clearly dated records → dashboard summaries or old prose.
  5. Names law. Lucia and Villa Valentin are written with a plain i on every surface (founder, 2026-09-09).
  6. Owner words on owner-facing pages. Where a page describes what a property owner sees, it uses the owner’s vocabulary and not engine or dev words (founder, 2026-09-02).
  7. No environment values, ever. An environment fact that no record evidences is written as “set by the founder’s hand, unverified.” Names may be cited; values never.
  8. Documentation is not runtime proof. Verify a runtime claim in the owning implementation or deployment evidence before writing it.
  9. Private stays private. Fleet mechanics, seats, credentials, service identifiers, and internal coordination material never enter this public Library.

​
truth_scope controlled list

Every canonical page carries one truth_scope from this list and no other spelling (ruled on Canon Wave 3, 2026-09-10; a writer who needs a sixth value names it on that record first):
A page whose body mixes doctrine with a dated snapshot carries the scope of its primary claim and dates the rest inline.

​
Weekly Review

Review:
  1. Current System State
  2. Lucia Decision Log
  3. Release Log
  4. Lucia Capability Roadmap
  5. Quality Bar
Ask:

​
Canon Failure Modes

Avoid:

​
See Also