Skip to content

Known limits and unresolved evidence

A limitation states which conclusion cannot yet be supported and what would resolve it. Missing source coverage, an undecided definition, an implementation gap and an unexecuted acceptance scenario need different next actions. None should be represented as a confirmed zero or a completed outcome.

This register explains how to read and maintain limits. The linked canonical articles own their exact technical rules. Current issue state must be checked when planning work; the dated status index and this source review are not a live acceptance dashboard.

Class Example in the reviewed system Required next evidence or decision
Financial acceptance Complete correction/payment/project lifecycle and historical exceptions Same-identity source reconciliation and independent scoped acceptance
Definition Revised self-cost/contribution-margin meaning Accepted owner decision before implementing a new metric
Payroll receiving outcome First-stage PAX handoff and later connector path Receiving-system acceptance and durable destination/receipt coverage
Operational independence Full working day and transition ownership Named persona journey without developer intervention
Import/cutover Historical parity, fixture cleanup and operational transition Authorized baseline, exception ownership and transition decision
Recovery Combined application/identity recovery and detection objectives Generation-bound drill and measured scenario timing
Security/source boundary MCP audience/bearer/quota gaps, incomplete originals and retention coverage Exact owning correction/decision and negative/positive evidence

The financial lifecycle, margin definitions, working-day acceptance, transition and recoverability retain their separate owning issues, including #414, #375, #413, #415 and #416 at this review. Payroll/PAX work and historical exception review likewise keep their receiving-system and source-specific outcomes. A new handbook edition does not close those issues.

Reports retain incomplete allocation, missing dates and unverified register coverage. Missing data does not become SEK, a date, complete payment evidence or zero cost. Preserve the current covered-only definitions and thresholds until their owner changes them. Reports and reconciliation specify the actual calculations.

Native eligible backoffice time attestation can queue payroll automatically; imported approvals are excluded. Documenting that executable distinction does not establish receiving-payroll acceptance. The direct connector path and the agreed first-stage PAX outcome have separate activation/evidence boundaries. Time and payroll owns them.

The mail archive can have incomplete original/attachment coverage. A missing source object is not proof that no attachment existed. The import registry’s 27 reconciliation rules specify checks; private-corpus parity and current historical exceptions need their own execution evidence. Import reconciliation preserves that scope.

Public MCP identity handling does not resolve every resource-audience, bearer and quota limitation. There is no established universal retention schedule or automatic redaction of all free-text diagnostic paths. UE audience, closure and photo evidence retain their documented limits. Stronger customer/recipient/completion predicates must not be weakened to simplify these summaries.

State the affected record/outcome, known evidence, missing fact, owner and next discriminating check. If a definition is undecided, name the decision. If execution is missing, name the scenario/target/version required. If source coverage is incomplete, show that coverage in the result rather than silently treating it as complete.

A synthetic report with an unallocated purchase invoice can show covered revenue and explicitly incomplete costs. It cannot support a final project-profit claim. A synthetic component restore can show matching hashes while leaving Auth startup unverified. Recovery keeps RPO 60 minutes/RTO 240 minutes as objectives until measured evidence supports them.

Resolve a gap only through its owning decision or evidence and update all dependent statements. Preserve the old receipt. Authority and evidence keep writing completion separate from product acceptance, including after all 85 handbook questions have detailed answers.