Reference
Glossary
Each term is defined twice: once in plain language, once technically. Where the two differ in emphasis, the plain-language version is the one to use with stakeholders.
Showing 15 of 15 terms.
- Advisory output Output
Plain: A recommendation for humans to weigh, not an instruction to execute.
Technical: A bounded recommendation carrying its assumptions, evidence basis, confidence statement, and named unresolved items.
Appears on: How It Works. Related: Release class, Supported inference.
- Authority Governance
Plain: Who is allowed to decide, and how far their permission goes.
Technical: Named decision rights and residual-risk acceptance limits bound to roles rather than individuals.
Appears on: How It Works, Sectors. Related: Scope, Release class.
- Contradiction Analysis
Plain: Two pieces of evidence that cannot both be right.
Technical: A recorded inconsistency between sources or between a source and the working hypothesis, with a resolution status.
Appears on: How It Works, Home. Related: Counterevidence, Supported inference.
- Counterevidence Evidence
Plain: Evidence deliberately sought because it would prove you wrong.
Technical: Material gathered through a directed search for defeaters of the current working conclusion.
Appears on: How It Works. Related: Contradiction.
- Defect-and-repair loop Governance
Plain: Finding a mistake, fixing it, and re-checking anything that depended on it.
Technical: A logged correction cycle that re-runs affected analysis steps and revises downstream classifications.
Appears on: How It Works, Framework Components. Related: Release class.
- Evidence Evidence
Plain: Recorded information used to support or challenge a conclusion.
Technical: A registered item with provenance, collection method, timestamp, and an assessed fitness rating.
Appears on: How It Works, Limits. Related: Source fitness, Counterevidence.
- Fail closed Governance
Plain: When support is weak, the framework withholds rather than guesses.
Technical: A default-deny behaviour where insufficient evidential support results in block or escalate rather than a qualified recommendation.
Appears on: Limits, How It Works. Related: Release class.
- Mission Governance
Plain: The specific decision you are trying to make, written down before analysis starts.
Technical: A bounded problem statement naming the decision, the decision owner, the time horizon, and the success condition.
Appears on: How It Works, Use-Case Builder. Related: Scope, Authority.
- Release class Output
Plain: The category an output falls into: proceed, qualify, constrain, escalate, or block.
Technical: A governed classification determining whether, and under what conditions, an advisory output may be issued.
Appears on: How It Works, Home. Related: Fail closed, Advisory output.
- Scenario Analysis
Plain: A described possible future used for comparison, not a prediction.
Technical: A coherent assumption set with stated dependencies, used to compare option performance across conditions.
Appears on: How It Works, Use-Case Builder. Related: Tradeoff, Supported inference.
- Scope Governance
Plain: What is inside and outside the question being examined.
Technical: Declared inclusion and exclusion boundaries covering entities, time period, jurisdictions, and data domains.
Appears on: How It Works. Related: Mission, Authority.
- Source fitness Evidence
Plain: How suitable a source is for the specific question being asked.
Technical: An assessment of relevance, independence, recency, method quality, and known bias for a given mission.
Appears on: How It Works, Limits. Related: Evidence, Unresolved claim.
- Supported inference Evidence
Plain: A reasonable conclusion drawn from evidence, but not directly shown by it.
Technical: A claim requiring one or more stated interpretive steps beyond the underlying evidence.
Appears on: Limits. Related: Unresolved claim, Evidence.
- Tradeoff Analysis
Plain: What you give up when you choose one option over another.
Technical: An explicit comparison of costs, benefits, and distributional effects across options under each scenario.
Appears on: How It Works. Related: Scenario.
- Unresolved claim Evidence
Plain: Something that has not been established and needs verification.
Technical: A claim lacking sufficient supporting evidence or blocked by an unresolved contradiction; carried forward explicitly.
Appears on: Limits, Use-Case Builder. Related: Supported inference, Fail closed.
Map KRYOS V6 to your context
Start with the builder to generate a structured starting map, or request a guided mapping session with a person.