Framework engine

Add a framework.
No deploy required.

A regime is data on the control spine, not code in the product. Bring the catalog the standards body publishes — a CSV export or an OSCAL JSON file — bind its columns to the control model, and register it. When the regulator reissues, you re-import the new revision against the same spine.

Source catalog

CSV · TSV · JSON (OSCAL catalog or flat array)

Paste the catalog, or drop a file anywhere in this field

Waiting for a catalog. Nothing is parsed until there is something to parse.

Column mapping

The mapping ledger opens once a catalog parses. Every binding below is a control the presenter can change — nothing about the source format is assumed.

Preview and register

The normalized catalog appears here once a source is parsed and mapped.

Crosswalk candidates

Checking the tenant registry for candidate edges…