Traceable evidence before maturity claims.
This index shows what IYABOKO currently records as internal, demonstrated, externally reviewed and operational within a precisely stated scope. Each record states the supported claim, the public reference and the next evidence gate. A score, visual demonstration, model output, internal document or public webpage does not become independent validation without an attributable review record.
Four labels with different meanings.
The labels are intentionally conservative. Public claims must not exceed the strongest evidence state supported for the specific scope.
Documented by IYABOKO
Methods, frameworks, controls, analyses and records created internally. Useful for preparation; not independent validation.
Publicly viewable or repeatable
A working demonstration, published artefact or repeatable test exists with scope, date and limitations stated.
Attributable review
A named reviewer or institution, review date, reviewed scope and evidence reference are published with permission.
Active declared service
The service is available in its stated scope with ownership, support, status and responsibility boundaries.
Current evidence records.
“Operational” applies only to the declared public service or workflow. It does not imply engineering certification, regulated approval or operational deployment of sector concepts.
| Evidence ID | State | Item | Supported public claim | Public reference | Next evidence gate |
|---|---|---|---|---|---|
| INT-001 | Internal | Core OS evidence and governance framework | Documented internal methodology and public framework description. | Core OS page | Publish version, owner and change history. |
| INT-002 | Internal | Sentinel OS 20-Law readiness methodology | Controlled readiness and evidence-gap method. Internal methodology; not independent certification. | Sentinel OS page | Publish method version and worked examples. |
| INT-003 | Internal | H0–H6 maturity pathway | Public maturity labels separating idea, evidence, simulation, prototype, validation and readiness. | Homepage maturity pathway | Attach evidence requirements to each maturity gate. |
| INT-004 | Internal | Six sector Core Lab frameworks | Sector-specific research, evidence and readiness pathways. | Solutions pages | Publish owner, scope and current maturity for each lab. |
| DEM-001 | Demonstrated | AI Workspace | Public idea-clarification and structured preparation experience. | AI Workspace | Version outputs and publish test cases. |
| DEM-002 | Demonstrated | Demo Lab artefacts | Public concept demonstrations, reports, images or workflow examples with limitations. | Demo Lab | Add evidence IDs, dates and reproducibility notes. |
| DEM-003 | Demonstrated | Pilot Readiness assessment | Interactive planning tool with named inputs, evidence grade and governance gates. | Pilot Readiness | Publish method version and validation sample. |
| DEM-004 | Demonstrated | Enterprise Readiness assessment | Interactive organisation-readiness planning tool with named inputs and evidence checklist. | Enterprise Readiness | Publish weighting rationale and test records. |
| DEM-005 | Demonstrated | Project Client Portal workflow | Public description of authorised project records, scope, milestones, support and access boundaries. | Client Portal | Document access-control and record-release tests. |
| EXT-000 | Externally Reviewed | No public external-review record currently listed | No item should be labelled externally reviewed until a named reviewer, date, scope and review record are published. | Validation boundary | Publish the first attributable review record when permission is granted. |
| OPS-001 | Operational | Public business website and information pathways | Public pages, navigation, Contact, Pricing, Validation, Governance and System Status pathways are published in their stated scope. | Homepage | Maintain dated manual status, version history, accessibility and broken-link review. |
| OPS-002 | Operational | Public support and contact routes | Business-domain contact and support email routes are publicly stated. | Support | Publish support ownership, escalation route and realistic response expectations. |
| OPS-003 | Operational | Account access pathways | Registration, Login, Account and AI Workspace pathways are published in their stated scope. | Account access | Publish account-access conditions, plan boundaries and Support ownership. |
| OPS-004 | Operational | Consultation intake pathway | A public route exists for scoped readiness, research, simulation and project discussions. | Consultation | Publish engagement acceptance, scope-confirmation and record-creation process. |
Publication and correction rule.
Every new record should identify an evidence owner, version or date, supported scope, source location, known limitations, claim wording, correction route and next review gate. External-review records require permission to identify the reviewer and accurately describe the review. Incorrect or outdated records should be corrected, versioned or withdrawn rather than silently overstated.
Send evidence corrections, broken-link reports or claim-boundary concerns to support@iyaboko.com. Do not send passwords, private keys, payment credentials, confidential reviewer records or restricted third-party data. General business enquiries can be sent to contact@iyaboko.com.