Wiki Repository Boundary¶

Status: CANONICAL REPOSITORY WIKI INDEX — NO PUBLICATION AUTHORIZED
User-content store: T_WIKI_PAGE, rendered through the Operations Manual
Current Phase state: implementation user hold
Current documentation correction: Appendix O
Current source/render inventory: CURRENT_WIKI_SOURCE_RENDERING_AND_ACCESS_INVENTORY_2026-08-08.md
Current read-only evidence package: RBR-EV-030-READONLY-WIKI-INVENTORY-PREFLIGHT.md
Does not own: Process semantics, Runtime behavior, role authority, Task status, or publication approval

repository draft
!= current T_WIKI_PAGE content
!= published
!= rendered readback
!= target-role accepted

1. Core Inputs¶

2. Current Source And Evidence Inventory¶

Static source inventory:

Read-only environment package:

Current package state:

source inventory: COMPLETE
query/render package: DEFINED
static validation: PASS
database/page/role/asset evidence: NOT RUN
publication: NOT AUTHORIZED

The current user experience is a composition of:

repository catalogue/baseline metadata
+ tenant T_WIKI_PAGE Markdown
+ rendered page under the exact tenant/role
+ mapped application-page access
+ referenced asset readability

Reading only one layer does not establish current Wiki correctness.

3. Current Platform Addenda¶

Identity / Session / Impersonation¶

Current source refresh: PLATFORM_IDENTITY_CURRENT_CONSUMER_REFRESH_2026-08-09.md
Read-only evidence: RBR-IDENTITY-001-READONLY-CURRENT-SURFACE-PREFLIGHT.md

The restricted current addendum covers actor versus subject, direct/user/tenant-only modes, login/session facts, password non-implications and Provider Credential Show/Save identity. It must not publish credential values, session values or target-only controls as current functionality.

Authorization / Access¶

Current source refresh: PLATFORM_AUTHORIZATION_CURRENT_SURFACE_REFRESH_2026-08-08.md
Read-only evidence: RBR-ACCESS-001-READONLY-CURRENT-SURFACE-PREFLIGHT.md

The restricted support addendum covers current Loader, Street Turn, Final Review, AR/QBO and document-send access layers. It must not be published to ordinary field roles before current menu/role/account and rendered-page evidence exists.

Integration / Provider¶

Current source refresh: PLATFORM_INTEGRATION_PROVIDER_CURRENT_SOURCE_REFRESH_2026-08-08.md
Read-only evidence: RBR-INTEGRATION-001-READONLY-CURRENT-SURFACE-PREFLIGHT.md

Current provider guidance must distinguish configured, sent, suppressed, unknown, provider-accepted/local-pending and object-readability states. Provider Credential configured/saved does not establish connectivity.

4. Current Business Addenda¶

Loader Work Assignment¶

Current authority: LOADER_WORK_ASSIGNMENT_CURRENT_SOURCE_CONTRACT_2026-08-08.md

The old Assign Work projection path is a compatibility redirect. Current publication must begin from the current-source addendum and RBR-AWCO-002 evidence.

Final Loading Review¶

Current addendum covers Shipper/CTC comparisons, Avg/Bale warnings, Edit Outbound, stale conflict and missing-response recovery.

Billing / QBO / Files / Email¶

Current source refresh: CTC_BILLING_QBO_FILES_EMAIL_CURRENT_SOURCE_REFRESH_2026-08-08.md
Read-only evidence: RBR-BILL-QBO-FILE-MAIL-READONLY-PREFLIGHT.md

Current Wiki publication still requires DB/rendered/role/provider evidence.

Billing / QBO / Files / Email¶

Current source refresh: CTC_BILLING_QBO_FILES_EMAIL_CURRENT_SOURCE_REFRESH_2026-08-08.md
Read-only evidence: RBR-BILL-QBO-FILE-MAIL-READONLY-PREFLIGHT.md

The current refresh found no material drift in the reviewed AR Billing/QBO, File, Gmail, BOL and Packing List owner blocks. Adjacent Loader, Street Turn, Staff Time and Booking changes remain separate handoff/evidence questions. Current Wiki publication still requires DB/rendered/role/provider evidence.

Street Turn¶

Covers Import Empty create, per-row mixed result, guarded Revert, downstream blockers and unknown-result recovery.

