Skip to content

CTC Document Authority Conflict And Retirement Register

1. Dispositions

CORRECTED
SUPERSEDED — RETAIN LINK
HISTORICAL EVIDENCE — RETAIN
CURRENT OWNER UPDATE REQUIRED
RETIRE AFTER CALLER-ZERO
UNKNOWN — INVESTIGATE

Delete/rename only after:

successor accepted
+ consumers migrated
+ current Wiki checked for links
+ old path caller-zero
+ history/rollback preserved

2. Current Conflicts

DOC-CONFLICT-001 — Loader assignment single-contract claim

Older source authority and evidence treated the typed ASSIGNMENT_DATA design as the complete current contract.

Current source also uses:

QUEUE_WORK_ASSIGNMENT
COMMODITY_NAME
FINAL_DRAFT

Disposition: CORRECTED.

Current owners:

Old authority path is retained as a redirect.

DOC-CONFLICT-002 — Loader historical Stage package looked executable

Affected:

  • original plan;
  • Stage 0–6 package;
  • local implementation prompt;
  • progress ledger.

Disposition: CORRECTED.

  • original plan = historical user decision;
  • Stage package = historical plan/evidence;
  • prompt = retired;
  • progress = current evidence ledger;
  • current work begins from current source and RBR-AWCO-002.

DOC-CONFLICT-003 — Loader legacy Runbook/Wiki path

Old filenames/content implied a single current typed contract.

Disposition: SUPERSEDED — RETAIN LINK.

Current successors:

Repository consumers still exist. See the path-consumer inventory before any retirement decision.

DOC-CONFLICT-004 — KJDatabase snapshot semantics

Older Architecture/Schema shorthand described KJDatabase as the general before/after business-row snapshot authority.

Disposition: CORRECTED DIRECTLY.

Current owners:

Current rule:

KJDatabase = bounded request/mutation diagnostic metadata
KJDatabase != general immutable business before/after snapshot authority

The direct shorthand in both canonical technical owners now matches the current audit/evidence rule. Business outcome still requires authoritative business-row reread plus process/domain/transition/provider evidence.

DOC-CONFLICT-005 — Transition Audit no-writer statement

Older Schema wording stated that the Transition Audit store had no active writer caller.

Current source contains a selected Loader Transloading transition writer, while current environment schema/activation/rows remain unverified.

Disposition: CORRECTED DIRECTLY / ENVIRONMENT EVIDENCE REQUIRED.

Current canonical wording:

selected Loader writer source present
environment installation/activation/row evidence required
universal Process coverage absent

Evidence:

The selected writer does not establish non-load Work Assignment transition coverage, universal Process coverage, or current Production execution.

DOC-CONFLICT-006 — Final Loading Review packet lag

Current source added:

  • Shipper/CTC comparison;
  • Avg/Bale warnings;
  • selected-row continuity;
  • guarded Pending outbound correction.

Disposition: CORRECTED.

Current owner/addenda:

Evidence: RBR-FLR-001, RBR-FLR-002.

DOC-CONFLICT-007 — Street Turn incomplete documentation

Create and guarded Revert existed in source, but no complete current Process/rebuild/Runbook/Wiki packet existed.

Disposition: CORRECTED.

Current packet:

Evidence: RBR-STREET-001.

DOC-CONFLICT-008 — Phase labels looked active

Older Roadmap/Task labels could be read as current implementation authorization.

Disposition: CORRECTED.

Current owner:

  • Context Appendix O
P2–P12 implementation = USER HOLD
Cloud documentation/source reconciliation = allowed / no Phase progress

DOC-CONFLICT-009 — Detailed documentation inferred as readiness

Disposition: CORRECTED in current coverage and review.

DETAILED INPUT != M3 != M4

DOC-CONFLICT-010 — Wiki draft inferred as current content

Disposition: BOUNDARY RETAINED / READ-ONLY INVENTORY PACKAGE DEFINED.

repository draft
!= current T_WIKI_PAGE read
!= publication
!= rendered verification
!= role acceptance

Current owners:

Current Wiki evidence is still not executed.

DOC-CONFLICT-011 — Archive inferred as backup

Disposition: corrected in deployment/recovery documentation.

business archive != complete database/file/config/credential disaster recovery

DOC-CONFLICT-012 — Loader caller ownership was uncharacterized

Earlier dual-contract documentation identified two representations but did not fully classify current Route/UI callers, typed-helper consumers, and cross-contract guards.

Disposition: CORRECTED — STATIC SOURCE PREFLIGHT COMPLETE.

Current owner:

Confirmed source findings:

active Board/Loader callers use Route representation
typed full-command family has no direct current Route/UI caller located
selected typed guards/locks/readers remain current dependencies
terminal guard sees typed Clock Out only
general Clock Out protection sees typed active rows only
Final Break identity differs by representation
cancellation/request/notification contracts diverge

Current DB population, dynamic invocation, target-role impact, and provider behavior remain evidence questions rather than document conflicts.

DOC-CONFLICT-013 — Repository entrypoint omitted current Appendices and audit precedence

The repository entrypoint required Context only through Appendix M and did not require the rebuild-grade Appendix N, current execution-hold Appendix O, or current audit/transition evidence rule.

Disposition: CORRECTED.

AGENTS.md now requires:

Context Appendix N
Context Appendix O
AUDIT_AND_TRANSITION_EVIDENCE.md

It also requires explicit lifting of Appendix O's hold before any named Phase implementation and states that detailed documentation does not establish M3/M4.

