Skip to content

CTC Rebuild-Readiness Gap Register

  • Status: CURRENT CROSS-FAMILY GAP REGISTER / NOT A ROADMAP
  • Current source head: qa/master@b09c339ec1a7305554af16bd55bc4be1685719b5
  • Context: Appendix O
  • Cross-family review: CROSS_FAMILY_RECONSTRUCTION_CONSISTENCY_REVIEW.md
  • Does not own: Phase/Task status, activation, implementation sequence, Process lifecycle or external-effect authorization

1. Purpose

This register lists named gaps that prevent reliable system reconstruction, operational verification or migration readiness.

A gap can be closed only by its owning authority and required evidence. Document volume does not close a gap automatically.

Severity:

S0 CRITICAL — current status/authority is contradictory or unsafe to execute
S1 HIGH — blocks M3/M4 or safe migration/correction
S2 MEDIUM — important completeness/operability gap
S3 LOW — improvement after higher-risk gaps

Readiness impact:

DOC = documentation consistency
M3 = operational verification
M4 = migration readiness
OPS = current operations/support
REC = deployment/backup/restore

2. Global Status And Authority Gaps

XFR-GAP-001 — Phase hold not reflected in current status owners

  • Severity: S0
  • Impact: DOC / OPS
  • Affected: Roadmap, Task consumers, agent execution
  • Finding: user placed Phase work on hold while Roadmap retained active IN PROGRESS Phase Tasks.
  • Required correction: Roadmap marks all Phase Transformation execution USER HOLD; preserve specs/evidence without activation.
  • Evidence to close: current Roadmap and Appendix O agree; no current execution prompt starts a held Phase.
  • Safe current action: documentation correction only.

XFR-GAP-002 — Volatile source/candidate status duplicated across documents

  • Severity: S1
  • Impact: DOC / M3 / M4
  • Affected: navigation, source-authority docs, progress ledgers, handoffs
  • Finding: candidate/release SHAs and statuses were copied into multiple files and diverged.
  • Required correction: one source-authority owner per family; navigation links rather than copies volatile facts.
  • Evidence to close: no contradictory current/released/not merged claims for selected families.

XFR-GAP-003 — Family analysis baselines are stale without delta disposition

  • Severity: S1
  • Impact: DOC / M4
  • Affected: Billing, MK Core, Scale, Trade, platform packets
  • Finding: detailed packets use older SHAs while current source has advanced.
  • Required correction: record current head and post-baseline delta state; revalidate affected source owners.
  • Evidence to close: every selected packet is HEAD-CURRENT, DELTA-RECONCILED or explicitly historical.

XFR-GAP-004 — Master coverage matrix became a stale second status view

  • Severity: S1
  • Impact: DOC / M4
  • Affected: SYSTEM_RECONSTRUCTION_COVERAGE_MATRIX.md
  • Finding: matrix described completed waves as future and Loader as unimplemented.
  • Required correction: replace with concise current summary; detailed companion matrices own family detail.
  • Evidence to close: no contradiction with source-authority docs/current head.

3. Loader / Inbound / Workforce Gaps

XFR-GAP-010 — Approved Loader storage contract conflicts with current source

  • Severity: S0
  • Impact: DOC / M3 / M4 / OPS
  • Source: ca0d354ac2a4e71f9a070d8a762abbab289bebf1
  • Approved historical decision: one ASSIGNMENT_DATA JSON column; no structured data in FINAL_DRAFT.
  • Current source: QUEUE_WORK_ASSIGNMENT and JSON detail in FINAL_DRAFT.
  • Required owner: current TMS operational owner + future Process/architecture review.
  • Evidence required:
  • current schema columns and data;
  • exact current field/marker contract;
  • current read/write callers;
  • compatibility and migration implications;
  • user decision on preserve/correct current adapter.
  • Blocks: current-source M2, all M4, current Wiki activation.
  • Safe current action: document divergence; no Phase correction while hold applies.

XFR-GAP-011 — Current Loader create idempotency is not established

  • Severity: S1
  • Impact: M3 / M4 / OPS
  • Finding: current source commit visibly creates rows but durable request-token behavior is not established from current reconciled evidence.
  • Required evidence:
  • duplicate/response-loss test;
  • exact request identity;
  • existing row lookup;
  • no duplicate queue item/Telegram send.
  • Safe current action: operator must reread queue before repeating create.

XFR-GAP-012 — Shared Loader queue concurrency requires current revalidation

  • Severity: S1
  • Impact: M3 / M4
  • Affected: Load, Break, Work, Clock Out Start/queue order
  • Required evidence:
  • same-loader concurrent commands;
  • terminal Clock Out enforcement;
  • one active job;
  • queue-order update behavior;
  • cleanup/residue.

