One boundary.json, four audiences — what the demos look like

[cognis-digital]

A nice property of fedramplens: a single boundary definition fans out into everything different stakeholders need. The new demos show the same engine through four lenses:

• A PM sees a one-line READY/BLOCKED verdict per system and the exact high/critical blockers to escalate.
• A 3PAO gets a SARIF 2.1.0 log — FedRAMP severity mapped to SARIF level, NIST control preserved — ready to upload to code-scanning.
• A platform engineer gets a Mermaid + Graphviz boundary map with unencrypted crossings called out as SC-8 gaps to fix in the network config.
• An ISSO gets OSCAL SSP + POA&M artifacts with deterministic UUIDs (clean diffs).

flowchart LR
    BJSON["boundary.json"] --> ANALYZE["analyze_boundary()"]
    BJSON --> SSP["generate_ssp()"]
    BJSON --> POAM["generate_poam()"]
    ANALYZE --> SARIF["to_sarif()"]
    ANALYZE --> MAP["boundary map"]

Loading

Try PYTHONUTF8=1 python demos/run_all.py and share which view fits your workflow.