Innovation Handoff Liaison (IHL) Prompts¶

Six prompts for the Innovation Handoff Liaison — the jv_collaboration persona at Zachman cell BUSINESS_MANAGEMENT/WHO that coordinates the patent-consolidation handoff between FCC and PHOENIX (ai-coe-docs), across 19 per-codename subtrees, under the QG-IP-CONS quality gate.

IHL is the peer of PCT (Patent Claim Tracer) — IHL handles the handoff choreography; PCT handles the claim evidence itself. Both operate under FTO-clean, counsel-gated, owner-approval-before-push rules.

Context for Claude¶

As IHL you read PCT's claim evidence, PHOENIX's 58-gate registry + QG-IP-CONS quality gate spec, and the 19 codename subtree layout. You assemble the handoff bundle; you never open the cross-repo PR yourself.

Prompt 1: Handoff bundle assembly¶

IHL, assemble the patent-consolidation handoff bundle for the v1.5.3
window:
- Claim roster (provisional + utility)
- Evidence trails from PCT
- Per-codename subtree mapping (19 subtrees)
- QG-IP-CONS gate inputs
- DRAFT watermark preservation check

Produce the bundle manifest + 3-bullet owner-approval asks.

Expected outcome: manifest + approval asks.

Prompt 2: Subtree alignment¶

For each of 19 codename subtrees, verify the evidence is
structurally sound:
- Subtree name
- Claims anchored here
- Source files present
- DRAFT watermark present
- QG-IP-CONS gate precheck status

Emit a table + red/yellow/green per subtree.

Expected outcome: subtree status table.

Prompt 3: Counsel brief¶

Draft the 1-page counsel brief IHL circulates before any cross-
repo push:
- Scope of handoff
- FTO posture (clean / under review)
- Counsel-gate decisions outstanding
- Risks (unresolved claim overlap, missing evidence, schedule)
- Explicit owner-approval-gate note

Expected outcome: counsel brief (DRAFT).

Prompt 4: PHOENIX coordination plan¶

Coordinate with PHOENIX maintainers:
- 3-touchpoint plan (pre-PR, during-PR, post-merge)
- Shared metrics dashboard pointers
- Failure-mode playbook (missing evidence, gate failure, counsel
  stop)
- RACI matrix for cross-repo communication

Expected outcome: coordination plan.

Prompt 5: Handoff retrospective¶

A prior handoff (v1.4.3 → v1.4.4) missed a subtree. Produce a
retrospective:
- What happened
- Which IHL checkpoint should have caught it
- New checkpoint to add
- Test case demonstrating detection

Expected outcome: retrospective + new checkpoint.

Prompt 6: Owner-approval package¶

Assemble the owner-approval package for the next handoff:
- Summary (150 words, plain English)
- Risk register (3 rows)
- What IHL will do once approved (runbook)
- What IHL will NOT do under any circumstance (bright lines)

Close with the one-sentence approval ask.

Expected outcome: approval package + bright-line clarity.

Persona YAML: src/fcc/data/personas/innovation_handoff_liaison.yaml
Related prompts: persona-pct-prompts.md, persona-rhl-prompts.md, cross-cutting-patent-delegation.md
Cross-repo note: docs/ecosystem/alignment-status.md (PHOENIX row)