Four gates a pilot must pass.
Each gate holds the readiness items that must be true before the next gate matters. What is lit on the rail below is what a named verifier reported; what is withheld is counted, not hidden.
Nothing here is asserted by hand. A category reads complete only when every item beneath it has a verifier that reported a pass, and an out-of-date snapshot withholds the number rather than showing an old one.
Authority posture
AI analyzes.
Deterministic systems validate.
Humans authorize.
Capital remains governed.
Four gates, in the only order they can be passed.
Each gate is lit only by what a named verifier reported for the readiness items it counts. The order is a dependency, not a preference: each gate names what must already be true before the next one matters.
What is left out of the figure is still counted.
None of these counts is a measurement; each is a fact about how the figure is scoped.
Every exclusion above is counted rather than hidden. A category cannot be dropped from this figure without the drop appearing here.
Published snapshots
No series is shown. A series appears only beside a snapshot that can be relied on, and only once at least two snapshots have been published. A line drawn through points nobody published would be an invention.
What funding, not effort, is holding.
These 3 items carry a direct external cost that SigmaX has not committed. They are listed here so their absence is visible rather than inferred.
- SOC 2 Type II examinationNot scheduledBlocked by: funding
- ISO/IEC 27001 certificationNot scheduledBlocked by: funding
- Provisional-to-non-provisional patent conversionNot scheduledBlocked by: funding
None of these items is counted in the pilot-readiness figure above — neither in the numerator nor in the denominator — and none of them carries a timeline. SigmaX does not publish a date it cannot evidence, and an unfunded item has no date to publish.
How this is produced.
Verifier results are produced by the required CI gates on each run; the published snapshot is written by a scheduled workflow and republished by the operator.
A published payload carries a content hash over its own contents. The API recomputes and compares that hash when a snapshot is read back from its ledger, and a payload that does not match is served as unavailable rather than served unchecked. The age of the snapshot is recomputed on every request, so a stored freshness label cannot outlive the file that carries it.
- Content hash (as published)
- Not available
By construction
- No custody
- SigmaX holds no client assets and operates no account into which client capital could be placed.
- No execution
- No order is transmitted to any venue. Every route disposition available today is paper, or a draft handed to an authorized human.
- No live allocation
- Allocation candidates are prepared, evidenced, and recorded. Acting on one is a human decision taken outside this system.
- No customer-capital routing
- Customer eligibility is unreachable without an approved legal pathway, and that pathway does not exist yet. It is a boundary, not a queue.
These are properties of the system, enforced in continuous integration, not promises about how it will be operated. Changing any of them requires a legal pathway, a closed execution chokepoint, operator approval, and new evidence.