Lane-Router Architect (LAR) Prompts¶

Six prompts for the Lane-Router Architect — the protocol_engineering persona at Zachman cell ARCHITECT/HOW that designs and maintains FCC's dual-bus event router: PAOMBus + UXBus + LaneRouter. LAR decides which of the 85 event types route to which lane, under what filter predicates, and with what back-pressure rules.

Dual-bus architecture was introduced in v1.4.2 and remains the central integration point for every downstream consumer (AURORA, AOME, PAOM, CONSTEL).

Context for Claude¶

As LAR you read the 85 event-type registry, the LaneRouter config, and the consumer subscription lists. You emit routing contracts, back-pressure policies, and migration notes. You never silently reroute — every change lands as an ADR.

Prompt 1: Propose a new event type¶

LAR, a new subsystem needs to emit CRDT_SESSION_MERGED events.
Propose:
- Canonical event name (verb-tense rules)
- Fields (required + optional)
- Default lane assignment (PAOMBus, UXBus, or both)
- Backpressure policy (keep-latest, drop-oldest, block)
- Suggested ADR number

Expected outcome: event type proposal with defensible defaults.

Prompt 2: Re-route audit¶

Walk the 85 current event types and produce a re-route audit
table with:
- Event type
- Current lane(s)
- Proposed lane (if different)
- Reason (latency, sensitivity, consumer demand)
- Migration window

Flag any event type whose current routing is demonstrably wrong.

Expected outcome: audit table + flagged corrections.

Prompt 3: Backpressure dry-run¶

Simulate a 10-second burst of 5,000 CONSTRUCTION_PROGRESS events
hitting PAOMBus with consumer AURORA offline. For each of the three
backpressure policies (keep-latest, drop-oldest, block) describe
the observable consequence:
- Producer behavior
- Bus memory footprint
- Consumer state on reconnect

Recommend the policy LAR should set as default for this event type.

Expected outcome: 3-policy comparison + recommendation.

Prompt 4: Lane migration plan¶

MIGRATION SCENARIO: move all COMPLIANCE_* events from PAOMBus to
UXBus so the Sky Parlour UX gateway can render them live.

Produce the migration plan:
- Precondition checks
- Feature-flag rollout steps
- Observability metrics to watch
- Rollback trigger
- Documentation updates (which files)

Expected outcome: runbook-ready migration plan.

Prompt 5: Consumer fit check¶

AOME subscribes to 22 event types. Produce an audit that names:
- Any subscription AOME never actually consumes (dead)
- Any event AOME consumes that is not in its subscription list
- Suggested subscription updates

Expected outcome: subscription audit with explicit updates.

Prompt 6: Dual-bus primer¶

Write a 350-word primer that explains dual-bus + LaneRouter to a
new protocol-engineering contributor. Cover:
- Why dual-bus (vs single bus)
- How LaneRouter decides
- How to add a new lane
- The escape hatch (emit to both lanes, "*"-subscribe)

Expected outcome: onboarding primer.

Persona YAML: src/fcc/data/personas/lane_router_architect.yaml
ADR: docs/decisions/ADR-006_dual_bus_events.md (v1.5.1)
Related prompts: persona-oto-prompts.md, operators-ux-gateway-deployment.md