Group A Filing Strategy
File each application with 20 claims (Group A). Keep full specifications unchanged. File continuations from each parent to claim Groups B+ later.
Why This Works
Continuations use the same specification as the parent application. Only the claim set changes per filing. This means zero specification rework and consistent prosecution across the portfolio.
Critical rule: At least one continuation must be filed while the parent is still pending. As long as you maintain this chain, continuation rights stay open indefinitely. Each continuation can itself spawn further continuations.
Fee structure (small entity): USPTO base fee covers 20 total claims and 3 independent claims. Excess fees are $100 per claim over 20 and $320 per independent claim over 3. By filing exactly 20 claims per Group A application, we stay at or near the base fee for every initial filing.
Claims by Application
Horizontal stacked bars show how claims distribute across filing groups for each application. Green segments file immediately; colored segments are reserved for continuations.
Group Assignments
Every claim is assigned to a filing group. Group A files with the parent application. Groups B+ are filed as continuations using the same specification.
| Application | Group | Claims | Ind. | Theme |
|---|---|---|---|---|
| App 1 | A | 20 | 4 | Core split-channel + visual indicators + CRM |
| App 1 | B | 20 | - | Progressive enrollment + enterprise + deferred delivery |
| App 1 | C | 20 | - | On-device AI + P2P + contact enrichment |
| App 1 | D | 18 | - | Remaining dependents |
| App 2 | A | 20 | 5 | Core DID delivery + bounded blast radius + trust registry |
| App 2 | B | 6 | - | Encrypt-then-split + key custody + standalone |
| App 3 | A | 20 | 11 | Push auth + anti-bombing + multi-device + relay |
| App 3 | B | 18 | - | M2M auth + prompt injection + ACI layer |
| App 4 | A | 20 | 6 | Core TEE + vendor isolation + memory defense |
| App 4 | B | 12 | - | AI Consensus Ring |
| App 4 | C | 12 | - | Firmware Ring Trust |
| App 4 | D | 20 | - | Dual-Mode + Double XorIDA + Het. Memory |
| App 4 | E | 12 | - | Xboot Server Code Deployment |
| App 4 | F | 22 | - | Xcompute Core |
| App 4 | G | 12 | - | Xcompute Embodiments |
| App 5 | A | 20 | 14 | Multi-tier consensus + storage + MEV elimination |
| App 5 | B | 19 | - | Agent Authorization + Tokenomics |
| App 5 | C | 16 | - | Conservation Law + Double XorIDA CIP |
| App 5 | D | 22 | - | MEV/Privacy Remaining + Storage Remaining |
| App 6 | A | 20 | 4 | Multi-layer extraction + proxy inference + entity vault |
| App 6 | B | 14 | - | Tier routing + streaming reinjection + normalization |
Items Requiring Action
Four items need attention before or during the filing process. Each is independent and can be addressed in parallel.
US 11,972,000 B2) published February 2023, outside the 1-year grace period. A §1.130 declaration is needed for all 6 applications to swear behind the prior art date. This must be filed with each application or as a preliminary amendment shortly after filing.US 11,972,000 B2 and US 2023/0043589 A1 must appear on PTO/SB/08 for all 6 applications. File with the application or within 3 months of filing to avoid additional fees. List all known prior art including the issued patent and published application.US 11,972,000 B2. Application 6 references Applications 1–5. If Apps 1–2 file before Apps 3–6, submit cross-references to the later apps as a preliminary amendment once their serial numbers are assigned.Filing Timeline
Key milestones from initial filing through continuation chains. The critical constraint: at least one continuation must be filed while the parent is pending.