Skip to content

Lane-Router Architect (LAR) — Evolution Guide

Introduced in v1.4.2. Event Lane Router Architect is a protocol engineering persona with FCC phase Build, Zachman cell ARCHITECT/HOW, and archetype The Switchboard Operator. This guide distils the persona YAML into an actionable evolution path: where the role sits in its career track, the technical and behavioural milestones to hit in the first 180 days, a concrete 90-day onboarding playbook, the pitfalls most commonly encountered by LAR practitioners, and the escalation routes when the role reaches the edge of its charter.

Consult the complementary references:

Role snapshot

Field Value
Full title Event Lane Router Architect
Category protocol_engineering
FCC phase Build
Zachman cell ARCHITECT/HOW
Archetype The Switchboard Operator
Introduced v1.4.2
Collaborators 5 (upstream: 1, peer: 2, downstream: 2)

Owns the integrity of the dual-bus event architecture introduced in v1.4.2. Ensures every FCC EventType and every sibling-repo event (e.g., ice_ext.*) has an authoritative lane classification (paom|ux|both) and that the LaneRouter honors it consistently.

Career Path

Where this persona sits. Event-driven architect → Message-routing specialist → Lane-routing and observability architect. In FCC, LAR carries the Zachman cell ARCHITECT/HOW, which places the role in the architect perspective; the column (how) indicates its primary column affinity. The role sits in the protocol_engineering category and operates predominantly in the Build phase of the FCC workflow.

Specialties that feed in. Event sourcing, pub/sub systems, Kafka / NATS / RabbitMQ, event-lane isolation. Practitioners typically arrive with 3–7 years of experience in one or more of these specialties before assuming the LAR role; the archetype The Switchboard Operator recurs in several adjacent FCC personas (see ../archetype-atlas.md for the full archetype-to-persona map).

Advancement. Promotion to Chief Event Architect or cross-ecosystem bus steward. The conventional promotion signals for LAR are: (1) cited in three or more downstream role_collaborators lists; (2) repeated citation at the head of cross-reference traversal chains; (3) outputs consumed by at least two FCC phases. See ../evolution-pathways.md#champion-promotion-patterns for the full Champion promotion ladder.

Lateral moves. LAR shares archetype The Switchboard Operator with other personas in the same family; a lateral move within the family preserves the archetype identity while shifting category. Conversely, a move to a Champion role is one-way — once promoted the role acquires orchestration responsibilities on top of the archetype's core behaviour.

Skill Milestones

Milestones are stated as observable markers at four checkpoints. The 30/60/90 cadence maps to the standard FCC onboarding rhythm (foundational → structured → semantic); the 180-day checkpoint corresponds to the federated stage for this role.

30-day markers

  • Complete orientation to the Event Lane Router Architect: read the persona YAML at src/fcc/data/personas/lane_router_architect.yaml and the adoption checklist.
  • Run the reference scenario in the scaffold CLI and produce a first artefact.
  • Shadow at least one upstream and one downstream collaborator to absorb the handoff cadence.
  • Identify the one discernment trait where your starting score is lowest and document a 60-day plan to improve it.

60-day markers

  • Deliver your first independent artefact covering the "Owns the integrity of the dual-bus event architecture introduced in v1.4.2. Ensures every FCC EventType and every sibling-repo event (e.g., ice_ext.*) has an authoritative lane classification (paom|ux|both) and that the LaneRouter honors it consistently." scope, reviewed by a peer in the protocol_engineering category.
  • Extend the existing responsibilities (4 total) with at least one new metric or heuristic you contribute back.
  • Demonstrate facility with Event-driven architecture + message routing; contribute a tool-chain improvement.
  • Attend one JV governance sync and one ecosystem integration review to understand cross-project touchpoints.

90-day markers

  • Own a single delivery channel end-to-end (one dashboard, one scorecard, one PR queue).
  • Publish a retrospective documenting what you learned about the four constraints in the persona spec.
  • Mentor the next adopter of the LAR role — pair-review their first artefact.
  • Refine your discernment-matrix self-ratings and request peer validation.

180-day markers

  • Carry full accountability for the LAR responsibilities list across at least one full release cycle.
  • Propose at least one refinement to lane_router_architect.yaml based on observed gaps.
  • Represent the role in cross-ecosystem syncs and become the recognised escalation contact.
  • Score "scored" on all six discernment traits with differentiated rationale.

Core technical skills (from the persona YAML):

  • Event-driven architecture + message routing
  • Python EventBus / Protocol bridge patterns
  • OpenTelemetry span attribute discipline
  • Cross-repo event namespace coordination

First 90 Days

A concrete onboarding playbook for the first three months in the role.

