KX-17 · Governance
21–30 Day Pilot Orchestrator
Run a bounded pilot with declared cadence, gates, and stop conditions.
Pilot-Validation Required
Sequences intake, modelling, experiment planning, and red-team review into a four-phase engagement with explicit success and failure signals at each gate.
Institute module developed within the KRYOS v6 framework ecosystem. Established scientific methods retain their conventional attribution.
When to use
As the first engagement with a new programme or problem.
When not to use
When approved materials cannot be made available inside the window.
Required inputs
- Scoped problem statement
- Approved material inventory
- Named review participants
Optional inputs
- Prior review history
- Facility calendar
Assumptions and constraints
- The pilot is non-intrusive and read-only with respect to client systems.
Process steps
- 01Phase 1: evidence intake and ontology build.
- 02Phase 2: simulation framing and artifact library.
- 03Phase 3: experiment planning and contradiction monitoring.
- 04Phase 4: red-team review and decision package.
- 05Close with an explicit continue, pause, or stop recommendation.
Human review gates
- A named client reviewer signs each phase gate before the next begins.
Primary output — Completed pilot package with phase artifacts and a stated recommendation.
- phase[], deliverables[], gate_status, reviewer
- success_signals[], failure_signals[]
- closing_recommendation
Failure signals
- Phase gates passed without a named reviewer.
Quarantine triggers
- Material supplied outside the approved handling class.
Mini prompt
Plan a 21–30 day pilot for [CLAIM] across four phases with deliverables, review cadence, named gate reviewers, success signals, and stop conditions.