Requirement
One control, rule or criterion as a list of identified statements. Each statement has a modality, obligated parties, typed parameters and prose. Guidance and objectives are statements too, with the modality unspecified, or they sit in a framework facet.
Takes overCatalog controls and their parts; the label, alt-identifier and sort-id props.
RequirementSet
Membership, and nothing else. A Set lists requirements or other Sets with a sequence number. Chapters, families, baselines, maturity levels and classification markers are all Sets, and a requirement may be in many.
Takes overGroups, the resolved-profile baselines, and the 5,301-entry applicability matrix of the ISM.
Tailoring
A selection plus a closed list of eight operations, each addressed by identity: requirement, statement, parameter. Nothing is copied. Resolution is one deterministic pass; there are no merge rules because global identifiers make them unnecessary.
Takes overProfiles and the profile-resolution specification; inline per-class variants as in FedRAMP CR26.
Mapping
One crosswalk edge in nine flat fields: source, target, optional statement scope, relationship, direction, confidence, rationale, provenance, evidence. Relationship codes follow NIST IR 8477, plus supplements for content attached to a foreign catalogue.
Takes overThe control mapping model of OSCAL 1.2; crosswalk spreadsheets.
Risk 2.0.0 candidate
The record ISO/IEC 27001 6.1.2 and 6.1.3, BSI Standard 200-3 and NIST SP 800-30 all require: a scenario, an owner, a state, a rating as a level on a named scale, one of four treatment options, and the clauses that carry the treatment. Scoring methods stay outside the kernel. A Risk justifies a requirement once it is assessed and its option chosen.
Takes overThe risk register as a spreadsheet and the Statement of Applicability as a document. risk-coverage computes the latter.
Component
A product, service, policy, process or a system, which is a component with members. Authorization boundaries are identified objects on the component. An absent boundary asserts nothing.
Takes overComponent definitions and the system description of the SSP.
Implementation
One edge: this component satisfies that requirement, optionally that statement, in this way. Responsibility is provider, customer, shared or inherited. An inherited edge must name the upstream component and the authorization it leans on, so a SaaS on a PaaS on an IaaS is checked link by link.
Takes overThe implemented requirements of the SSP and the control implementations of component definitions, which said the same thing twice.
Assessment
Who checked what, how, when, with which result and which evidence. The method is described through a registered facet.
Takes overAssessment plan and assessment results.
Finding
A gap against a requirement or a statement: state, actions with due dates that know their calendar, and Deviations. A Deviation is one typed record with one state machine (investigating, pending, approved or withdrawn) wherever something is weakened or accepted.
Takes overThe POA&M and four FedRAMP extensions that each encoded the same state machine.
Check 2.0.0 candidate
A typed contract of the facts a collector reports, and a flat conjunction over twelve comparators that decides pass or fail. Collector code sits in a facet. What does not fit this form stays a manual check. Recorded verdicts are recomputed by the validator, and evidence files are named by their SHA-256.
Takes overAudit procedures as prose, such as the 291 automated rules of the CIS Ubuntu 24.04 Benchmark that arrive as text a person must read. The design and a live demo.
Advice pack no type, 2.0.0 candidate
A bundle whose manifest names publisher, pack and release, and whose objects are Components only. A vendor's recommendations are capabilities on its Component: the requirement, the clauses, the text, and suggested parameter values. Importing a pack changes no object a set already holds. A recommendation counts for nothing until an Implementation of the user's own cites it.
Takes overThe one use of component definitions worth keeping: a vendor supplies text for consideration and cannot change controls or assessments. How a pack works.