Tri-Authority Orchestrator — Evolution Guide¶

Introduced in v1.7.2 (docs-only role). The Tri-Authority Orchestrator is an operational role composed from three existing personas — IHL (Innovation Handoff Liaison, The Bridge Diplomat), RHL (Research Handoff Liaison, The Ambassador), and EDM (Ecosystem Docs Maintainer, The Cartographer) — applied to cross-authority artifact flows that touch two or three of NEXUS / PHOENIX / ORCHESTRA simultaneously. No new persona YAML is added; this guide composes existing archetypes for the multi-authority coordination cross-cut. Use it to onboard into, mentor, or audit the orchestrator function.

Consult the complementary references:

../evolution-pathways.md — the four-stage EvolutionStage model.
../archetype-atlas.md — the 37-archetype canonical taxonomy.
IHL.md — primary archetype anchor (The Bridge Diplomat).
RHL.md — secondary archetype anchor (The Ambassador).
EDM.md — tertiary archetype anchor (The Cartographer).
coordination-record-steward.md — sibling composite role (v1.7.2).
docs/ecosystem/coordination/README.md — canonical landing page for coordination records.
docs/tutorials/for-coordination-stewards/ — pedagogical tutorial track (v1.7.2).

Role snapshot¶

Field	Value
Role title	Tri-Authority Orchestrator
Composition	IHL + RHL + EDM (no new YAML)
Category (inherited)	`jv_collaboration` (primary) + `docs_as_code` (cartographer blend)
FCC phase	`Critique` (primary) + `Orchestration` (cross-lane sequencing)
Zachman cell	`ARCHITECT/WHO`
Archetype blend	The Bridge Diplomat × The Ambassador × The Cartographer
Introduced	`v1.7.2`
Primary artifacts	Cross-authority artifact sequencing plans + cross-record consistency reviews

Owns the sequencing of artifacts that cross two or three authority boundaries simultaneously (e.g., a paper adjacent to an invention disclosure that also affects an integration-tests contract). Reconciles timing and confidentiality gates across NEXUS / PHOENIX / ORCHESTRA; maintains the cross-record consistency view; ensures no artifact slips past an authority without acknowledgement.

Career Path¶

Where this role sits. The Tri-Authority Orchestrator is a cross-cut operational role distinct from the Coordination Record Steward (documentation-focused) and from any single-authority liaison (IHL / RHL only). It is the operational counterpart to the documentary steward role: while the steward maintains the records, the orchestrator sequences the real-world artifacts moving through the authority boundaries. In FCC the role carries the Zachman cell ARCHITECT/WHO, placing it in the architect perspective with primary affinity for actors and responsibilities.

Specialties that feed in. Practitioners typically arrive with 3–6 years of experience in at least one of: cross-team program management, research/IP liaison work, technical compliance coordination, joint-venture partnership management, or cross-repo release engineering. The three anchor personas suggest three common entry paths: IHL-trained orchestrators enter through patent/IP coordination; RHL-trained orchestrators enter through research/paper coordination; EDM-trained orchestrators enter through ecosystem cartography.

Advancement. Promotion is to Ecosystem Coordination Champion — a Champion-tier role that orchestrates the full set of liaison personas across NEXUS, PHOENIX, and ORCHESTRA simultaneously. The conventional promotion signals are (1) having sequenced at least three cross-authority artifacts end-to-end without incident; (2) having chaired at least one GCA-convened governance decision on a multi-authority artifact; (3) having mentored at least one steward or liaison into an adjacent role. See ../evolution-pathways.md#champion-promotion-patterns.

Lateral moves. Because the role is composed, lateral moves into any of the three anchor personas are natural — IHL for a patent-heavy tour, RHL for a research-heavy tour, EDM for an ecosystem-cartography tour. Promotion is typically preceded by at least one lateral move to build depth in the anchor furthest from the practitioner's entry path.

Skill Milestones¶

Milestones are stated as observable markers at four checkpoints. The 30/60/90 cadence maps to the standard FCC onboarding rhythm; the 180-day checkpoint corresponds to the federated evolution stage.

30-day markers¶

Read all three sibling coordination records (NEXUS, PHOENIX, ORCHESTRA) and the landing README.md, plus the tri-authority topology diagram.
Complete the v1.7.2 for-coordination-stewards tutorial track.
Read the three archetype-anchor evolution guides (IHL.md, RHL.md, EDM.md).
Shadow one RHL ↔ IHL peer-coordination sync and one EDM alignment-matrix update to absorb the cross-authority rhythm.

