◐Overview
This is a reader for JASCON bundles — the file format in which compliance frameworks (BSI Grundschutz++, FedRAMP CR26, the ACSC ISM, CIS, CyFun, C5 …) are represented as a graph of eleven shallow, globally identified objects instead of eight nested document models. A bundle is a folder: one content-manifest.json (the sealed table of contents, with two integrity digests per object) plus an objects/ tree of small JSON files.
Open a bundle folder (e.g. converted_examples/US.CSF/csf-core-bundle) with the button on the left — everything runs locally in your browser, nothing is uploaded. Then walk the Stages, browse objects, and verify the cryptographic digests yourself.
◬The five stages of the compliance graph
Every document of the old world — catalog, profile, SSP, assessment plan, POA&M — decomposes into objects that belong to one of five stages. Documents become renderings of this graph. Click a stage to browse its objects in this bundle.
⌕Object browser
⬡How to read a JASCON object
Three layers, strictly separated. Every object is built from the same three layers:
1 · Kernel — the fields every framework was measured to need: identity (id — a global URI, compared as a string, never fetched), version, lifecycle, statements with a typed binding force (modality), obligated parties, typed parameters (with display label and advisory default), membership, aliases, relations.
2 · Facets — registered, schema-pinned extensions (…facet/statement-grammar@1 etc.). Each declares which computations it may change; a tool that cannot handle a semantics-bearing facet must stop, never guess. Per-clause payloads are keyed by-statement.
3 · Annotations — rendering chrome. Digest-excluded, strippable, invisible to compliance.
Two digests seal each object in the manifest: the package digest binds the delivered bytes; the semantic digest binds the canonical meaning (annotations removed). Signatures therefore survive legitimate repackaging — and tampering with meaning has nowhere to hide. Use Verify all digests to check this bundle yourself.
The modality lattice (right) orders binding force. Upward moves are free tightening; downward or cross-branch moves are weakenings that require an audited Deviation record — unless the tailoring authority is the framework owner itself.