CTC System Reconstruction Dossier¶
- Status:
CURRENT RECONSTRUCTION NAVIGATION — IMPLEMENTATION USER HOLD - Current status:
docs/ROADMAP.md - Current direction and hold:
Canonical Context - Current Cloud integration:
CLOUD_PARALLEL_DOCUMENTATION_INTEGRATION_2026-08-10.md - Current read-only evidence integration:
PARALLEL_READONLY_EVIDENCE_INTEGRATION_2026-08-10.md - Cross-family review:
CROSS_FAMILY_RECONSTRUCTION_CONSISTENCY_REVIEW.md - Parent coverage:
SYSTEM_RECONSTRUCTION_COVERAGE_MATRIX.md - Evidence register:
REBUILD_READINESS_GAP_AND_EVIDENCE_REGISTER.md - Current execution worksheets:
CURRENT_OPERATIONAL_EVIDENCE_WORKSHEET_INDEX_2026-08-08.md - Packet source-drift baseline:
HIGH_RISK_PACKET_SOURCE_DRIFT_REVIEW_2026-08-08.md - Document conflict/retirement register:
DOCUMENT_AUTHORITY_CONFLICT_AND_RETIREMENT_REGISTER.md
detailed documentation
!= current runtime evidence
!= target-role acceptance
!= provider/physical verification
!= restore verification
!= M3
!= M4
1. Current Documentation Lane¶
Allowed:
- inspect current source and history;
- reconcile Process/data/interface/Runbook/Wiki packets;
- correct source drift and stale current/historical labels;
- add diagrams and evidence definitions;
- document unknowns and policy decisions;
- define read-only environment packages without executing them;
- inventory historical/redirect consumers before retirement.
Not authorized:
- Runtime/schema/data changes;
- role/menu/config/credential/account changes;
- provider/service/scheduler/deployment effects;
- file/object or backup/restore effects;
- Wiki DB publication;
- Phase implementation.
2. Core Reconstruction Documents¶
| Document | Owns |
|---|---|
CTC_SYSTEM_REBUILD_BLUEPRINT.md |
current/target system assembly |
CAPABILITY_REBUILD_PACKET_TEMPLATE.md |
complete per-capability packet format |
DATA_AUTHORITY_AND_STATE_RECONSTRUCTION_MAP.md |
data/state/identity relationships |
INTERFACE_INTEGRATION_AND_EFFECT_CATALOG.md |
queries/commands/events/effects |
REBUILD_DEPENDENCY_AND_BOOTSTRAP_SEQUENCE.md |
rebuild/deploy/restore order |
REBUILD_READINESS_GAP_AND_EVIDENCE_REGISTER.md |
evidence package families and status vocabulary |
CLOUD_PARALLEL_DOCUMENTATION_INTEGRATION_2026-08-10.md |
current 2026-08-10 source-successor and evidence-package delta |
PARALLEL_READONLY_EVIDENCE_INTEGRATION_2026-08-10.md |
current Production read-only evidence integration and contradiction review |
DOCUMENT_AUTHORITY_CONFLICT_AND_RETIREMENT_REGISTER.md |
historical conflict/retirement handling |
DOCUMENT_PATH_CONSUMER_AND_RETIREMENT_INVENTORY_2026-08-08.md |
compatibility path consumers and retirement gates |
The 2026-08-10 integration document controls when an older drift/register row conflicts with one of the six refreshed families below. Historical files remain retained evidence.
3. Current Platform Source Successors¶
Identity / Session / Impersonation¶
PLATFORM_IDENTITY_CURRENT_CONSUMER_REFRESH_2026-08-10.mdCurrent consumer matrix
Current source now includes request-time active-user/role invalidation on validated paths. Central all-session revocation, privileged reauthentication and complete standalone-entrypoint coverage remain unestablished. The credential reveal API is source-present, but the reviewed Admin Console UI has no current reveal caller.
Tenant / Config / Credential¶
PLATFORM_TENANT_CONFIG_CREDENTIAL_CURRENT_SOURCE_REFRESH_2026-08-10.mdCurrent resolution matrix
Managed encrypted SECRET.<KEY> storage, legacy compatibility reads, separate reveal/replace semantics and secret-safe diagnostics are current source facts. Managed credential removal, profile binding, entitlement authority and universal cache invalidation remain open.
Deployment / Recovery¶
PLATFORM_DEPLOYMENT_RECOVERY_CURRENT_SOURCE_REFRESH_2026-08-10.mdCurrent component matrix
Encrypted tenant credentials are not recoverable from DB ciphertext alone without compatible CTC_TENANT_SECRET_KEY key material or an approved rotation/re-encryption/reauthorization procedure. Git promotion, runtime application, liveness, readiness, business acceptance, backup existence, restore verification and provider reconciliation remain distinct states.
Authorization / Access¶
PLATFORM_AUTHORIZATION_CURRENT_SURFACE_REFRESH_2026-08-08.mdCurrent action matrix
Audit / Transition¶
CANONICAL_AUDIT_AND_TRANSITION_CONTRACT_CORRECTION_2026-08-08.mdPLATFORM_AUDIT_CURRENT_WRITER_AND_EVIDENCE_INVENTORY_2026-08-08.md
Integration / Provider¶
PLATFORM_INTEGRATION_PROVIDER_CURRENT_SOURCE_REFRESH_2026-08-08.mdPLATFORM_PROVIDER_CREDENTIAL_MANAGEMENT_CURRENT_SOURCE_2026-08-08.mdCurrent effect matrix
4. Current CTC Business Corrections¶
CURRENT_SOURCE_DOCUMENTATION_MAINTENANCE_2026-08-11.md— current Loader, Street Turn, Final Loading Review, KJDatabase/Transition Audit and lifecycle-label successor
Loader Work Assignment¶
LOADER_WORK_ASSIGNMENT_RECONSTRUCTION_INDEX_2026-08-08.mdLOADER_WORK_ASSIGNMENT_CURRENT_SOURCE_CONTRACT_2026-08-08.mdCurrent evidence ledger
Current source has route-owned QUEUE_WORK_ASSIGNMENT/FINAL_DRAFT rows and a separate typed ASSIGNMENT_DATA helper. The canonical application contract still requires evidence and policy acceptance.
Final Loading Review¶
Current operator addendum
Street Turn¶
Billing / QBO / Files / Email¶
Read-only current-state preflight
5. Current MK Source Successors¶
Trade / Cost / Rate / Document Outputs¶
The detached d964983... candidate is historical and does not own current Trade facts.
Inventory Allocation¶
Current action matrix
Current source includes partial allocation UI, active OPEN/PARTIAL source lots, target item creation, separate quantity/weight persistence and a conditional remaining-weight guard. Quantity/UOM/reversal policy remains open.
Physical Scale¶
Current four-flow matrix
Purchase / Doortrade = Gross-in -> Tare-out
Sales / Export = Tare-in -> Gross-out
Older all-flow Gross and missing integrated Check-out statements are historical. Physical/device and target-role evidence remain not run.
6. Wiki Inventory¶
repository draft
!= current T_WIKI_PAGE content
!= publication
!= rendered role-specific verification
No Wiki read or publication was performed by CTC-CDOC-001 through 007.
7. Rebuild Reading Order¶
Product and Context
-> current Roadmap / hold
-> current Cloud integration
-> family current source successor
-> Process/data/interface contract
-> Runbook / Wiki projection
-> read-only evidence package
-> separately authorized runtime evidence
-> migration packet only after applicable gates
Current source and accepted business policy control over historical plans.
8. Current Readiness¶
six 2026-08-10 parallel documentation families: INTEGRATED
major business documentation: DETAILED INPUT
major platform documentation: DETAILED INPUT
current source freshness: SOURCE-RECONCILED FOR NAMED SUCCESSORS
role/DB/session/provider/physical/Wiki/deployment evidence: INCOMPLETE
accepted M3 families established here: NONE
M4 families: NONE
implementation: USER HOLD
The RBR-*-002 packages are DEFINED / NOT AUTHORIZED / NOT RUN until a later explicit instruction authorizes the named environment and evidence scope.
9. Current Handovers¶
10. Maintenance¶
When a named family changes, update its source successor and evidence package first, then update this navigation once. Preserve historical evidence and compatibility redirects until consumer caller-zero. Do not infer Runtime, role, provider, physical, Wiki, backup/restore or migration acceptance from documentation alone.
---¶
Source:
docs/reconstruction/README.md— ctc repository · This page is an English translation of the source document. Identifiers, file paths and code symbols are unchanged.