Terms in CFSE have precise meanings. When a term appears in the spec, it carries the definition below.

Core Terms

TermDefinition
ArtifactA documented unit of CFSE output
World ModelThe conceptual map of a system's building blocks and rules
Logic LayerAbstract security rules independent of implementation
Implementation LayerConcrete code/config that realizes the logic layer

Artifacts

TermDefinition
ConceptA fundamental building block representing a system entity
InteractionA single-step operation between concepts
FlowA multi-step legitimate sequence achieving a goal
ScenarioA testable vulnerability hypothesis
ExplorationA concrete test comparing BASE and ATT behavior
FindingA confirmed vulnerability with evidence
PredicateAn atomic boolean condition
InvariantA rule that MUST always hold true
Entry PointA first-class surface artifact (EP-*) describing how a surface is accessed, what it can expose, and where it is tangible
PRJProjection artifact (PRJ-*) describing what a viewer-context sees across one or more surfaces
GeneratorA reusable pattern for creating scenarios
PatchA documented fix with verification

States and Verdicts

TermDefinition
HOLDSInvariant state: the invariant is satisfied
VIOLATEDInvariant state: the invariant is not satisfied
UNKNOWNInvariant state: could not determine
NOT_APPLICABLEInvariant state: the invariant does not apply in context
VIOLATION_CONFIRMEDExploration verdict: attack hypothesis succeeded (invariant violated)
ENFORCEMENT_CONFIRMEDExploration verdict: attack blocked as expected (invariant enforced)
INCONCLUSIVEExploration verdict: results ambiguous
BLOCKEDExploration verdict: could not execute due to environment/tooling constraints

Methodologies

TermDefinition
CIAConcept Interaction Analysis - systematic interaction discovery
Delta AnalysisComparison method isolating single-variable differences
4VVerify, Validate, Vaccinate, Valuate - patch methodology
BASELegitimate user behavior in exploration
ATTAttack behavior in exploration

Modeling Helpers

TermDefinition
tangible_locationsField listing concrete access locators for a surface (URLs, CLI invocations, etc.), intended for scoping and testing

Document Types

TermDefinition
NormativeSpec content defining requirements (uses SHALL/MUST)
InformativeSpec content providing guidance (non-binding)
DerivativeContent generated from normative definitions