DOC-CONFLICT-014 — High-risk packets lacked current baseline/drift disposition

Several detailed packets either predate later source changes, use a diverged candidate baseline, or omit an exact source SHA.

Disposition: CENTRAL DRIFT CLASSIFICATION COMPLETE / FAMILY REFRESH OPEN.

Current owner:

Current classifications include:

Billing = direct source drift
Identity/Access = consumer surface drift
Integration = effect-owner/caller drift
Deployment = release identity drift
MK Trade = diverged candidate baseline
MK Allocation = baseline missing
MK Physical Scale = baseline missing

This central classification prevents stale source claims but does not replace targeted family re-review.

DOC-CONFLICT-015 — Compatibility paths lacked exact consumer/caller-zero inventory

Redirect and historical Loader paths were retained, but the repository consumers and retirement gate were not listed in one current owner.

Disposition: CONSUMER INVENTORY COMPLETE / RETIREMENT NOT READY.

Current owner:

Current result:

repository caller-zero = no
current Wiki consumers = not read
external consumers = unknown
retirement authorized = no

3. Historical Documents

Retain exact historical evidence:

  • dated research/reference files;
  • candidate-specific reports;
  • old Stage plans;
  • migration/runbook evidence for exact refs;
  • old source snapshots.

Historical evidence must state or inherit its exact source/environment and must not override current source authority.

4. Current Compatibility Paths

Old path Current use Successor Retirement state
LOADER_ASSIGN_WORK_AND_CLOCK_OUT_SOURCE_AUTHORITY.md redirect current Loader source contract/caller inventory/index repository consumers remain
CTC_ASSIGN_WORK_AND_CLOCK_OUT_FUTURE_OPERATOR_RUNBOOK.md redirect current Loader operator addendum repository consumers remain
LOADER_ASSIGN_WORK_CLOCK_OUT_WIKI_PROJECTION_ADDENDUM.md redirect current Loader Wiki addendum repository and unknown Wiki consumers remain
Loader Stage 0–6 files historical evidence current source authority/evidence ledger mixed directory; not caller-zero
original Loader local prompt retired notice future new plan only after explicit activation repository references remain

Use the consumer inventory for exact paths. Retire only after repository, current Wiki and external caller-zero.

5. Closed Documentation Queue Items

Item Result
Repository entrypoint current Appendices/audit precedence CORRECTED
Architecture KJDatabase diagnostic shorthand CORRECTED DIRECTLY
DB Schema KJDatabase diagnostic shorthand CORRECTED DIRECTLY
DB Schema selected Transition writer wording CORRECTED DIRECTLY
Loader source caller inventory CORRECTED / STATIC PREFLIGHT COMPLETE
Loader guard consumer inventory CORRECTED / STATIC PREFLIGHT COMPLETE
Loader evidence fixture/account/cleanup design CORRECTED / EXECUTION WORKSHEET COMPLETE
Loader read-only DB query design CORRECTED / QUERY PACKAGE COMPLETE
Audit read-only environment query design CORRECTED / QUERY PACKAGE COMPLETE
Wiki source/render/access static inventory CORRECTED / STATIC INVENTORY COMPLETE
Wiki read-only inventory query design CORRECTED / QUERY PACKAGE COMPLETE
Wiki inventory template validation PASS
Redirect/historical path consumer inventory COMPLETE / CALLER-ZERO NOT REACHED
High-risk packet baseline/drift classification COMPLETE / FAMILY REFRESH OPEN
Final Review evidence fixture/account/cleanup design CORRECTED / EXECUTION WORKSHEET COMPLETE
Street Turn evidence fixture/account/cleanup design CORRECTED / EXECUTION WORKSHEET COMPLETE

These results are documentation and source-preflight completion only.

6. Remaining Current Corrections And Evidence

Priority Item State
1 Billing/QBO/Files/Email current source refresh direct source drift classified; targeted re-review pending
1 current Authorization/access surface refresh consumer surface drift classified; matrix refresh pending
1 MK Trade current-lineage source refresh diverged candidate baseline classified
1 MK Allocation exact baseline/source refresh baseline missing
1 MK Physical Scale exact baseline/source refresh baseline missing
1 Loader current DB population and dynamic/deployed caller evidence separately authorized read evidence; query package defined
1 Loader terminal/general Clock Out controlled reproduction separately authorized non-Production evidence
1 current Wiki inventory RBR-EV-030 defined; separately authorized read/render evidence
2 audit current schema/writer/row inventory RBR-AUDIT-002 defined; separately authorized read
2 Integration provider-family current source refresh drift classified; targeted re-review pending
2 Identity current consumer/source refresh drift classified; targeted re-review pending
3 compatibility/historical path retirement consumer inventory complete; caller-zero not reached

7. Required Header For Current Packets

Status
Original source baseline
Current review ref
Source relation: ancestor / diverged / missing / current
Current source drift disposition
Current Runtime/source state
Policy state
Evidence state
Wiki state
Phase/implementation state
Effects performed/not performed
Owning authority links

Avoid one ambiguous CURRENT, COMPLETE or SOURCE-RECONCILED label.

8. Effect Boundary

This register authorizes no source deletion, database/provider/Wiki/deployment effect, evidence execution, or Phase activation.

9. Maintenance

Update after source drift, document conflict, successor creation, caller inventory change, evidence acceptance, Wiki publication, migration, or consumer retirement.

---

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