XFR-GAP-013 — Loader role/API/current Wiki acceptance missing

  • Severity: S1
  • Impact: M3 / OPS / WIK
  • Required matrix:
  • intended office roles;
  • Forklift Operator own-record;
  • foreign-loader denial;
  • page/API/action parity;
  • current labels/mobile;
  • Telegram/QBT partial results;
  • exact Wiki rows/rendered content.

XFR-GAP-014 — Historical Loader execution package remains executable

  • Severity: S0
  • Impact: DOC / OPS
  • Finding: old local prompt still instructs Stage 0–6 implementation against superseded assumptions.
  • Required correction: retire prompt/package as historical and point to current source authority.
  • Evidence to close: no current navigation tells an agent to run the old package.

4. Final Loading Review / Inventory Gaps

XFR-GAP-020 — Current Final Review read model not reflected in packet

  • Severity: S1
  • Impact: DOC / M3
  • Source: b09c339ec1a7305554af16bd55bc4be1685719b5
  • Change: shipper quantity/weight and revised comparison presentation.
  • Required correction: source delta addendum; DTO/Runbook/Wiki scenario updates.

XFR-GAP-021 — High-average calculation/policy not source-reconciled

  • Severity: S1
  • Impact: M3 / OPS
  • Required evidence:
  • formula;
  • baseline source;
  • threshold;
  • warning vs blocker;
  • type/UOM behavior;
  • target-role interpretation.

XFR-GAP-022 — Final Review semantic role matrix incomplete

  • Severity: S1
  • Impact: M3 / M4
  • Finding: menu roles and write-helper roles differ; non-Client-1 behavior differs.
  • Required correction: tenant/profile + role + page + API + action + record matrix.

XFR-GAP-023 — Customer-name weight exception remains structural debt

  • Severity: S1
  • Impact: M4
  • Finding: current behavior uses customer display name such as TGI for weight policy.
  • Required target: typed profile/customer policy, not name comparison.
  • Safe current action: preserve current behavior; document exact exception.

XFR-GAP-024 — Bale adjustment transaction/reversal policy incomplete

  • Severity: S1
  • Impact: M3 / M4
  • Required:
  • manual source taxonomy;
  • multi-source atomicity;
  • balance concurrency;
  • reversal lower-bound policy;
  • placement/allocation effects;
  • role/reason/audit.

5. Yard / Driver / Street Turn Gaps

XFR-GAP-030 — Street Turn source delta not reconciled into family packets

  • Severity: S1
  • Impact: DOC / M3 / M4
  • Sources: 8e661451..., 31ce2583...
  • Required:
  • eligibility;
  • selected Equipment Load identity;
  • Booking relation;
  • multi-row partial result;
  • current/future command semantics;
  • Runbook/Wiki update.

XFR-GAP-031 — Street Turn revert pairing policy incomplete

  • Severity: S1
  • Impact: M3 / M4 / OPS
  • Current logic selects the immediately preceding returned import load.
  • Required evidence/policy:
  • uniqueness/ambiguity;
  • progressed child blockers;
  • response-loss reread;
  • reason/audit;
  • correction after partial sync.

XFR-GAP-032 — Pull Out Closing durable checkpoint identity missing

  • Severity: S1
  • Impact: M3 / M4 / OPS
  • Required: separate closing/scale and Yard completion states, resume identity, no physical replay.

XFR-GAP-033 — Queue-after-clear idempotency/owner incomplete

  • Severity: S1
  • Impact: M4 / OPS
  • Required: stable origin/dependency ID, one physical completion, correction/cancel, scheduler/command owner.

XFR-GAP-034 — Hardcoded staff/roster policy

  • Severity: S1
  • Impact: M4
  • Required: semantic role/capability/configured shift assignment; preserve current compatibility until evidence.

6. Billing / Provider / File Gaps

XFR-GAP-040 — QBO provider-created/local-reference-unknown recovery incomplete

  • Severity: S0
  • Impact: M3 / M4 / OPS
  • Risk: duplicate invoice after timeout/local-save failure.
  • Required:
  • provider matching identity;
  • search/reconcile capability;
  • stale SYNCING policy;
  • attempt history;
  • finance manual-review owner.

XFR-GAP-041 — Outbound cost transaction identity ambiguous

  • Severity: S1
  • Impact: M3 / M4
  • Required: explicit cost subtype/owner and exact transaction ID; no “latest AP” target behavior.

