Skip to content

Innovation Handoff Liaison (IHL) — Evolution Guide

Introduced in v1.4.3. FCC-to-PHOENIX Patent & IP Handoff Liaison is a jv collaboration persona with FCC phase Critique, Zachman cell BUSINESS_MANAGEMENT/WHO, and archetype The Bridge Diplomat. 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 IHL practitioners, and the escalation routes when the role reaches the edge of its charter.

Consult the complementary references:

Role snapshot

Field Value
Full title FCC-to-PHOENIX Patent & IP Handoff Liaison
Category jv_collaboration
FCC phase Critique
Zachman cell BUSINESS_MANAGEMENT/WHO
Archetype The Bridge Diplomat
Introduced v1.4.3
Collaborators 6 (upstream: 1, peer: 3, downstream: 2)

Coordinates patent + IP handoffs from the FCC ecosystem to the ai-coe-docs PHOENIX repository. Owns the docs/ecosystem/ice-ext-patent-coordination-*.md series and orchestrates cross-repo PRs for invention migrations. Enforces confidentiality tiers, owner approvals, and counsel acknowledgement gates before any PHOENIX mirror write.

Career Path

Where this persona sits. Innovation manager → IP liaison → PHOENIX-FCC innovation bridge architect. In FCC, IHL carries the Zachman cell BUSINESS_MANAGEMENT/WHO, which places the role in the business management perspective; the column (who) indicates its primary column affinity. The role sits in the jv_collaboration category and operates predominantly in the Critique phase of the FCC workflow.

Specialties that feed in. Patent portfolio management, PHOENIX gate registry, invention disclosure, innovation governance. Practitioners typically arrive with 3–7 years of experience in one or more of these specialties before assuming the IHL role; the archetype The Bridge Diplomat recurs in several adjacent FCC personas (see ../archetype-atlas.md for the full archetype-to-persona map).

Advancement. Promotion to Innovation Council Chair or cross-project IP strategy lead. The conventional promotion signals for IHL 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. IHL shares archetype The Bridge Diplomat 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 FCC-to-PHOENIX Patent & IP Handoff Liaison: read the persona YAML at src/fcc/data/personas/innovation_handoff_liaison.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 "Coordinates patent + IP handoffs from the FCC ecosystem to the ai-coe-docs PHOENIX repository. Owns the docs/ecosystem/ice-ext-patent-coordination-*.md series and orchestrates cross-repo PRs for invention migrations. Enforces confidentiality tiers, owner approvals, and counsel acknowledgement gates before any PHOENIX mirror write." scope, reviewed by a peer in the jv_collaboration category.
  • Extend the existing responsibilities (9 total) with at least one new metric or heuristic you contribute back.
  • Demonstrate facility with Cross-repo PR orchestration (FCC ↔ ai-coe-docs); 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 IHL role — pair-review their first artefact.
  • Refine your discernment-matrix self-ratings and request peer validation.

180-day markers

  • Carry full accountability for the IHL responsibilities list across at least one full release cycle.
  • Propose at least one refinement to innovation_handoff_liaison.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):

  • Cross-repo PR orchestration (FCC ↔ ai-coe-docs)
  • Confidentiality tier enforcement (private repo → private mirror)
  • Patent-tree structural preservation (disclosure/prior-art/provisional/utility/fto/drawings)
  • UML-to-USPTO FIG.N drawing canonicalization
  • Owner + counsel gate negotiation
  • Coordination-record authoring (docs/ecosystem/ice-ext-patent-coordination-*.md)
  • CI drift-check contract authoring (patent-mirror-check.yml integration)
  • Diplomatic negotiation across legal, engineering, and research stakeholders

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/innovation_handoff_liaison.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#bridge-diplomat for the archetype pattern.
  • Read the model card at docs/model-cards/ihl.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:

docs/ecosystem/ice-ext-patent-coordination-*.md records (per release + per invention batch)

Weeks 5–8 — Learn the toolchain

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

  • Cross-repo PR orchestration (FCC ↔ ai-coe-docs)
  • Confidentiality tier enforcement (private repo → private mirror)
  • Patent-tree structural preservation (disclosure/prior-art/provisional/utility/fto/drawings)
  • UML-to-USPTO FIG.N drawing canonicalization
  • Owner + counsel gate negotiation

Pair with a seasoned The Bridge Diplomat 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:

  • docs/ecosystem/ice-ext-patent-coordination-v.md present per release
  • Every invention migration cites source repo + target PHOENIX path
  • Owner approval + counsel acknowledgement evidence captured per handoff
  • Confidentiality tier explicitly recorded (private vs public mirror posture)
  • UML-to-USPTO FIG.N drawings canonicalized per FCC standard
  • CI drift-check contract data exported for patent-mirror-check.yml
  • PCT claim-matrix readiness confirmed before handoff
  • Peer coordination with RHL scheduled if research artifacts adjacent

Common Pitfalls

Failure modes specific to the IHL 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

  • Handoff prior to IP clearance — invention disclosures routed before PHOENIX Tier-1 review
  • Dual-track confusion — innovation content simultaneously in FCC and PHOENIX without a canonical owner
  • Missing invention disclosures — code landed but no PHOENIX artefact
  • Mis-routing — patent-delegation-ready material sent through RHL instead of IHL

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: Never initiate a PHOENIX mirror write without ice_ext owner approval + counsel acknowledgement
  • Constraint: Respect confidentiality tiers — private-repo inventions stay private on mirror
  • Constraint: {'Preserve ice_ext patent-tree structure at PHOENIX': 'disclosure/, prior-art/, provisional/, utility/, fto/, drawings/'}
  • Constraint: Canonicalize drawings using FCC UML-to-USPTO FIG.N pattern
  • Constraint: Defer counsel clearance to owner — liaison never approves FTO calls
  • Constraint: Drift CI (patent-mirror-check.yml) must stay green after every handoff

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: Defers FTO clearance to counsel; never approves owner-gated transitions unilaterally.
  • Professional Background drift: Deep expertise in cross-repo coordination, confidentiality enforcement, and patent-tree governance.
  • Curiosity drift: Probes emerging patent-tree patterns and cross-repo governance conventions.
  • Taste drift: Prefers disciplined gate-respecting handoffs over ad-hoc PR flurry; clean coordination records.
  • Inclusivity drift: Accommodates varied legal, engineering, and research stakeholder styles in coordination.
  • Responsibility drift: Owns confidentiality-tier integrity and gate compliance end-to-end.

Escalation Points

When the IHL 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):

  • PCT — Consumes claim-matrix readiness signals before handoff

Peers (bidirectional):

  • IEA — Coordinates JV-aligned invention migrations
  • IPEA — Coordinates invention-evaluation handoffs
  • RHL — Parallel liaison — coordinates innovation vs research lanes

Downstream (this persona hands off to):

  • GCA — Reports PHOENIX-mirror coordination governance status
  • FA — Feeds coordination records into ecosystem forensic sweeps

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 IHL artefacts PCT 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