Public Evidence Index
Show exactly what evidence supports each public technical claim.
Each record applies only to the stated item, version and supported claim. One operational pathway or demonstration does not validate every related method or future product.
Evidence ID · State · Item · Claim · Next Gate
Website shell version changes do not change the version or validation state of an evidence record. Artefact-specific evidence labels remain unchanged until supporting evidence justifies an update.
TraceableIDs and versions
ProportionateClaims match evidence
ReassessableNext gate recorded
IndependentExternal review separated
Operating Model
Current public evidence register.
Update states only when the supporting record exists.
| Evidence ID | State | Item | Supported claim | Next gate |
|---|---|---|---|---|
| INT-CORE-001 | Internal | Core OS v11 lifecycle model | Documented governed object/evidence architecture. | Publish version/change history. |
| INT-S20-001 | Internal | Sentinel 20 | Operational readiness/evidence-gap workflow within declared scope. | Publish method version/worked cases. |
| INT-S36-001 | Internal | Sentinel 36 | Requirements/evidence/findings/remediation workflow within declared scope. | Independent user/partner evaluation. |
| DEM-SPACE-001 | Demonstrated | SpaceCore Live Mission | Public simulation demonstrates mission data/evidence flow. | External technical review. |
| INT-EAC-001 | Internal | SENTINEL EAC-1 Alpha | Executable candidate runtime-assurance architecture. | Independent technical review. |
| INT-EAC-002 | Internal | EAC-1 scenario suite | Controlled scenarios generate traceable assurance records. | External reproduction/broader tests. |
| INT-EAC-012 | Internal | SIM-012A/B | Same simulated physical state + different evidence integrity changes runtime authority. | Independent reproduction and IP review. |
| PILOT-EAC-001 | Seeking partner | EAC-1 P4 Pilot Site 001 | Read-only live-BESS pilot architecture prepared; Australian pilot not yet completed. | Secure partner and execute governed pilot. |
Operating Model
Evidence publication rule.
A credible record identifies the version, inputs, method, outcome, limitations, owner and reviewer state.
Identify the exact system
Record code/model/ruleset/version, evidence date and responsible owner.
Make the test reproducible
State inputs, assumptions, environment, expected result and procedure.
Preserve failures
Record passed, failed and ambiguous outcomes rather than deleting inconvenient results.
State independence honestly
Separate internal, customer, partner and independent qualified review.
Make the next evidence gate visible.
Use Partnerships when the next step requires an independent reviewer or pilot site.