Administrative Maintenance Terminology Registry
Registry extension: MP-ADMIN-TERMS-001
Parent registry: docs/AGENT_COUNCIL_TERMINOLOGY_REGISTRY.md
Decision lineage: ADR-0016
Current interpretation: amended by MP-STREAMLINED-EXECUTION-001
This controlled extension defines the maintenance vocabulary used by MATH-PROGRAMME. Terms introduced by the original accelerated pilot remain registered for documentary continuity, but their historical timing or admission mechanics do not create current routine countdowns or approval gates.
| Term | Canonical meaning | Boundary and exclusions |
|---|---|---|
| Core Clarity | The condition in which authority, material identity, current state, validating route, supporting evidence, permitted next action, and prohibited claims are explicit without inference. | Does not assert that the governed mathematics is correct or complete. |
| Material evidence closure | The governed changed bytes together with the directly consumed protected artifacts, validators, schemas, workflows, toolchain pins, policy bytes, authority, and claim scope that can affect the conclusion. | Unrelated repository-head movement is outside the closure. |
| Material change | A change that alters authority, lifecycle, route, claim, promotion, accepted evidence, prohibited use, consumed provider content, required workflow semantics, or another input in the material evidence closure. | Repository-head movement alone is not material when relevant consumed identities and semantics are unchanged. |
| Nonmaterial change | A change that preserves the material evidence closure, such as an unrelated protected commit, byte-identical synchronization, mirror repair, or typographic edit outside the governed conclusion. | Classification requires evidence; genuine ambiguity fails closed to the smallest defensible affected set. |
| Delegated routine disposition | Standing authority to complete bounded administrative, documentation, engineering, workflow, maintenance, routing, synchronization, and campaign-execution work through protected merge and readback once affected checks pass. | Does not authorize mathematical certification, source-semantic adjudication, constitutional expansion, security-sensitive weakening, or external claim promotion. |
| Concurrent protected development | Development in which protected main may advance without forcing every open candidate to update or rebase. |
Candidate remains valid only while mergeable and its relevant dependencies, material closure, scope, and authority are unchanged. |
| Impact-routed CI | Selection of only the policy shards, formal lanes, or computational replays affected by the material transition, with stable aggregate required contexts where needed. | Does not exempt material changes from their substantive checks; scheduled/manual full sentinels remain available. |
| Protected evidence reuse | Completion of a required context by verifying that previously protected evidence remains valid for an unchanged material identity. | It is not caching a mathematical conclusion across changed inputs. |
| Event-triggered material propagation | Immediate update of materially affected cross-repository contracts after a governed change. | “Propagation” does not mean branch rebasing or repository-head synchronization when consumed artifacts are unchanged. |
| Event-triggered synchronization | Historical ADR-0016 name for immediate cross-repository propagation after a material transition. Under current policy it means material-contract propagation, not numerical repository-head synchronization. | Does not require rebase, update-branch, repin, or rerun when the consumed material identity is unchanged. |
| Accelerated maintenance time scale | Historical ADR-0016 pilot rule multiplying proposed maintenance durations by 0.1. |
Retained for interpreting pilot records; it does not create a current recurring schedule. |
| Accelerated pilot | Historical nine-day administrative-maintenance pilot beginning at the protected admission of PR #184. | Its admission and timing sequence is provenance, not the present routine operating protocol. |
| Workflow coverage | The recorded combination of capability, trigger, required-context role, affected-input rule, execution or protected-reuse evidence, owner, repair route, and last verified material identity. | A workflow file, historical green run, or monolithic full-suite execution alone is insufficient. |
| Canonical tracker | The designated issue or navigation surface that points to protected authority, current lifecycle and route state, next obligation, claim boundary, and review trigger. | It cannot create protected state. |
| Issue mirror | A mutable issue, pull request body, or comment that explains or navigates protected authority. | It cannot change lifecycle, route, certification, or claim state. |
| Tracker refresh clock | Historical ADR-0016 PT7H12M target for refreshing mutable tracker mirrors during the accelerated pilot. |
No standing current clock exists; repair a mirror when a material protected transition makes it stale or contradictory. |
| Specialist review | Independent non-author scrutiny required by a substantive mathematical, source-semantic, constitutional, security-sensitive, or external-claim boundary. | Not a generic requirement for routine bounded administration. |
| Protected readback | Verification after merge that the intended artifact and authority state are present on protected state. | It is evidence, not a second approval cycle. |
| Administrative waiver | A typed, scoped, expiring exception with owner, evidence, approver, prohibited uses, and repair obligation. | It cannot authorize claim promotion; critical waiver classes remain subject to their reserved authority. |
| Emergency override | A temporary bounded control used only to restore availability, respond to a security incident, or restore CI operability. | It cannot promote, certify, delete evidence, or leave repository protection weakened. |
| Maintenance-burden circuit breaker | The principle that administrative machinery is narrowed, consolidated, automated, or retired when recurring cost exceeds the material risk it reduces. | It does not suspend unrelated campaigns because a calendar interval elapsed. |
| Campaign-level fail closed | Suspension of the affected promotion or transition when a critical required capability or evidence boundary is materially missing or stale. | Does not automatically suspend unrelated campaigns. |
| Portfolio admission freeze | Historical term for withholding a new portfolio admission when the pilot's applicable maintenance or authority prerequisites were unsatisfied. | It is not an estate-wide freeze and does not block unrelated already-authorized work. |
| INTELLECT Phase A buy-in | Historical first stage of the original INTELLECT administrative-maintenance adoption sequence. | Retained as admission provenance; current routine maintenance does not repeat it. |
| INTELLECT Phase B protected adoption | Historical protected-adoption stage of the original INTELLECT sequence. | Current INTELLECT administration follows live protected contracts and readback rather than replaying this admission ceremony. |
| Protected-merge activation | The rule that an artifact whose authority requires protected admission becomes operative only through the applicable protected merge/readback condition. | A branch, issue, comment, or review alone cannot create protected authority. |
| Final cross-repository closure | A state in which materially affected provider/consumer contracts and protected identities agree and required readback is complete. | Does not require ceremonial repinning of unchanged artifacts and does not promote mathematical or external claims. |
Historical pilot interpretation
The 0.1 accelerated factor, PT7H12M tracker target, nine-day pilot, and Phase A/Phase B INTELLECT sequence remain readable in ADR-0016-era evidence. They do not override the current event-driven cadence in docs/governance/AGENT_CADENCE_OPERATING_DESIGN.md, the routine execution rules in docs/governance/STREAMLINED_EXECUTION_AMENDMENT.md, or the current CI evidence in docs/WORKFLOW_COVERAGE.md.
Final administrative closure is prohibited while a genuinely applicable material authority, evidence, protection, or documentary obligation remains unresolved. That fail-closed rule does not convert historical pilot timers, obsolete review ceremony, or unrelated repository-head movement into new blocking obligations.
Change control
A term in this extension may change through a governed change that identifies the affected control, material consistency checks, applicable review evidence, supersession boundary, and claim boundary. Routine terminology/editorial maintenance uses standing delegated authority; a change that alters constitutional authority, promotion semantics, or a substantive claim boundary receives the specialist review appropriate to that material change.