XFR-GAP-042 — File object/link/readability/retention evidence incomplete

  • Severity: S1
  • Impact: M3 / M4 / REC
  • Required:
  • actual storage backend;
  • object generation/version;
  • metadata/link atomicity;
  • shared-object delete;
  • orphan cleanup;
  • backup/restore consistency.

XFR-GAP-043 — Gmail target/part unknown-result recovery incomplete

  • Severity: S1
  • Impact: M3 / M4
  • Required: message/thread identity, target × part outcomes, attachment version, resume only missing parts.

XFR-GAP-044 — Durable provider attempt model not implemented

  • Severity: S2
  • Impact: M4
  • Current accepted policy: no generic outbox.
  • Required: provider-specific intent/attempt/callback/reconciliation only when selected/approved.

7. MK Core / Allocation / Scale / Trade Gaps

XFR-GAP-050 — Booking compatibility child mutations remain hidden

  • Severity: S0
  • Impact: M3 / M4 / OPS
  • Required: Booking-owned save separated from explicit child commands/results; current partial/unknown recovery characterized.

XFR-GAP-051 — Allocation quantity/weight/UOM authority unresolved

  • Severity: S0
  • Impact: M3 / M4
  • Required:
  • per-UOM authority;
  • precision/rounding/conversion;
  • lower-bound concurrency;
  • request idempotency;
  • reversal/correction;
  • downstream lock.

XFR-GAP-052 — Physical Scale Gross/Tare flow contradiction

  • Severity: S0
  • Impact: M3 / M4 / OPS
  • Required current evidence for Purchase, Doortrade, Sales, Export and accepted flow policy.
  • Blocks: Scale process approval and writer migration.

XFR-GAP-053 — YMS/BMS competing Scale writer contract

  • Severity: S1
  • Impact: M4
  • Required: one owner or proven disjoint record scopes; common correction/reversal evidence.

XFR-GAP-054 — Commercial/Order manual status vs derived execution

  • Severity: S1
  • Impact: M3 / M4 / OPS
  • Required: user-facing status meaning, transition actor, utilization projection and correction policy.

XFR-GAP-055 — Trade/Cost/Rate packet baseline stale

  • Severity: S1
  • Impact: DOC / M4
  • Required: current source recheck and removal of detached Loader candidate status from this family authority.

XFR-GAP-056 — Packing Rate per-item result and print race

  • Severity: S1
  • Impact: M3 / M4 / OPS
  • Required: per-item result, expected version/rate, persisted reread before print, reason/history.

XFR-GAP-057 — Browser document output lacks durable completion semantics

  • Severity: S2
  • Impact: M4 / OPS
  • Required Product decision: browser projection only vs durable snapshot/file/email/approval effect.

8. Tenant / Identity / Authorization Gaps

XFR-GAP-060 — Runtime operating-profile assignment not first-class

  • Severity: S1
  • Impact: M4
  • Required: portable tenant/profile assignment/version and effective readback.

XFR-GAP-061 — Missing/error module compatibility is fail-open

  • Severity: S1
  • Impact: M3 / M4 / OPS
  • Required: caller inventory, explicit parity seed, role regression and bounded strict cutover.
  • Safe current action: do not globally fail-close.

XFR-GAP-062 — Semantic action/record matrix incomplete

  • Severity: S0
  • Impact: M3 / M4
  • Required: tenant × role/capability × page × API × command × record × state × expected decision.

XFR-GAP-063 — Session/impersonation lifecycle policies open

  • Severity: S1
  • Impact: M4 / OPS
  • Required: idle/absolute timeout, revoke, privileged reauth, impersonation reason/expiry, actor/subject audit.

XFR-GAP-064 — Numeric tenant/customer business compatibility remains

  • Severity: S1
  • Impact: M4
  • Required: typed profile/capability/config replacements; preserve current operational behavior until selected cutover.

9. Audit / Evidence Gaps

XFR-GAP-070 — Canonical KJDatabase audit description is incorrect

  • Severity: S0
  • Impact: DOC / M4 / OPS
  • Finding: canonical DB rule says generic before/after snapshots; source indicates bounded mutation metadata and no generic before snapshot.
  • Required correction: update canonical owner and consumers.

XFR-GAP-071 — Transition audit active-writer statement is stale

  • Severity: S1
  • Impact: DOC / M3 / M4
  • Finding: canonical DB rule says no active writer; selected Loader writer exists in source.
  • Required: exact writer/caller/environment DB evidence and bounded wording.

XFR-GAP-072 — Transition audit environment activation unknown

  • Severity: S1
  • Impact: M3 / M4
  • Required: actual table schema, writer execution, rows, retention/legal hold, failure behavior.