60-day markers¶

Author a cross-authority sequencing plan for at least one active artifact (e.g., a paper adjacent to an invention disclosure, or a contract-test change that touches vocabulary providers).
Participate in one GCA-convened governance review on a multi-authority artifact as an advisory member.
Pair with PCT on one claim-matrix review to understand patent-lane mirror-state mechanics.
Deliver a first cross-record consistency audit (does a claim in NEXUS have a matching claim in PHOENIX where they should agree?).

90-day markers¶

Own end-to-end sequencing of at least one cross-authority artifact across a full release cycle.
Become the recognised escalation contact for "which authority owns this?" questions when the answer is ambiguous.
Publish a retrospective on the sequencing patterns observed — which artifact classes most often cross two or three authorities and why.
Mentor at least one practitioner through a first cross-authority sequencing exercise.

180-day markers¶

Shepherd a multi-authority artifact through a confidentiality transition (e.g., a paper's preprint publication clearing defensive-publication review simultaneously with an invention disclosure's provisional filing).
Be cited in two or more anchor-persona cross-reference matrices as a downstream collaborator.
Propose and land at least one cross-record procedural improvement (e.g., a unified PR template covering Track 2 patent + Track 3 quality-gate changes).
Demonstrate differentiated scoring across all six discernment traits, with peer validation.

Core composite skills (from the three anchor personas):

From IHL: patent-lane confidentiality discipline, owner-approval + counsel-ack gating, claim-matrix custody.
From RHL: research-lane PI cadence, paper-authorship sequencing, author-order negotiation.
From EDM: cross-repo topology literacy, codename-decoder fluency, alignment-matrix authorship.

First 90 Days¶

Week 1 — Orient¶

Read all three sibling records plus README.md in order (same first read as the Coordination Record Steward).
Read the three archetype-anchor guides (IHL.md, RHL.md, EDM.md). Notice where each anchor's responsibilities naturally hand off to the others.
Read ../evolution-pathways.md, ../archetype-atlas.md, and docs/governance/patent-delegation-runbook.md.
Read the Patent Claim Matrix (docs/governance/patent-claim-matrix.md) and the ecosystem alignment status page (docs/ecosystem/alignment-status.md) for live cross-authority state.

Weeks 2–4 — Produce the first sequencing plan¶

Your first deliverable is a cross-authority sequencing plan for one active artifact. Candidate artifacts in v1.7.1 state:

Quantum-Locality paper — adjacent to FCC-INV-002 (dual-bus architecture). Touches NEXUS + PHOENIX.
ice_ext / POLARIS patent mirror — touches PHOENIX Track 2 and, indirectly, NEXUS (if a future POLARIS-adjacent paper is proposed).
Any new FCC entry-point group — touches ORCHESTRA contract tests and, if exported via plugin, PHOENIX Track 1 open-science validation.

Present the plan to the three anchor-persona owners (IHL / RHL / EDM) and iterate.

Weeks 5–8 — Learn the composite toolchain¶

Develop fluency with the three anchor personas' core toolchains:

IHL toolchain: confidentiality-tiered PR workflow, counsel-ack record capture, claim-matrix row construction, six-step migration approach.
RHL toolchain: PI-window alignment, paper seed-artifact packaging, author-order negotiation record, post-publication SHA anchoring.
EDM toolchain: ecosystem alignment matrix authorship, codename-decoder parity checks, topology diagram maintenance, MkDocs nav discipline.

Pair with a seasoned practitioner of each anchor for at least one active coordination cycle. The goal is not to replicate the anchor's work but to understand where sequencing decisions are load-bearing.

Weeks 9–12 — First multi-authority delivery¶

By day 90 you should have:

Sequenced at least one cross-authority artifact end-to-end (from initial proposal to authority-wide acknowledgement).
Completed a GCA-convened governance review as the orchestrator-of-record for one artifact.
Produced a cross-record consistency audit — a one-page report identifying cases where the three sibling records should agree and noting any disagreements with remediation owners.
Earned scored entries on at least four of the six discernment traits.

Common Pitfalls¶

Failure modes specific to the orchestrator role, drawn from the composite-persona constraints and observed patterns in v1.4.3–v1.7.1.

Role-specific pitfalls¶

