Modular layers

Framework Components

These are described as layers of a framework, not as guaranteed features of any installed system. Each entry states its maturity so framework vocabulary is never read as shipped functionality.

GovernanceCore

Governance and control layer

Role in the framework: Holds scope, authority limits, and release permissions.
What it contributes: Prevents analysis from drifting beyond what the organisation authorised, and records who may accept residual risk.
Caution: Described as a framework layer. Do not read it as a deployed access-control product.

EvidenceCore

Evidence registration layer

Role in the framework: Registers each source with provenance, fitness, and known weaknesses.
What it contributes: Makes source quality a first-class input rather than an implicit judgement.
Caution: Fitness scoring depends on human assessment; it is not an objective measurement.

AnalysisCore

Contradiction and counterevidence layer

Role in the framework: Actively searches for evidence that would defeat the working conclusion.
What it contributes: Surfaces disagreement early instead of letting a narrative harden.
Caution: Absence of found contradiction is not evidence of correctness.

AnalysisCore

Scenario analysis layer

Role in the framework: Models plausible futures and their tradeoffs against stated assumptions.
What it contributes: Turns a single prediction into a comparison with visible assumptions.
Caution: A modelled scenario is not a claim that the scenario is true or likely.

AnalysisOptional

Prioritisation layer

Role in the framework: Ranks options against declared criteria and constraints.
What it contributes: Makes the ranking logic inspectable and contestable.
Caution: Ranking inherits every bias present in the declared criteria.

AnalysisDerived

Simulation and counterfactual layer

Role in the framework: Explores what would change if a key assumption were false.
What it contributes: Identifies which assumptions the conclusion actually depends on.
Caution: Availability varies by context and data quality. Treat as a proposed extension unless documented in your implementation.

OutputCore

Release logic layer

Role in the framework: Classifies output as proceed, qualify, constrain, escalate, or block.
What it contributes: Gives weak support a defined destination instead of a softened recommendation.
Caution: Release classes advise. They do not execute or enforce anything on their own.

GovernanceOptional

Defect, repair, and retest loop

Role in the framework: Records defects found in analysis and re-runs affected steps.
What it contributes: Stops a single corrected error from silently invalidating downstream conclusions.
Caution: Effective only where the original reasoning trail was recorded.

Framework vocabulary is not deployment

The most common misreading of a framework document is to treat its component list as a product specification. A layer describes a responsibility that must be met somewhere: by software, by a process, or by a named person with a checklist.

When you map KRYOS V6 to your organisation, the useful question for each layer is not "do we have this feature" but "who or what currently holds this responsibility, and is that recorded".

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.

Open the Use-Case Builder Request a mapping session