Glossary: debt, maintenance, and deprecation
This family groups the terms that explain how a canonical corpus remains governable after expansion. The problem is not only to create definitions, but to keep them current, routed, versioned, deprecatable, translatable and aligned with machine-readable artifacts.
The central distinction is direct: publication creates a surface; maintenance preserves authority. A page can remain available while losing governing force, and a correction can remain published while still failing to resorb older interpretations.
Canonical terms
- Semantic debt
- Canon maintenance
- Interpretive maintenance
- Maintenance burden
- Correction backlog
- Deprecation discipline
- Canonical refresh cycle
- Obsolescence control
Maintenance sequence
- Identify the canonical source and its current role.
- Check whether related terms, translations, artifacts and links still match that role.
- Mark obsolete or superseded surfaces through deprecation discipline.
- Open a correction backlog when propagation is incomplete.
- Estimate maintenance burden and correction budget.
- Apply obsolescence control to stale pages, examples, artifacts and memory states.
- Confirm correction resorption through observation, audit and durable routing.
This sequence prevents a common failure of large conceptual sites: treating volume as authority while allowing old, weak or obsolete surfaces to keep governing interpretation.
Related pages
- Glossary: sustainability, debt, correction
- Glossary: memory, persistence, remanence, and correction
- Glossary: canon, corpus, and machine readability
- Definitions and canonical concepts
How to read this lexical family
This family is the maintenance layer of the doctrine. It explains what happens after a canon has been created, expanded and linked. The hardest governance problems often appear later, when old definitions survive, examples become stale, translations drift, links keep pointing to weak pages and earlier versions remain influential.
The terms should be read as an operational sequence. Semantic debt accumulates when meaning is easier to publish than to maintain. Canon maintenance keeps primary surfaces aligned. Interpretive maintenance checks whether systems still reconstruct the intended meaning. Deprecation discipline prevents obsolete surfaces from continuing to govern interpretation.
Typical misreadings
The first mistake is to treat freshness metadata as authority. A recently modified page can still contain an outdated claim, and an older page can remain canonical if it is stable, explicit and maintained. Obsolescence control therefore depends on role, evidence and routing, not on date alone.
The second mistake is to treat correction as a single publication event. A correction is not complete when a new page is published. It is complete only when old interpretations stop dominating, weak surfaces are deprecated, the backlog is reduced and correction resorption is observable.
Use in audit and routing
Use this family when a site has become large enough that its own history starts to compete with its current canon. The audit should inspect stale examples, contradictory definitions, unresolved translations, superseded frameworks, old blog posts, residual links and machine-readable artifacts that may still point to prior states.
For routing, this family supports interpretive sustainability, memory governance, correction budget and canonical refresh pages. Its function is to keep a strong corpus from becoming an ungoverned archive.
How to use this glossary family
This glossary family should be read as a conceptual map, not as a replacement for the individual canonical definitions. Its role is to show how the terms around Glossary: debt, maintenance, and deprecation relate to one another and why they should not be collapsed into a single generic idea.
A useful reading starts with the failure pattern. Ask what kind of mistake the family helps prevent: confusing visibility with authority, retrieval with legitimacy, citation with proof, persistence with current validity, action with authorization, or coherence with fidelity. The definitions then become routing surfaces. They help decide which page should be primary, which page should support it, and which concept should remain separate.
Boundary of the family
The family does not prove that a model, search engine or agent follows these distinctions. It provides the vocabulary required to test whether they do. In practice, it should be used with observations, audits, source hierarchies and proof discipline. Without those layers, a glossary can name a risk but cannot show whether the risk has occurred.