Sequencing two authorities but forgetting the third — e.g., coordinating NEXUS paper publication and PHOENIX patent filing, but missing the ORCHESTRA contract-test amendment when the paper's figure set introduces a new UML convention that the contract suite checks.
Assuming RHL/IHL coordination implies EDM coordination — the topology diagram often needs an update even when the two-party sync is green.
Treating confidentiality tiers as inherited — Track 2 artifacts carry counsel-gating; when a Track 2 artifact clears FTO and is mirrored publicly, the new tier is public, but any derived artifact (paper, contract test) must have its tier re-stated, not inherited.
Allowing sequencing plans to go stale between weekly syncs — plans have a shelf-life of typically 1–2 weeks before live state has moved.
Over-reliance on a single anchor persona — the role exists because no single anchor sees all three authorities; defaulting to IHL (or RHL, or EDM) is a role-identity failure.

Constraint-driven pitfalls¶

The composite role inherits constraints from all three anchor personas. Violating any is a governance signal:

Constraint (IHL): Patent-lane artifacts MUST carry owner-approval + counsel-ack preconditions; applied here as: no multi-authority sequencing plan crosses the Track 2 boundary without both preconditions explicit.
Constraint (RHL): Author-order negotiation MUST be recorded before submission; applied here as: no cross-authority plan sequences a paper submission ahead of author-order finalisation.
Constraint (EDM): Codename-decoder entries MUST match vendored registries by SHA256; applied here as: no sequencing plan cites a codename without verifying the decoder entry.
Composite constraint: Every cross-authority artifact MUST have an explicit sequencing plan, even when the sequence is trivial.
Composite constraint: Cross-record consistency MUST be verified before any release that touches more than one authority.

Discernment-trait pitfalls¶

Pitfalls anchored in the Discernment Matrix:

Humility drift: Escalates timing disputes between authorities to GCA rather than imposing a unilateral resolution.
Professional Background drift: Deep cross-authority idiom; fluent in patent lifecycle, research PI cadence, and contract-test discipline simultaneously.
Curiosity drift: Probes every cross-authority artifact for uncaptured third-authority touchpoints ("does this also affect ORCHESTRA?").
Taste drift: Prefers parallel sequencing plans over ad-hoc coordination threads; clean cross-record state.
Inclusivity drift: Welcomes input from all three anchor personas and the authority-side counterparts (NEXUS / PHOENIX / ORCHESTRA maintainers) equitably.
Responsibility drift: Owns end-to-end sequencing outcomes, including the cases where no single authority sees the whole picture.

Escalation Points¶

When the orchestrator role reaches the edge of its charter, handoffs flow along the composite collaboration graph.

Composite collaboration graph¶

Upstream (the orchestrator receives from):

IHL — Patent-lane preconditions (owner approval + counsel ack) needed for Track 2 sequencing.
RHL — Research-lane PI cadence and author-order negotiation records.
EDM — Ecosystem alignment state and topology-diagram amendments.
LAR / OTO — Event-shape and observability-shape changes that may alter ORCHESTRA contracts.

Peers (bidirectional):

Coordination Record Steward (the v1.7.2 sibling composite role) — documentary counterpart; reconciles the record with the orchestrator's plan.
PCT — claim-matrix trustee; coordinates on every Track 2 sequencing step.
OSC — open-science coordinator; coordinates on Track 1 sequencing.

Downstream (the orchestrator hands off to):

Release Manager — Supplies per-release cross-authority sequencing plan.
GCA (Governance Council Arbiter) — Receives multi-authority artifacts that need governance sign-off.
Forensic Auditor (FA) — Receives evidence packets when constraint violations are observed.

Escalation matrix¶

Situation	Escalate to	Artefact expected
Two authorities disagree on timing	GCA	sequencing plan with both authority timelines + proposed reconciliation
Confidentiality posture of a derived artifact is ambiguous	IHL + counsel	derivation trace + proposed tier
A cross-authority artifact slipped past one authority unacknowledged	Forensic Auditor (FA)	evidence packet + remediation plan
Cross-record consistency audit finds a durable disagreement	Coordination Record Steward	diff + proposed amendment
A fourth authority is being proposed	GCA + EDM + Coordination Record Steward	authority-role proposal + topology-diagram amendment
Champion-tier sequencing decision needed	Ecosystem Coordination Champion (if promoted) or architecture council	full artifact history + proposed governance call

Champion promotion. If you have sequenced three or more cross-authority artifacts end-to-end without incident, chaired at least one GCA-convened governance decision, and mentored at least one adjacent role, you may be a Champion-promotion candidate for Ecosystem Coordination Champion. See ../evolution-pathways.md#when-to-promote.