The 20 Operational Principles of IYABOKO.
A proprietary evidence and readiness methodology used by IYABOKO Sentinel to turn complex projects into operational questions, evidence requirements, critical floors, corrective strategies and proportionate decisions.
The public business page uses “Operational Principles.” Scientific publications may discuss proposed laws separately. The methodology is decision support—not certification, regulatory approval or permission to implement high-risk work.
Understand the Principles here, then apply them in Sentinel.
This page explains the methodology. The dedicated Sentinel Examiner page performs the interactive assessment, creates the indicative decision and allows logged-in users to save reports.
Each Principle connects a question to evidence and action.
The purpose is not to reward confident language. It is to identify what must be demonstrated, corrected, governed or escalated before the intended next stage.
Clarify the question
Translate a broad challenge into an operational question that can be answered and reviewed.
Identify evidence
Specify records, measurements, authority, data and review needed to support the answer.
Find the weakness
Expose missing proof, uncertainty, boundary failures, weak controls and unresolved dependencies.
Define correction
Assign a proportionate evidence task, safeguard, owner, review date or escalation route.
Explore the 20 Operational Principles.
Select a Principle below or review them through the five operating layers.
Foundation
Purpose, starting state, hidden capacity and authorised inputs.
ToutoContinuity
What essential function, value or service must continue?
Continuity objective, affected users, minimum acceptable state and recovery requirement.
Define the minimum continuity objective, owner and recovery evidence.
EwaaBaseline
What is the verified starting state?
Dated baseline, source records, current performance and known limitations.
Create a dated, evidence-linked baseline before scoring improvement.
GaboLatent State
What hidden capacity, dependency or inactive risk exists?
Asset inventory, dormant capability, dependency map and unactivated risks.
Identify hidden dependencies and test whether latent capacity is usable.
MetaInput
What information, pressure, request or disturbance enters the system?
Input register, data origin, format, authority, completeness and sensitivity.
Document input provenance, quality, access authority and rejection rules.
Signal & Operation
Observable evidence, activation conditions, operating mechanism and internal workflow.
PuduSignal
What observable evidence shows the challenge is real?
Measurements, logs, observations, incident records and repeatable indicators.
Define validated signals and separate them from assumptions or opinions.
BidaActivation
What condition justifies responsible action now?
Trigger criteria, urgency evidence, authorised owner and activation record.
Set activation criteria and prevent action without an authorised trigger.
BokoEngine
What mechanism drives the problem or proposed solution?
Causal model, architecture, operating mechanism and dependency evidence.
Document the proposed mechanism and test competing explanations.
MunoInternal Mechanics
Which processes, components and workflows shape performance?
Process map, component roles, interfaces, controls and failure points.
Map internal workflow, interfaces, failure points and control ownership.
Interaction & Flow
Concurrent movement, dependencies, hand-offs and accountability across the system.
BegoMulti-Movement
How do simultaneous activities or changes interact?
Interaction map, timing dependencies, feedback effects and conflict analysis.
Model interacting changes and identify collisions, bottlenecks and feedback.
ImoumikapoFlow
How do information, energy, evidence, resources and responsibility move?
Flow diagram, hand-offs, latency, loss points and accountability trail.
Create an end-to-end flow map with owners, delays and loss controls.
Control, Reform & Measurement
Thresholds, boundaries, corrective change, lawful authority, measurement and cross-domain review.
DakiThreshold
What measurable point requires escalation, intervention or change?
Threshold value, rationale, monitoring source, breach response and review date.
Define measurable thresholds and explicit escalation responses.
BedeBoundary
What safety, legal, ethical, technical or scope limit cannot be crossed?
Boundary register, prohibited actions, authority limits and exception process.
Publish non-negotiable boundaries and enforce pause or stop controls.
GotomaiReform
What should be corrected, redesigned, repaired or improved?
Root-cause evidence, reform options, expected effect and verification plan.
Convert the weakest evidence into a testable corrective action.
AkiyakiyaLawful Pathway
Who has authority and what legitimate pathway must be followed?
Role authority, approvals, professional standards, legal route and audit trail.
Assign authorised reviewers and record approvals before escalation.
GakiiMeasurement
How will evidence, risk, readiness and progress be measured?
Metric definition, scale, weighting, data source, confidence and review method.
Use reproducible scoring rules with confidence and missing-data handling.
DuwaWigiCross-Domain Model
Which connected systems or disciplines change the interpretation?
Cross-domain dependencies, assumptions, interfaces and specialist inputs.
Map cross-domain dependencies and obtain the required specialist review.
Detection, Context & Continuity
Transitions, anomalies, local meaning and alternative pathways that preserve progress.
PatiTransition Detection
What sudden change or state transition requires attention?
Transition indicators, rate-of-change limits, alert logic and response record.
Define transition indicators, detection timing and escalation ownership.
DouPekaAnomaly Detection
What hidden pattern, weak signal or unusual condition may be missed?
Anomaly rule, comparison baseline, false-positive controls and validation data.
Test anomaly logic against known cases and document false-positive risk.
UmikapoDomain Context
What sector, location, population, institution or operating context governs meaning?
Context statement, applicable standards, affected groups and local conditions.
Document the domain context and prevent conclusions outside that context.
ItamutoMultidirectional Continuity
What alternative pathways preserve progress if one route fails?
Fallback options, redundancy, recovery routes, dependencies and decision rules.
Create alternative pathways with clear switch, recovery and review criteria.
A readiness score is limited by the evidence supporting it.
The Examiner records evidence quality and confidence alongside readiness. A confident claim without supporting records should not be treated as validated readiness.
Six Principles create a minimum responsibility floor.
Weakness in these areas can prevent progression even where other evidence and readiness scores are stronger.
Measurable escalation and intervention points.
Safety, legal, ethical, technical and scope limits.
Authority, approvals and legitimate review routes.
Reproducible metrics, confidence and missing-data controls.
Hidden patterns, validation and false-positive controls.
Sector, location, affected groups and applicable standards.
The same Principle can require different evidence in different sectors.
Sentinel Sector Review changes priority, mandatory stop conditions, professional boundaries and specialist-review requirements for each domain.
Space OS
Mission assumptions, telemetry, simulation limits, aerospace safety and qualified engineering review.
Energy OS
Loads, storage, installer boundaries, resilience, electrical safety and evidence of performance.
Environment OS
Local context, affected communities, biodiversity, water, land and environmental evidence.
Health & Biotech OS
Non-clinical scope, ethics, privacy, evidence quality and qualified clinical or laboratory authority.
Quantum Net OS
Threat models, secure architecture, verification, telecom boundaries and cybersecurity review.
Financial Security OS
Identity, auditability, transaction controls, financial boundaries and lawful governance.
The assessment supports a proportionate decision.
The purpose is not to produce a decorative score. It is to decide whether the intended next stage is justified and what safeguards or corrections are required.
Understand the method, apply it in Sentinel and retain the evidence trail.
Use this page for methodology review. Use the dedicated Examiner for interactive assessment and request human review when the decision carries material risk.