Parked BY DESIGN — each wakes on its written trigger, never by drift:
- Oracle provider — first real customer demand
- auth saml/ldap · multiTenancy path-prefix/db-per-tenant — no scenario card fired these
- Kafka rider for campaign fan-out — the 30M-scale trigger (constraints 5/6 in the jobs RFC)
- specdrift wiring-row OR-semantics per package — TRIGGER FIRED 2026-07-24: CorPay's own stop-gate/nightly drift emits SPEC0203 noise (Goldpath.Jobs justified by bulk/archival, flagged via the notification/campaign rows). Lands with the next specdrift train (0.4.2/0.5) alongside --fail-on and the embedded schema.
- Automated schema-affecting-package detection — the first upgrade incident a [schema] CHANGELOG marker would not have prevented
- spec engine as its own OSS — per docs/rfc/spec-engine-v1.md decision points
2026-07-24: UI-phase line removed — the trigger fired long ago; U0/U1 shipped (docs/rfc/goldpath-console.md, ACCEPTED; kit live). This ledger keeps only items whose triggers have NOT fired.
- MassTransit exit — Mediant-transport feasibility RFC — OWNER-PRIORITIZED (2026-07-26, "kesinlikle atlamayalım"): opens at the START of the module phase (after UI U1–U4), fed by Insurance/Telco real-usage inventory of the MT surface we actually consume (EF outbox, inbox dedup, retry/redelivery, topology, test harness). The RFC is a GO/NO-GO gate on growing Mediant toward transport (zero third-party licensing in the core path); earlier triggers unchanged: unpatched CVE / v8 maintenance window closing / a customer licensing constraint. Ledger: goldpath-messaging.md D1.
Parked BY DESIGN — each wakes on its written trigger, never by drift:
2026-07-24: UI-phase line removed — the trigger fired long ago; U0/U1 shipped (docs/rfc/goldpath-console.md, ACCEPTED; kit live). This ledger keeps only items whose triggers have NOT fired.