Patent Architecture Map
Visual guide to how the 19 MicroStax patents map onto the control-plane pipeline, runtime components, and user workflows.
This page is the visual companion to the patent family guide. Use it when you want to understand the novelty of the system quickly: which patents sit where in the pipeline, which runtime components they affect, and which user workflows they unlock.
1. Patent Pipeline Map
Click top-right to expand
The order matters:
01,02,03, and05decide what should exist06,10, and11decide how sparse environments behave at runtime12,15,14, and16decide whether environments can relocate safely across sovereignty zones07,04,08, and09decide whether those environments can be replayed, audited, and safely promoted13,17,18, and19decide how the system is verified, visualized, and billed
2. Five Patent Layers
Click top-right to expand
This is the clearest way to understand the portfolio:
- Layer 1 makes sparse environments possible
- Layer 2 makes them deterministic
- Layer 3 makes them mobile and residency-compliant
- Layer 4 makes them replayable and governable
- Layer 5 makes them auditable, visual, and economical
3. Component Map
Click top-right to expand
The portfolio is not concentrated in one subsystem. It spans:
- planning
- runtime identity and routing
- replayable execution state
- validation and promotion evidence
4. Artifact Map
| Patent | Main artifact or mechanism |
|---|---|
01 | difference graph |
02 | ancestry chain and resolution graph |
03 | provisional provisioning plan |
04 | snapshot graph and replay package |
05 | optimization record |
06 | provider mapping and routing artifacts |
07 | conflict graph and conflict report |
08 | executable environment graph and execution state |
09 | mirror session and diff report |
10 | routing context identifier and propagation record |
11 | canonical identity and resolved identity record |
12 | sovereignty decision artifact |
13 | audit envelope and integrity manifest |
14 | relocation token and custody record |
15 | resource demand vector and quota reservation |
16 | handover plan and healing artifact |
17 | trust metric and render-state artifact |
18 | counterfactual closure and cost attribution |
19 | usage record and graph-epoch reconciliation |
This artifact trail is where much of the novelty lives. The system keeps turning graph state into reusable machine-readable control artifacts rather than discarding decisions after provisioning.
5. Product Workflow Map
| User workflow | Patent support |
|---|---|
baseline create | 01, 02, 08 |
overlay create | 01, 02, 05, 06, 11, 12 |
| route requests into overlay | 06, 10, 11 |
env relocate across zones | 12, 14, 15, 16 |
env snapshot create | 04, 08 |
env replay | 04, 08 |
env diagnose and trust inspection | 17, 13, 08 |
| governance-safe promotion | 07, 09, 08, 12 |
| behavioral diff review | 09, 11, 10 |
| cost and ROI analysis | 18, 19, 05 |
| long-horizon audit forensic | 13, 04, 08 |
This is why the platform feels integrated. The same patent family supports CLI workflows, dashboard visibility, and operator review paths.
6. Novelty Summary
The platform is novel not because any one feature is individually impossible to imagine. The novelty is in the control-plane composition:
- sparse realization is graph-derived, not manually selected
- inheritance is lineage-aware, not a loose proxy convention
- routing uses explicit provider and identity artifacts
- snapshots preserve replay meaning, not only data state
- runtime execution persists state back into the graph lifecycle
- validation and promotion consume graph-aware evidence rather than ad hoc checks
That is what makes MicroStax feel like a next-generation environment system instead of a simpler wrapper around Kubernetes objects.