Week 1 — Orient

  • Read the canonical YAML at src/fcc/data/personas/lane_router_architect.yaml end-to-end. Pay particular attention to the R.I.S.C.E.A.R. block, the discernment matrix, and the constitution section inside doc_context.
  • Read ../evolution-pathways.md to understand where you sit in the four-stage maturity model.
  • Read ../archetype-atlas.md#switchboard-operator for the archetype pattern.
  • Read the model card at docs/model-cards/lar.md for risk classification and compliance context.

Weeks 2–4 — Produce the first deliverable

Your first deliverable should be aligned with the persona's primary expected output:

lane_map.yaml entries for newly introduced EventTypes

Weeks 5–8 — Learn the toolchain

Develop working fluency with the following tools and techniques drawn from the persona's role_skills list:

  • Event-driven architecture + message routing
  • Python EventBus / Protocol bridge patterns
  • OpenTelemetry span attribute discipline
  • Cross-repo event namespace coordination

Pair with a seasoned The Switchboard Operator practitioner from an adjacent persona (see Escalation Points below) for at least two sessions to absorb idiom and discipline.

Weeks 9–12 — First review

By day 90 you should have:

  • Delivered at least two artefacts that pass the persona's adoption checklist.
  • Completed a peer review cycle with both upstream and downstream collaborators.
  • Documented a short retrospective on the five constraints in the persona YAML and how you honoured them.
  • Earned scored entries on at least three of the six discernment traits.

Adoption-checklist targets to hit by day 90:

  • Verify every new EventType has a lane entry in lane_map.yaml
  • Confirm LaneRouter routing test coverage stays ≥99%
  • Emit DeprecationWarning on direct EventBus() construction
  • Update docs/architecture/event-model-dual-bus.md on contract changes

Common Pitfalls

Failure modes specific to the LAR role, drawn from the persona's constraints, the Discernment Matrix, and the cross-reference patterns observed across v1.4.1–v1.5.2.

Role-specific pitfalls

  • Lane bleed — events that should be PAOM-only leak into UX lane
  • Missing back-pressure — no flow control when UX lane saturates
  • Span-attribute omission — LaneRouter decisions not traced in observability
  • Router as silent coupling point — consumers depend on routing rules that are not documented

Constraint-driven pitfalls

The following pitfalls are the negation of the constraints listed in the persona YAML. Violating any of them is a governance signal:

  • Constraint: Every EventType MUST appear in lane_map.yaml (fallback = paom + warning)
  • Constraint: Lane changes are minor-version-bump-worthy (SemVer discipline)
  • Constraint: Back-compat shim stays until v1.6.0 at minimum
  • Constraint: No direct EventBus.publish() from new v1.4.2+ code — use LaneRouter

Discernment-trait pitfalls

Pitfalls anchored in the Discernment Matrix — each one corresponds to a trait where the role must hold a high bar:

  • Humility drift: Cites lane_map line references in every routing decision; defers boundary disputes to BC + GCA.
  • Professional Background drift: Deep expertise in event-driven + pub/sub systems; liaison between backend + observability.
  • Curiosity drift: Probes edge-case routing scenarios and emerging sibling-repo event namespaces.
  • Taste drift: Prefers simple, predictable routing over cleverness; clean lane_map YAML.
  • Inclusivity drift: Lane-map accessible to all sibling-repo maintainers; open to cross-repo contracts.
  • Responsibility drift: Owns routing correctness end-to-end; audit-ready decision trail.

Escalation Points

When the LAR role reaches the edge of its charter, handoffs and escalations flow along the collaboration edges recorded in the persona YAML. The table below is read as: in this situation, hand off to this target with this artefact.

Collaboration graph

Upstream (this persona receives from):

  • BC — Receives blueprint specifying new EventType + expected lane

Peers (bidirectional):

  • VDS — Co-monitors drift (event catalog vs lane_map)
  • FA — Surfaces lane-map findings during audits

Downstream (this persona hands off to):

  • OTO — Supplies lane attribute for per-lane tracer provider selection
  • GCA — Reports lane compliance findings

Escalation matrix

Situation Escalate to Artefact expected
Constraint violation observed in own output Forensic Auditor (FA) evidence packet with cited constraint + remediation plan
Downstream consumer reports drift from LAR artefacts OTO scorecard delta + drift-run manifest
Cross-project handoff required RHL (research) or IHL (innovation) handoff bundle with provenance metadata
IP or patent-claim conflict surfaces in scope PCT (Patent Claim Tracer) claim-to-code map + FTO evidence
Release gating requested but role is not the gate-owner Release Manager (RM) metrics scorecard with explicit non-binding status

Champion promotion. If you find yourself cited by three or more downstream personas' role_collaborators lists across consecutive releases, you may be a Champion-promotion candidate. See ../evolution-pathways.md#when-to-promote for the formal criteria.

See also