Skip to content

Chapter 33: Patent Delegation to PHOENIX

New in v1.4.3. FCC's v1.3.9 release introduced a docs/patent/ tree with 20 provisional and 32 utility claims under the IP Evaluation Analyst persona. As the ecosystem has grown to three authority repos (FCC, RC/NEXUS, and ai-coe-docs/PHOENIX) plus ten public constellations and private JV repos such as ice_ext/POLARIS, the question of where the canonical IP record lives has stopped being obvious. v1.4.3 answers it: ai-coe-docs (PHOENIX) is the single source of truth for the ecosystem's IP. This chapter documents the delegation runbook.

Why delegate

FCC is the canonical authority for the FCC framework and R.I.S.C.E.A.R. It is not the canonical authority for the ecosystem's IP portfolio. Those are related but distinct jobs: framework authority means "this is how R.I.S.C.E.A.R. works," patent authority means "this is the defensible filing strategy for the 52+ claims generated across all our projects."

PHOENIX (ai-coe-docs) v4.0.0 shipped patent-publication infrastructure specifically for this role:

  • make pub-patent — Quarto-based patent-document build.
  • Quality gates QG-RC-001 (claim completeness) and QG-CIA-001 (conflict-of-interest assertion).
  • A patent-counsel-facing Markdown template set.

Delegating to PHOENIX means FCC stops pretending it can single-handedly track IP across a 19-repo ecosystem, and PHOENIX picks up its designed job.

The three authority model

The ecosystem now has three cleanly-separated authorities:

  • FCC — framework, R.I.S.C.E.A.R., Zachman 6×6 cross-cut, personas, workflows. Open source (MIT).
  • NEXUS (Research Center) — industry papers, academic artefacts, ecosystem registry. Covered in Chapter 34.
  • PHOENIX (ai-coe-docs) — patent filings, IP registry, counsel handoff. Private repo; covered in this chapter.

The three authorities coordinate via cross-repo PRs, per-PI handoffs, and shared vocabulary (the Zachman cross-cut and the SAFe vocabulary table both help).

The eight-step delegation runbook

A persona, workflow, or pattern that might be patentable follows an eight-step runbook from invention discovery to counsel handoff.

  1. Invention discovery. An FCC contributor flags a pattern as potentially patentable. The flag is a GitHub issue on the FCC repo with the candidate-ip label.
  2. IP Evaluation Analyst (IEA) triage. The IEA persona, shipped in v1.3.9, reviews the issue and produces a docs/patent/triage/<slug>.md note: prior-art risk, novelty argument sketch, scope note. FCC keeps this triage on the FCC side.
  3. Draft abstract + claims on FCC. If triage passes, the IEA drafts the abstract plus a first cut of claims in docs/patent/drafts/<slug>.md. This is the furthest the artefact goes on the FCC side.
  4. PCT (Patent Claim Tracer) cross-reference. The PCT persona, new in v1.4.3, runs a cross-repo traceability pass against the PHOENIX claims registry, RC publication list, and any JV partner (ice_ext, lyra_ext, ...) to surface overlap, prior disclosure, or conflicting filings.
  5. IHL (Innovation Handoff Liaison) package. The IHL persona, new in v1.4.3, assembles the delegation package: triage note, draft claims, PCT report, a fill-in-the-blank counsel brief. The package is committed to the FCC repo under docs/patent/handoff/<slug>/.
  6. Cross-repo PR to PHOENIX. IHL opens a PR on PHOENIX mirroring docs/patent/handoff/<slug>/ into the PHOENIX tree. The PHOENIX-side quality gates (QG-RC-001, QG-CIA-001) run; if green, the PR merges and the PHOENIX make pub-patent pipeline picks up the new claim set.
  7. QG-IP-CONS gate on the FCC side. The new QG-IP-CONS quality gate confirms the FCC-side handoff package is complete (all four artefacts present, PCT report clean, IHL review signed). This gate is what turns the FCC PR from "draft" to "ready for merge."
  8. Counsel handoff. PHOENIX runs make pub-patent to produce the counsel-facing PDF. From this point the process is outside both FCC and PHOENIX — it's a law firm engagement.

The runbook has hard gates on steps 2, 4, 6, and 7. Skipping any of them is a finding on the next audit.

The cross-repo PR flow

The mechanics of the cross-repo PR are worth a diagram. The IHL persona is the owner; most of the friction is in keeping the FCC-side and PHOENIX-side PRs in lockstep.

