Framework Delta

Path: /framework-delta

Framework Delta is the UI for the cross-framework delta engine: pick the framework you have already done and the framework you now need, and it shows how much of your existing control work carries over — and exactly what is still missing.

What the page shows

• Headline reuse percentage — "Reuse X% of your <source> work for <target>", computed by the engine (full coverage counts 100%, partial ~50%).
• Coverage breakdown — counts of full / partial / none target controls with a segmented bar.
• Per-control table — for every target control: the mapped source controls (with relationship type, and pass/fail status when an assessment refined the result), a coverage badge, the concrete delta text (what still must be authored or implemented), a confidence value, and a crosswalk vs AI source badge.
• Framework pickers — source and target selectors fed by the live /api/v1/frameworks catalog (all 20 frameworks).

Refining with a real assessment

Optionally select one of your completed source-framework assessments. The engine then distinguishes controls that are merely mapped from controls that are actually passing in that assessment — coverage is downgraded where the source control is failing, and the delta text says whether you can reuse evidence directly or must fix the source control first.

Honesty labels

Every row carries its provenance:

• crosswalk — deterministic curated mappings plus your org's custom mappings. Always available; no LLM involved.
• ai — LLM-suggested mappings for controls with no crosswalk row. These are confidence-capped, prefixed "AI-suggested — verify", and must be human-reviewed. Suggested control ids that don't exist in the source framework are discarded — the engine never fabricates a mapping. If the LLM is unavailable, crosswalk results are returned unchanged (ai_augmented: false).

See Cross Compliance for the underlying API (POST /api/v1/orgs/{org_id}/cross-compliance/delta), custom mapping management, and the full request/response format.