XFR-GAP-073 — Unified support timeline target not implemented

  • Severity: S2
  • Impact: OPS / M4
  • Required: read-only resolver across business row, transition, request log, domain/provider evidence with redaction.

10. Integration / Worker Gaps

XFR-GAP-080 — Current scheduler/service inventory incomplete

  • Severity: S1
  • Impact: M4 / REC
  • Required: installed definitions, deployment, schedule/timezone, last result, overlap/lease, disable/resume owner.

XFR-GAP-081 — Voice transcript outbox is host-local

  • Severity: S1
  • Impact: M4 / REC
  • Required: host replacement, multi-instance ownership, locking, backup/restore and drain reconciliation.

XFR-GAP-082 — Callback deduplication varies by provider

  • Severity: S1
  • Impact: M4
  • Required: provider event identity, duplicate/out-of-order, receipt/apply state, secret rotation.

XFR-GAP-083 — Provider connectivity/current credential state unverified

  • Severity: S2
  • Impact: M3 / REC
  • Required environment evidence; no live side-effect probe without approval.

11. Deployment / Backup / Restore Gaps

XFR-GAP-090 — Production auto-pull mechanism not repository-established

  • Severity: S1
  • Impact: REC / OPS
  • Required: installed service/timer/lock/retry/failure/reload and deployed-SHA evidence.

XFR-GAP-091 — Application-wide readiness contract missing

  • Severity: S1
  • Impact: M4 / REC
  • Required: source/config/schema/dependency identity and safe liveness/readiness endpoints per service.

XFR-GAP-092 — Central observability/SLO/alerting not established

  • Severity: S2
  • Impact: M4 / REC
  • Required: metrics/log/trace backend, thresholds/windows, owner/escalation, capacity/retention.

XFR-GAP-093 — Complete DB backup/PITR evidence missing

  • Severity: S0
  • Impact: REC / M4
  • Required: snapshot/PITR, encryption, retention, owner, isolated restore evidence.

XFR-GAP-094 — File/object backup evidence missing

  • Severity: S0
  • Impact: REC / M4
  • Required: actual EFS/S3 backend, versioning/snapshot/inventory, cross-region/restore and DB-object consistency.

XFR-GAP-095 — Config/credential recovery plan incomplete

  • Severity: S1
  • Impact: REC / M4
  • Required: secure config version/recovery, secret restore vs rotate, OAuth reauthorization, applied readback.

XFR-GAP-096 — Complete isolated restore rehearsal missing

  • Severity: S0
  • Impact: REC / M4
  • Required: DB, archive, files, config, credentials, source/schema, provider reconciliation, canaries, cleanup.

XFR-GAP-097 — Approved/measured RPO and RTO missing

  • Severity: S1
  • Impact: REC / M4
  • Required: Product/Operations tolerance, infrastructure capability, measured rehearsal and approval.

XFR-GAP-098 — Shared/Dedicated recovery parity unverified

  • Severity: S1
  • Impact: M4 / REC
  • Required: dedicated deployment inventory, portable tenant identity, config/credential/provider/file ownership and rehearsal.

12. Wiki / Operational Knowledge Gaps

XFR-GAP-100 — Current Wiki content not read for detailed packets

  • Severity: S1
  • Impact: OPS / M3 / M4
  • Required: exact T_WIKI_PAGE row and rendered page read, comparison, owner/role review.

XFR-GAP-101 — Future/current wording may be mixed

  • Severity: S1
  • Impact: OPS
  • Required: classify every procedure as current verified, current source-reconciled, future target or unknown.

XFR-GAP-102 — Diagram renderer/mobile/accessibility unverified

  • Severity: S2
  • Impact: OPS
  • Required: renderer test or maintained SVG/PNG fallback with plain text.
  • Severity: S2
  • Impact: M4 / OPS
  • Required: current PHP route, future React/Next.js route, redirect/retirement and findability.

13. Readiness Conclusion

Detailed packets present: YES
Cross-family dependency documented: YES
Phase execution active: NO — USER HOLD
Current M3 family accepted: NONE established by this review
Current M4 family accepted: NONE
Complete restore readiness: NO
Current Wiki field acceptance: NO

14. Gap Closure Record

When closing a gap, record:

gapId
owner
source/environment
change/evidence
normal/negative/recovery result
cleanup/rollback
updated Process/Runbook/Wiki/rebuild packet
acceptance owner
effect state
new readiness disposition

Do not close a gap because a file, test or code path exists without the required evidence.

---

Source: docs/reconstruction/REBUILD_READINESS_GAP_REGISTER.md — ctc repository · This page is an English translation of the source document. Identifiers, file paths and code symbols are unchanged.