spec: add visual raw demo artifact views

Author: geraldarthurdavis

engi-demo/CHECKLIST.md

@@ -18,6 +18,7 @@ npm start
 - [ ] Confirm the hero says **Spec V7**
 - [ ] Confirm the primary CTA is **Make ENGI branch**
 - [ ] Confirm no stale V6/query-era language is visible in the main flow
+- [ ] Confirm JSON-heavy surfaces default to **Visual** mode and can be flipped to **Raw**
 
 ---
 

engi-demo/README.md

@@ -54,6 +54,7 @@ All of those surfaces are represented deterministically in local state.
 - Measurement provenance distinguishes static deterministic analysis from inferred evaluator surfaces.
 - Structured telemetry artifacts (`.engi/unit-catalog.json`, `.engi/pipeline-telemetry.json`) explain the live pipeline during demos.
 - Proof bundles now include prompt/evaluator implementation surfaces alongside the existing settlement / policy / identity proofs.
+- Every JSON-heavy demo surface now supports a reusable **Visual | Raw** presentation mode. Visual is the default for readability; Raw preserves the exact pretty-printed artifact JSON for inspection/debugging.
 
 ## Run
 

engi-demo/SCRIPT.md

@@ -80,6 +80,10 @@ Important line:
 
 > The need descriptor is a measured object, not just a text box.
 
+Operator note:
+
+> Keep the demo in **Visual** mode by default so people can follow the story, then flip any artifact to **Raw** when you want to prove the exact JSON contract.
+
 ---
 
 ### 2. Candidate recall and hybrid matching
@@ -172,6 +176,10 @@ Important line:
 
 > The branch artifact set is the inspectable remediation package, not just a hidden internal state blob.
 
+Operator note:
+
+> Every major artifact card now shares the same Visual|Raw toggle, so you can move fluidly between human legibility and exact machine-facing structure.
+
 ---
 
 ### 5. Telemetry and advanced V7 surfaces