Kiyo uses fixed values in separate fields. They are deliberately not interchangeable. A task can be DONE while a check is FAIL, and task DECISION REQUIRED is different from readiness DECISION_REQUIRED.
Source: Evidence Contract (KIYO-VERIFY-001)
| Value |
Meaning |
PASS |
The check actually ran, and observed evidence met its criterion within the inspected scope |
FAIL |
The performed check did not meet its criterion |
NOT_RUN |
Not performed; the reason and whether it is still required are stated |
NOT_APPLICABLE |
The criterion does not apply, with a concrete reason (never used for a missing environment) |
BLOCKED |
An evidenced missing prerequisite, or a denied or unsafe target, prevents the check |
Source: Definition of Done (KIYO-DONE-001)
| Value |
Meaning |
DONE |
The named deliverable and all mandatory completion criteria are satisfied with current evidence |
PARTIALLY COMPLETE |
Useful scoped work delivered; requested work or mandatory evidence remains |
BLOCKED |
A concrete missing prerequisite prevents required progress |
DECISION REQUIRED |
A material business, scope, or authority choice blocks the next dependent action |
Source: readiness checklist
| Value |
Meaning |
READY_FOR_IMPLEMENTATION |
Actionable for the stated scope; not permission to implement |
DECISION_REQUIRED |
A material choice needs an authorized decision |
INSUFFICIENT_EVIDENCE |
Necessary technical or current-state evidence is missing |
Source: Memory specification (KIYO-MEM-006)
| Value |
Meaning |
NONE |
Assessed scope has no necessary durable delta |
UPDATE_REQUIRED |
A necessary correction or addition exists (applied, pending, or blocked) |
CONFLICT |
Competing authority, intent, paths, IDs, or concurrent edits need resolution |
NOT_ASSESSED |
Impact could not be assessed; the reason is stated |
| Field |
Values |
record_type |
observation, proposal, decision |
Observation status |
ACTIVE, ARCHIVED |
Proposal status |
PROPOSED, REJECTED, SUPERSEDED |
Decision status |
APPROVED, SUPERSEDED, REVOKED |
verification_status |
VERIFIED, STALE, UNVERIFIED |
git_revision special values |
UNKNOWN; NOT_APPLICABLE (confirmed non-Git) |
Source: activation contract (KIYO-ACT-001) and the compatibility records
| Label |
Meaning |
VERIFIED |
An actual recorded observation, limited to the stated conditions; can describe a real failed check |
DOCUMENTED_ONLY |
Supported by checked vendor documentation, with no Kiyo test |
NOT_TESTED |
That execution has not occurred on the stated target |
UNKNOWN |
Insufficient or conflicting evidence |
UNSUPPORTED |
An applicable source explicitly establishes the limit; not an executed failure |
NOT_REVALIDATED |
A source not rechecked in the current step |
| Field |
Values |
Source |
| Governance mode |
G1 Observe, G2 Assist, G3 Controlled, G4 Restricted |
governance-levels.md |
| Risk rating |
LOW, MEDIUM, HIGH, CRITICAL |
risk-assessment.md |
| Governance Review outcome |
PROCEED, HOLD, DENY |
ai-usage.md |
| Data class |
Public, Internal, Confidential, Restricted |
data-handling.md |
| Adaptive depth |
Tiny, Normal, High-impact |
adaptive-flow.md |
Source: severity and confidence guide
| Field |
Values |
| Classification |
Confirmed defect, Plausible risk, Improvement suggestion |
| Severity |
CRITICAL, HIGH, MEDIUM, LOW, INFO |
| Confidence |
HIGH, MEDIUM, LOW (always with a stated basis) |
| Architecture conformance |
Match, Deviation, Insufficient evidence |
These appear in the framework’s release records and on this site:
| Value |
Meaning |
DEVELOPMENT_UNRELEASED |
Package artifact status; not a published release |
UNSET |
The product version has not been chosen |
PACKAGE_VALIDATED_WITH_LIMITATIONS |
Release rehearsal passed with a documented blocked check |
NOT_SIGNED / NOT_ATTESTED / NOT_PUBLISHED |
No signature, no provenance attestation, no publication |
NOT_VERIFIED |
A signature or claim that could not be checked; neither safe nor malicious |
OWNER_REQUIRED |
An input only the product owner can supply |