MK Trade / Allocation / Physical Scale¶

Current evidence: MK_TRADE_ALLOCATION_SCALE_CURRENT_EVIDENCE_INDEX_2026-08-08.md

The current addendum preserves Trade derived-read boundaries, Allocation quantity/weight uncertainty and the Physical Scale Gross/Tare and one-writer blockers.

5. Detailed Business Packets¶

Inbound Planning / Loader
Final Loading Review
Yard / Driver
Billing / QBO / Files / Email
MK Order-First Core
MK Inventory Allocation
MK Physical Scale
MK Trade / Cost / Rate / Documents
Street Turn

6. Platform Packets¶

Platform topics are restricted administrator/support content. Do not expose credentials, session values, server paths, provider secrets, access-control internals or incident-sensitive details to ordinary field roles.

7. Required Boundaries¶

Business¶

Loader Complete != Final Review/Inventory/Yard/Driver complete
assignment created != message delivered
local Clock Out != external time synchronized
Street Turn create != physical/export completion
Revert Street Turn != universal downstream rollback
Shipper variance != Loading Difference
Edit Outbound != Confirm or inventory adjustment
local Billing transaction != local container AR confirm
local container AR READY != QBO delivered
QBO provider accepted != local provider reference saved
file metadata/link != readable object
BOL response missing != safe resend
Packing List target/part partial != complete
QuickBooks Time != QBO Invoice
Scale Check-in != Check-out
Scale Check-out != owner finalize/close
Outbound Save != Allocation
Booking Save != all children synchronized
rendered/printed != durable file/email/provider result

Platform¶

Tenant != Profile != Module != Capability != Config != Credential != Authorization
Actor != Subject
Tenant-only impersonation != target-role acceptance
Password changed != every session revoked
Credential shown != Provider verified
Menu visible != Page allowed
Page allowed != API allowed
API allowed != Action allowed
Action allowed != Record allowed
Record allowed != State eligible
request diagnostic != business transition
notification ACK != approval/completion
local commit != provider accepted
provider accepted != local reference saved

8. Required User Page Content¶

Every current procedure explains:

when to use it
who acts
where to enter
identity/date/state to verify
entered versus derived values
primary action
visible result
authoritative reread
next owner
partial/unknown meaning
what not to repeat
correction/recovery
what completion does not imply
last verified environment/role/source
known limitations

Use diagrams when actors, transactions, providers, physical work, partial results or corrections cannot be explained clearly in prose.

9. Current/Future Classification¶

CURRENT VERIFIED/ACCEPTED
CURRENT SOURCE-RECONCILED
CURRENT SOURCE PRESENT / EVIDENCE REQUIRED
HISTORICAL EVIDENCE
TARGET DESIGN
OPEN POLICY / UNKNOWN
MIXED OR MISLEADING

Follow the owning current source-authority document. Do not copy stale source or candidate labels into multiple Wiki files.

10. Current Wiki Inventory¶

Evidence package:

RBR-EV-030 — Current Wiki Inventory

Per priority slug it covers:

current schema variant;
row state and Markdown hash;
repository baseline versus DB override;
page-route mapping;
rendered page;
intended and denied role visibility/findability;
asset metadata/readability;
current/stale/historical/target classification;
mobile/keyboard/accessibility.

Current status:

DEFINED / NOT AUTHORIZED / NOT RUN

This index does not authorize a database read, authenticated page read, screenshot, asset read or publication.

11. Publication Sequence¶

current row/rendered read
-> source/Process/role comparison
-> bounded named-slug draft
-> Process and role review
-> exact publication authorization
-> write once
-> DB and rendered readback
-> findability/mobile review
-> observation
-> rollback or retirement

Use WIKI_CONTENT_REVIEW_PUBLICATION_AND_ROLLBACK_CHECKLIST.md.

12. Current State¶

repository packets: PRESENT
current Wiki static source inventory: COMPLETE
current Wiki DB content: NOT READ
rendered role-specific content: NOT VERIFIED
publication: NOT AUTHORIZED
field acceptance: INCOMPLETE

13. Maintenance¶

Update Wiki packets after source, identity, role, Process, provider, physical, data, route, recovery or migration changes. Preserve stable user topics while current PHP routes later change.

---¶

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

In this section¶

Document	Contents
manual	Wiki Repository Boundary
program-closed	Prior Programme (closed)