sequenceDiagram
    participant Dev as FCC contributor
    participant IEA as IEA persona (FCC)
    participant PCT as PCT persona (FCC)
    participant IHL as IHL persona (FCC)
    participant FCC as FCC repo
    participant PHX as PHOENIX repo
    participant QG as PHOENIX CI

    Dev->>FCC: GitHub issue #N<br/>label=candidate-ip
    FCC->>IEA: triage request
    IEA->>FCC: docs/patent/triage/<slug>.md
    IEA->>FCC: docs/patent/drafts/<slug>.md
    FCC->>PCT: cross-ref pass
    PCT->>FCC: docs/patent/pct-report/<slug>.md
    FCC->>IHL: handoff request
    IHL->>FCC: docs/patent/handoff/<slug>/*
    IHL->>PHX: cross-repo PR
    PHX->>QG: QG-RC-001 + QG-CIA-001
    QG-->>PHX: pass/fail
    PHX-->>IHL: PR merged
    IHL->>FCC: QG-IP-CONS gate
    FCC-->>Dev: PR ready for merge

The three new personas

Three personas ship in v1.4.3 to operate this delegation:

  • PCT — Patent Claim Tracer (category governance). Owns the cross-ecosystem patent-claim traceability matrix. This is the ice_ext pattern scaled: PCT runs the same SHA-based cross-reference sweep across the entire 19-repo ecosystem that ice_ext previously ran internally.
  • IHL — Innovation Handoff Liaison (category jv_collaboration). Owns FCC → PHOENIX handoffs. IHL is the persona you bring to a counsel coordination meeting; it translates between FCC's engineering vocabulary and PHOENIX's IP vocabulary.
  • RHL — Research Handoff Liaison (category jv_collaboration). Mirror of IHL for the RC side, covered in detail in Chapter 34. PCT + IHL + RHL form the cross-authority delegation triad.

All three carry full R.I.S.C.E.A.R. specifications and are in the main persona registry.

The QG-IP-CONS quality gate

The new quality gate QG-IP-CONS (IP Consolidation) checks the following on every PR that touches docs/patent/:

  • Every drafts/<slug>.md has a matching triage/<slug>.md.
  • Every handoff/<slug>/ has a PCT report.
  • Every PCT report is newer than the corresponding draft.
  • The IHL sign-off line is present in every handoff package.

QG-IP-CONS is a hard-stop constitution-tier gate for the IP Evaluation Analyst, PCT, and IHL personas. It is advisory for other personas — contributors without IP training should not be blocked by it.

The ice_ext/POLARIS case study

The authoritative case study for this delegation pattern is the ice_ext/POLARIS migration. POLARIS is a private JV repo hosting the Model Management Service (MMS) described in US patent application US20250272473A1. The anchoring is important:

  • POLARIS ships the implementation.
  • US20250272473A1 is the filed patent and lives with counsel.
  • PHOENIX is where the ecosystem-facing IP record lives, consolidated with other claims.
  • FCC ships the R.I.S.C.E.A.R. pattern (Model Management Service persona spec) that informed the patent.

No confidential POLARIS implementation detail flows through FCC or PHOENIX. The handoff package contains only the IP-relevant abstractions: the persona spec, the cross-reference report, and the counsel brief. Private-repo confidentiality is preserved by construction.

This case study is documented in full at docs/ecosystem/ice-ext-patent-coordination-v143.md.

How auditors see this

From the auditor's perspective (Chapter 30), the new delegation surface adds three evidence streams:

  • The docs/patent/ tree on FCC — triage, drafts, PCT reports.
  • The PHOENIX make pub-patent output (referenced by URL in the FCC audit report; the artefacts themselves live in PHOENIX).
  • The ice_ext coordination doc for the POLARIS case study.

Auditors walking the evidence graph from a patent-related finding now traverse the cross-repo link set. The evidence graph serializer understands cross-repo URIs; see the cross-repo evidence schema for the added node types.

What stays on FCC

It bears restating: the triage, drafts, PCT report, and handoff package stay on FCC. What delegates is the downstream consolidation, counsel-facing PDF, and active filing tracking. An FCC contributor who files a candidate-ip issue still interacts primarily with the FCC repo through IHL sign-off. The delegation is process, not geography.

Key takeaways

  • PHOENIX (ai-coe-docs) is the ecosystem's single source of truth for IP from v1.4.3 onward.
  • An eight-step runbook takes a candidate invention from discovery to counsel handoff, with hard gates at steps 2, 4, 6, and 7.
  • Three new personas — PCT, IHL, RHL — operate the delegation; all carry full R.I.S.C.E.A.R. specs.
  • QG-IP-CONS is the new quality gate enforcing handoff package completeness.
  • The ice_ext/POLARIS migration (anchored to US20250272473A1) is the canonical case study; private-repo confidentiality is preserved by construction.