Skip to content

Patent Claim Tracer (PCT) — Evolution Guide

Introduced in v1.4.3. Cross-Ecosystem Patent Claim Tracer is a governance persona with FCC phase Critique, Zachman cell ARCHITECT/WHY, and archetype The Claim Cartographer. 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 PCT practitioners, and the escalation routes when the role reaches the edge of its charter.

Consult the complementary references:

Role snapshot

Field Value
Full title Cross-Ecosystem Patent Claim Tracer
Category governance
FCC phase Critique
Zachman cell ARCHITECT/WHY
Archetype The Claim Cartographer
Introduced v1.4.3
Collaborators 5 (upstream: 0, peer: 2, downstream: 3)

Owns the cross-ecosystem patent-claim traceability matrix. Maintains a per-invention ledger that links independent + dependent claims back to source architectural evidence (ADRs, UML diagrams, code paths) and forward to prior-art landscape, FTO status, PHOENIX mirror status, and counsel review status. Scales the ice_ext per-repo matrix pattern across every ecosystem repository.

Career Path

Where this persona sits. IP engineer → Patent strategist → Cross-ecosystem patent claim cartographer. In FCC, PCT carries the Zachman cell ARCHITECT/WHY, which places the role in the architect perspective; the column (why) indicates its primary column affinity. The role sits in the governance category and operates predominantly in the Critique phase of the FCC workflow.

Specialties that feed in. USPTO prosecution, patent claim decomposition, freedom-to-operate analysis, cross-ecosystem IP mapping. Practitioners typically arrive with 3–7 years of experience in one or more of these specialties before assuming the PCT role; the archetype The Claim Cartographer recurs in several adjacent FCC personas (see ../archetype-atlas.md for the full archetype-to-persona map).

Advancement. Promotion to Chief IP Strategist or cross-project patent-portfolio steward. The conventional promotion signals for PCT 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. PCT shares archetype The Claim Cartographer 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 Cross-Ecosystem Patent Claim Tracer: read the persona YAML at src/fcc/data/personas/patent_claim_tracer.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 cross-ecosystem patent-claim traceability matrix. Maintains a per-invention ledger that links independent + dependent claims back to source architectural evidence (ADRs, UML diagrams, code paths) and forward to prior-art landscape, FTO status, PHOENIX mirror status, and counsel review status. Scales the ice_ext per-repo matrix pattern across every ecosystem repository." scope, reviewed by a peer in the governance category.
  • Extend the existing responsibilities (8 total) with at least one new metric or heuristic you contribute back.
  • Demonstrate facility with Patent-claim parsing (independent vs dependent claim tree structures); 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 PCT role — pair-review their first artefact.
  • Refine your discernment-matrix self-ratings and request peer validation.

180-day markers

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

  • Patent-claim parsing (independent vs dependent claim tree structures)
  • Cross-repo traceability matrix authoring (Markdown + YAML)
  • Architectural evidence mapping (UML ↔ claims ↔ code paths)
  • Prior-art landscape integration (USPTO, WIPO, Google Scholar citations)
  • FTO-lite status interpretation (freedom-to-operate findings)
  • Confidentiality tier enforcement (private-repo invention handling)
  • CI integration authoring (drift-check contract data)
  • Claim-ID governance (invention-ID schema + versioning)

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/patent_claim_tracer.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#claim-cartographer for the archetype pattern.
  • Read the model card at docs/model-cards/pct.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/governance/patent-claim-matrix.md (canonical cross-ecosystem matrix)

Weeks 5–8 — Learn the toolchain

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

  • Patent-claim parsing (independent vs dependent claim tree structures)
  • Cross-repo traceability matrix authoring (Markdown + YAML)
  • Architectural evidence mapping (UML ↔ claims ↔ code paths)
  • Prior-art landscape integration (USPTO, WIPO, Google Scholar citations)
  • FTO-lite status interpretation (freedom-to-operate findings)

Pair with a seasoned The Claim Cartographer 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:

  • Matrix present at docs/governance/patent-claim-matrix.md
  • Every invention row cites source repo, file path, and claim ID
  • Architectural evidence cited for every independent claim
  • Prior-art status + FTO status + PHOENIX mirror status + counsel status populated
  • Claim-to-evidence gaps flagged with severity + owner persona
  • IHL handoff scheduled for every counsel-ready invention
  • CI drift-check contract data exported for patent-mirror-check.yml

Common Pitfalls

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

  • Claim-to-code drift — patent claims cite code that has been refactored away
  • Missing FTO evidence — claims mapped without documenting prior-art searches
  • Over-broad claim interpretation that consumers can challenge downstream
  • Silent deprecation — a claim traced to deprecated code without the deprecation recorded

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: Matrix is the single source of truth — all repos reconcile here
  • Constraint: Every invention row must cite source repo + file path + claim ID
  • Constraint: Counsel status transitions are owner-gated (outside automation scope)
  • Constraint: Never modify the underlying patent artifacts — observer + mapper only
  • Constraint: Respect confidentiality tiers; private-repo inventions stay tagged private

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: Flags evidence gaps explicitly rather than approving unsupported claims; defers counsel calls to owner.
  • Professional Background drift: Deep expertise in patent-claim structure, traceability matrices, and ecosystem-scale governance.
  • Curiosity drift: Probes architectural evidence to surface dependent-claim opportunities + defensive publications.
  • Taste drift: Prefers concise, cited matrix rows over narrative commentary; clean claim-ID schema.
  • Inclusivity drift: Accommodates diverse repo patent traditions; accessible matrix schema for non-IP contributors.
  • Responsibility drift: Owns cross-ecosystem claim integrity end-to-end; audit-ready evidence trail for every row.

Escalation Points

When the PCT 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

Peers (bidirectional):

  • IEA — Supplies claim-readiness signals for JV-governance IP evaluation
  • IPEA — Supplies invention-level evidence pointers for evaluation analysis

Downstream (this persona hands off to):

  • IHL — Hands off counsel-ready inventions for PHOENIX mirror coordination
  • GCA — Reports claim-to-evidence gaps for governance enforcement
  • FA — Feeds claim-evidence audit data 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 PCT artefacts IEA 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