📖About

This write-up is withheld because the input does not include a verified public projection from the owning app under the publication contract.

📖Usage

Publication requires validation through shared.carolopedia_publication. The supplied internal prose alone does not establish public approval.

📖Purpose

The Bypass Shipper ships an initiative via canonical bypass (skipping the normal approval gates) by writing a BYPASS-tagged row to bypass_audit_trail with a UTC timestamp, the initiative id, the acting agent, and the reason, then returns the shipped status with the new audit id and tag - exactly as it ran inside the app before. It does NOT touch the bypass book, cookbook, or initiative status rows; only the audit-trail row. Carries its own DB path so it is self-contained.

📖Duties

- Triggered whenever an operator ships an initiative via the initiatives app bypass-ship endpoint.
- Writes a single BYPASS-tagged row to bypass_audit_trail with timestamp, initiative id, agent, and reason.
- Returns the shipped status with the new audit id and tag.
- Records a session_event and a Palantir post on every successful ship.

📖Constraints

- Owns its own database path (the the initiatives ledger the app used); never relies on a caller's connection.
- Behavior is preserved exactly from the app.
- Touches only the audit-trail row, never the bypass book, cookbook, or initiative status rows.
- Reached only through the initiatives app's shared shim, never imported by the app directly.
- Accountability logging is best-effort and never breaks the ship.

👤Belongs to

• Elrond