Skip to content

DRAFT — not legal advice. For counsel review only. All content in docs/patent/ is AI-authored from the public FCC codebase and public prior-art search results. Nothing herein constitutes legal advice. Do not file any document on the basis of this package without attorney sign-off.

v1.4.3 delegation notice (2026-04-22): The FCC ecosystem is consolidating all patent material at ai-coe-docs (PHOENIX) under docs/patent/<codename>/. FCC's own tree will mirror to ai-coe-docs/docs/patent/fcc/ as the authoritative single source of truth. Migration PR is user-approval-gated per /home/bobbie_d/.claude/plans/create-multi-stage-plan-breezy-thompson.md. Until the migration PR merges, this tree remains the authoritative FCC-side draft. After migration, this README becomes a redirect sentinel + drift-check only.

FCC Patent Package

This tree contains the full draft utility-patent package for the Find → Create → Critique (FCC) Agent Team Framework, owned by INFORMATION COLLECTIVE, LLC. It is authored for the v1.3.9 patent-centric milestone and is READY for counsel review. Actual filing is out of scope — that requires patent counsel engagement.

Scope

The package supports a single U.S. utility-patent filing pathway:

  1. Provisional application (12-month priority anchor) — see provisional/.
  2. Non-provisional utility application (expanded, claims-focused) — see utility/.
  3. Freedom-to-operate analysis (per-claim risk register) — see fto/.

International (PCT) routing is a downstream decision for counsel and is noted but not drafted here.

Primary invention statement

The FCC framework's novel contributions, as claimed in this package:

  1. R.I.S.C.E.A.R. 10-element persona specification (Role, Inputs, Style, Constraints, Expected output, Archetype, Responsibilities, Role Skills, Role Collaborators, Role Adoption Checklist) unifying prior persona systems and role-based agent frameworks under a single machine-enforceable schema.
  2. Find → Create → Critique workflow graph with plugin-based extension points across 11 plugin types (personas, engines, templates, scorers, validators, providers, governance, scenarios, workflows, subscribers, vocabulary_providers).
  3. Cross-project vocabulary provider plugin pattern — VocabularyProviderPlugin enabling federated entity resolution against packaged YAML mappings without runtime coupling between projects.
  4. Constitution registry with 3-tier governance (hard-stop / mandatory / preferred) applied per-persona as a pre-inference policy gate.
  5. Discernment Matrix × Design Target Factors evaluation — 6 traits × 7 rating dimensions + 6 factors × 7 dimensions for super-connector persona recognition and persona quality gating.
  6. Hybrid persona audit (strict R.I.S.C.E.A.R. completeness + open-science template presence) as a continuous-integration gate that a machine can enforce at commit time.

Counsel contact

Field Value
Primary counsel TBD — to be engaged
Firm TBD
Engagement date TBD
Matter number TBD
Inventor liaison INFORMATION COLLECTIVE, LLC — rollingthunderfourtytwo@gmail.com

Filing checklist

  • IDF review — Review disclosure/invention-disclosure-form.md. Confirm inventorship, prior public disclosures (including GitHub commits, PyPI releases, and docs-site content), and funding sources.
  • Prior-art landscape reviewed — Review prior-art/landscape.md and prior-art/search-report.md. Cross-check with counsel's preferred patent-search vendor (e.g., Questel Orbit, PatSnap, Clarivate Derwent).
  • Provisional application drafted — Review provisional/specification.md, provisional/abstract.md, and provisional/claims.md. Confirm 35 U.S.C. § 112(a) written-description, enablement, and best-mode compliance.
  • Claims reviewed by counsel — Review utility/claims.md. Confirm Alice/Mayo § 101 eligibility posture per USPTO 2024/2025 AI/ML guidance (technological-improvement articulation).
  • FTO assessed — Review fto/analysis.md and fto/risk-register.md. Confirm no identified blocking prior art at independent-claim level.
  • Drawings finalized — Review drawings/README.md. Confirm the 4+1 UML views + C4 context diagram are suitable as FIG. 1 through FIG. 6. Have draftsperson render in USPTO-compliant black-and-white line art (37 CFR 1.84).
  • Oath/declaration and inventorship entity — Confirm INFORMATION COLLECTIVE, LLC as assignee; confirm small-entity or micro-entity status for fee reduction.
  • File via USPTO EFS-Web (pro se) or via licensed attorney — Recommend licensed attorney given § 101 and AI-invention sensitivities.
  • Post-filing — Docket 12-month provisional-to-nonprovisional conversion deadline. Decide PCT routing before the 12-month mark.

Status matrix

Sub-document Path Purpose Status
README README.md This file DRAFT
Invention Disclosure Form disclosure/invention-disclosure-form.md Structured IDF for counsel DRAFT
Prior-art landscape prior-art/landscape.md 10-15 candidate prior-art documents, per-item distinguishing analysis DRAFT
Prior-art search report prior-art/search-report.md Queries, sources, shortlisting methodology DRAFT
Provisional abstract provisional/abstract.md 150-word USPTO abstract DRAFT
Provisional specification provisional/specification.md Full provisional (8-12k words) DRAFT
Provisional claims provisional/claims.md 10-20 provisional claims DRAFT
Utility specification utility/specification.md Expanded utility (12-18k words) DRAFT
Utility claims utility/claims.md 3-5 independent + 20-30 dependent DRAFT
FTO analysis fto/analysis.md Per-claim FTO DRAFT
FTO risk register fto/risk-register.md Conflicts + mitigations DRAFT
Drawings README drawings/README.md Pointer to 4+1 UML + C4 source figures DRAFT

Disclaimer

This package is not legal advice. All content is READY FOR counsel review; file only after attorney sign-off. Nothing in this tree should be construed as establishing an attorney-client relationship between INFORMATION COLLECTIVE, LLC and any AI system or automated tooling. The inventors are solely responsible for all decisions regarding disclosure, prosecution, and commercialization.

  • STRATEGIC_ARCHITECTURE_REVIEW.md — FCC/PAOM cross-project authority boundary.
  • docs/architecture/uml/ — 4+1 UML views referenced by drawings/README.md.
  • docs/architecture/context-diagram.md — C4 context for FIG. 1.
  • docs/decisions/ — 5 Architecture Decision Records contextualizing the claimed embodiments.
  • src/fcc/ — Reference implementation. Line-level references appear in utility/specification.md.