Make the evidence position visible before increasing the claim.
IYABOKO Validation separates active services, controlled workflows, prototypes, research-stage systems, pilot evidence and external review so internal success is not presented as certification, physical validation or independent assurance.
Use validation labels proportionately.
A status applies to a defined system, test, artefact or claim—not automatically to an entire company, product family or future capability.
Available within scope
A digital service is available for its declared purpose and operating boundary.
Managed operational use
A workflow operates in a bounded environment but is not automatically independently assured infrastructure.
Demonstration stage
A software or hardware concept exists and still requires stronger evidence before broader claims.
Proposed or experimental
A method, architecture or system remains under investigation.
Controlled real-world test
Scope, owners, metrics, stop conditions and evidence collection are sufficiently defined for a bounded pilot discussion.
Specific independent review
Only the stated evidence, artefact or claim that was reviewed should carry the external-review label.
H0–H6 keeps maturity visible.
The maturity path separates an idea from definition, evidence, simulation, prototype and higher-readiness states.
H0
Idea or initial opportunity.
H1
Problem and boundary defined.
H2
Evidence and assumptions organised.
H3
Simulation or computational representation.
H4
Executable or physical prototype.
H5/H6
Validation, controlled pilot and readiness progression as evidence justifies.
Validation sits across the IYABOKO technology pathway.
C3 generates and organises computational decision evidence; Core OS maintains governed project state; Sentinel challenges readiness; Engineering & Invention produces progressively stronger software, hardware, HIL and physical evidence.
Problem framing, computation, modelling and decision preparation.
Project state, provenance, roles and evidence continuity.
Readiness, findings, remediation and progression gates.
Simulation, multidigital systems, prototypes, HIL and physical validation.
Consequential authority remains with accountable qualified parties.
EAC-1 evidence position remains explicitly bounded.
The statements below preserve the current source position: they describe internal prototype evidence and next gates, not certification.
EAC-1 Alpha software
Executable evidence qualification, deterministic/predictive assessment, uncertainty, concordance and bounded action-authority logic.
Frozen scenarios
Normal, thermal, sensor, stale-data, disagreement and prohibited-command scenarios.
SIM-012A/B
The same simulated physical state with different evidence integrity changes runtime authority.
P4 Pilot Site 001
Read-only real Australian BESS or representative-facility pilot pathway.
Independent validation
Requires external university, engineering or appropriately qualified specialist review.
Certification / autonomous control
Safety, product, regulatory and operational-authority gates remain separate future work.
Publish the evidence state before increasing the claim.
Connect each claim to its evidence, limitations and next justified validation gate.