---
title: "The model: eleven object types | JASCON"
description: "The JASCON kernel in one page. Eleven shallow object types, the order of the modal verbs, typed parameters, facets with a contract, two digests per object, three conformance tiers, and where each OSCAL 1.x construct went."
lang: en
url: https://jascon.net/model.html
---

The model

# Eleven object types and what each one replaces

The kernel holds what three national frameworks were measured to need and nothing else. This page walks through it once. The normative text is the [specification](https://github.com/christoph-puppe/JASCON/blob/main/drafts/jascon-specification-1.0.0.md); the long form with every count is the [handbook](https://github.com/christoph-puppe/JASCON/tree/main/jascon/references).

01 The smallest object

## A complete requirement

This is a whole object, with no props, no facets and no document around it. The handbook uses it as its first example because the entire extension surface of the Australian ISM needs nothing more.

- **`id`** is a URI under the authority's own domain. It is compared as a string and never fetched, so validation works on a sealed network.
- **`version`** is the object's own version, and ** `history`** is its publisher's record of its changes; two digests in the manifest seal each version. The ISM maintains 2,202 revision props by hand for the same purpose.
- **`statements`** is a list because clauses are addressed one at a time: SP 800-53 writes a control as items a., b., c., which an implementation answers and an assessment objective names singly.
- **`modality`** and ** `obligated-parties`** sit on the statement. One requirement can bind the operator with MUST and the customer with SHOULD.
- **`prose`** is a map from language tag to text.

*jascon/examples/req-ism-1234.json — illustrative text*

```json
{
  "id": "https://ns.cyber.gov.au/ism/req/ISM-1234",
  "version": "2026.06.18",
  "label": "ISM-1234",
  "lifecycle": "active",
  "statements": [
    {
      "id": "s1",
      "modality": "must",
      "obligated-parties": [
        "https://ns.cyber.gov.au/ism/party/organisation"
      ],
      "prose": {
        "en": "Privileged access to systems is limited to personnel with a demonstrated business need."
      }
    }
  ]
}
```

02 The types

## Each type exists because a published catalogue demanded it

Nine types are in the released 1.0.0. Risk and Check are the tenth and the eleventh, in the 2.0.0 release candidate. The right column says what the type takes over from OSCAL 1.x or from common practice.

Content: what is required

### 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 over** Catalog 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 over** Groups, 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 over** Profiles 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 over** The control mapping model of OSCAL 1.2; crosswalk spreadsheets.

Organisation: why it is in scope

### 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 over** The risk register as a spreadsheet and the Statement of Applicability as a document. `risk-coverage` computes the latter.

Systems: what is in place and what was found

### 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 over** Component 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 over** The 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 over** Assessment 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 over** The POA&M and four FedRAMP extensions that each encoded the same state machine.

Signature

### Attestation

Binds the semantic digests of the objects, the digest of the content manifest and the digest of the rendered document a person signed, in a DSSE envelope. What the machine checked and what the authorizing official signed cannot drift apart unnoticed.

**Takes over** The signed PDF whose relation to the data nobody can verify.

Machines: how a requirement is decided

### 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 over** Audit 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.](https://jascon.net/checks.html)

Vendors: what a supplier recommends

### 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 over** The one use of component definitions worth keeping: a vendor supplies text for consideration and cannot change controls or assessments. [How a pack works.](https://jascon.net/model.html#advice)

03 Binding force

## The modal verbs have an order, and tailoring is checked against it

Three corpora converge on the same field: `modal_verb` in Grundschutz++ (1,006 instances), `force` in FedRAMP CR26, the style guide of the ISM. In JASCON it is a kernel code with a partial order.

Obligations

`unspecified` → `may` → `should` → `must`

Prohibitions

`unspecified` → `should-not` → `must-not`

Restriction (German DARF NUR)

`may` → `may-only`

A move along an arrow is monotone and free. A move against it is an easing, and a move between the chains is an axis change. A Tailoring published by the authority may make either; a consumer's Tailoring needs a recorded Deviation with an approver for both. Excluding a requirement is plain selection and needs no Deviation, because baselines consist of exclusions.

*an operation with a typed deadline*

```json
{
  "op": "set-parameter",
  "requirement-ref": "https://ns.fedramp.gov/cr26/req/IEC-CSO-IIR",
  "statement-id": "s1",
  "parameter": "iir-deadline",
  "value": { "type": "duration", "num": 6, "unit": "hours" }
}
```

### Parameters are typed

Strings, integers, canonical decimals, booleans, dates, URIs and codes, with choice, list and range as containers. Durations are either elapsed time or a calendar period that names its calendar, because a deadline in business days means nothing without one. A `{param:name}` token in prose must resolve to a declared parameter, and a list is a JSON array, never a string a reader has to know to split.

04 Extension

## Two members on every object carry everything else

More than 70 % of the 22,000 props counted in three national catalogues imitate kernel mechanics: membership, ordering, history, aliases, clause structure. The remainder gets a contract.

### `facets`

7 in the standard library

A facet name resolves to a JSON Schema pinned in the bundle's manifest by exact version and digest. Its descriptor declares what it changes: assessment, tailoring, selection or rendering. A tool validates the payload against the pin. A tool that meets a semantics-bearing facet it does not implement stops and prints the reason.

**Why:** three tools that meet one unknown prop today do three different things, and all three claim conformance.

### `annotations`

excluded from digests

A flat map for tool bookkeeping and rendering hints: a tracker id, a web name, a do-not-link flag. Annotations are outside every compliance computation and outside the semantic digest by definition, so nothing conformant can read meaning from them.

**Why:** tools need a place for their own notes that cannot turn into a second, unvalidated vocabulary.

05 Integrity

## Two digests per object

A publication is a bundle: objects, pinned facet schemas, renderings and one content manifest. The attestation lies beside the manifest, since nothing signed can contain its own signature.

| Verdict | Package digest | Semantic digest | Meaning |
|---|---|---|---|
| Full Match | equal | equal | The exact package that was attested. |
| Semantic Match | differs | equal | The approved content, repackaged. The verifier says so. |
| Does not bind | any | differs, or absent | A failure, not a third state. The content is not what was approved, or the bundle does not hold it. It fails the bundle while the attestation is `active`; a draft, a deprecated or a withdrawn one is reported and fails nothing. |

[Compute both digests in your browser](https://jascon.net/index.html#try)

06 Conformance

## Three tiers, each with receipts

A tier claim is checked against the public conformance corpus. A claim without corpus results is a datasheet.

| Tier | Promises |
|---|---|
| Core | Schema validation of every type, sealed operation, package digests, local reference resolution, and preservation of everything unknown. No semantic computation. |
| Portable | Facet validation against pins with the fail-closed gate, semantic digests, deterministic tailoring resolution, lawful bundle composition, risk coverage, and the recomputation of every recorded check verdict. |
| Authority | Publication duties: governed stable identifiers, alias and lineage records on every reorganisation, both digests per object, a deprecation lifecycle. |

07 Vendor advice

## A vendor recommends. The pass mark stays yours.

A vendor knows how its product is hardened. An advice pack brings that knowledge into the graph next to the requirement it serves. Eleven rules, ADVICE-1 to ADVICE-11, hold the file to being advice.

- **Components only.** A pack that lists a Requirement, a Tailoring, a Check or an Assessment is refused. Every id in it lies under the publisher's own origin, so it cannot replace an object of yours.
- **A recommendation is a capability.** It names the requirement, the clauses, a text and suggested parameter values. `product-version` says which version of the product the advice is for.
- **Adopting is your edge.** Your Implementation cites `<component-id>#<capability-id>`, and the product must be a member of your system. Until then the capability is a claim and nothing computes on it.
- **The vendor's manifest is the import record.** It stays in your set, named by the SHA-256 of its bytes. The same file is not imported twice, another release replaces only what the earlier one brought, and advice edited after import is reported.
- **Claimed, attested or proven.** A tool shows the publisher as proven only when the vendor's attestation binds the manifest and its signature verifies under a key you trust. An attestation nobody checked is shown as such.

designed for 74 vectors and one worked pack, signed with a public test key. No vendor has published a pack, and the clause-level field rests on one fictional example file. [The limits.](https://jascon.net/evidence.html#limits)

[Preview the worked pack in the app](https://jascon.net/app/index.html#load=../jascon/example-packs/dbvendor-server-7-advice/) [Write a pack: the builder for vendors](https://jascon.net/pack-builder/index.html)

*the vendor's Component, shortened — worked example*

```json
{
 "id": "https://dbvendor.example/component/server-7",
 "version": "2026-10",
 "kind": "software",
 "product-version": "7",
 "capabilities": [
  {
   "id": "cap-key-rotation",
   "requirement-ref": "https://ns.bsi.bund.de/gspp/req/KONF.14.1",
   "statement-ids": ["s2"],
   "description": {
    "en": "Rotate the server certificate and key with the rotateCertificates command; no restart is needed. The vendor suggests an interval of 90 days."
   }
  }
 ]
}
```

*your Implementation adopts it — worked example*

```json
{
 "id": "https://cso.example/impl/acme--konf-14-1-s2",
 "component-ref": "https://cso.example/component/acme-saas",
 "requirement-ref": "https://ns.bsi.bund.de/gspp/req/KONF.14.1",
 "statement-refs": ["s2"],
 "satisfied-by": [
  { "capability-ref": "https://dbvendor.example/component/server-7#cap-key-rotation" }
 ],
 "status": "planned"
}
```

08 For OSCAL 1.x users

## Where everything went

OSCAL is the origin of this work and the format JASCON reads and writes. Catalogue bundles export to OSCAL 1.2.2; what OSCAL has no construct for rides in namespaced props and returns on import.

| OSCAL 1.2.2 | In JASCON |
|---|---|
| Catalog: groups, controls, parts | Requirement objects in nested RequirementSets. Statement parts become `statements`. |
| Profile and profile resolution | Tailoring: selection plus operations addressed by identity, resolved by one deterministic algorithm of half a page. |
| Component definition | `Component.capabilities`, published as an [advice pack](https://jascon.net/model.html#advice): a bundle of Components that an import cannot use to change a requirement, a tailoring or an assessment. The pack builder imports an OSCAL component definition and reports what has no place in a pack. |
| System security plan | Component with `authorizations`, plus Implementation edges. The document is a rendering, bound by an Attestation. |
| Assessment plan and results | Assessment with its method in a facet, its result, and Findings. |
| POA&M | `Finding.actions` and the Deviation lifecycle. |
| Control mapping model | The Mapping type. |
| props with `ns` | A registered facet, an annotation, or nothing: most props imitated a kernel mechanism. |
| Metaschema, XML, YAML, Schematron | JSON Schema 2020-12, one serialization, ten rule primitives whose rationale prints on failure. |

The eight OSCAL document models mapped onto the object types, with diagrams: [oscal-1x-models-and-jascon.md](https://github.com/christoph-puppe/JASCON/blob/main/oscal-1x-models-and-jascon.md). Migration levels and playbooks: [handbook, chapter 14](https://github.com/christoph-puppe/JASCON/blob/main/jascon/references/ch14-migration-playbooks.md).

## Read one hour, then open a bundle

Chapter 2 of the handbook builds the kernel from the smallest real object upward. The app shows the same objects on SP 800-53, CSF 2.0, the ISM and Grundschutz++.

[The core in one hour](https://github.com/christoph-puppe/JASCON/blob/main/jascon/references/ch02-the-core-in-one-hour.md) [Get started](https://jascon.net/start.html)
