Demo proof assets

Visuals can make proof scannable without becoming the proof.

This page shows public-safe, screenshot-style representations of the public demo report outputs: summary rows, static paths, before/after change rows, impact rows, and release-review checklist items.

Public claim level: demo. These visuals are orientation aids over deterministic static evidence. Generated reports, rule IDs, evidence tiers, coverage labels, limitations, facts, and indexes remain the source of truth.

Purpose

The visual layer helps humans orient before they inspect artifacts.

Public-safeThe cards use status labels, rule IDs, evidence tiers, coverage labels, counts, and limitations that are already safe for the public demo.

SecondaryThe cards do not replace generated summaries, Markdown reports, fact streams, SQLite indexes, or the rule catalog.

BoundedThe cards do not claim runtime behavior, production traffic, deployment state, endpoint performance, release safety, or AI impact analysis.

Visual proof board

Each card keeps the rule/status frame and limitation visible.

Report summary

Status available demo evidence

Rule public.demo.summary.v1

Tier Tier2Structural

Coverage: PartialAnalysis. Counts stay visible beside gaps and reasons.

Paths and reverse

endpoint

static path

data surface

12 paths, 25 reverse paths, 37 path gaps, and 23 reverse gaps. Static orientation only, not runtime traces.

Diff and impact

before public fixture surface

after changed public fixture surface

impact NeedsReview under demo coverage

14 diff rows considered, 12 surface impacts, 0 endpoint impacts, 0 edge impacts, 0 gaps.

Release review

50static findings

53checklist items

3gaps

Checklist output supports review orientation. It is not release approval or CI policy enforcement.

Evidence handoff

The cards point back to generated public-demo artifacts.

demo-summary.*Public-safe status ledger with rule IDs, evidence tiers, coverage labels, counts, reasons, and limitations.

reports/dependency/**Combined dependency report families for endpoint-stack and mixed-stack demo outputs.

reports/paths/**Endpoint-to-surface path reports with static coverage and gap framing.

reports/reverse/**Surface-to-endpoint reverse lookup reports with selected roots and visible gaps.

portfolio-manifest.jsonGenerated manifest with relative inputs for the public demo portfolio report.

reports/portfolio/**Portfolio report family for public-demo source, surface, edge, endpoint, and gap counts.

reports/diff/**Before/after report families generated from checked-in public fixtures.

reports/impact/**Static impact rows derived from the public demo diff, not runtime impact proof.

reports/release-review/**Review checklist reports that keep static findings, gaps, and non-claims together.

Artifact safety

What this page can show, and what must stay local.

Safe: public demo row names, statuses, rule IDs, evidence tiers, coverage labels, demo counts, report-family names, and limitation labels.
Safe: visual representations of public-safe report summaries when they remain tied to evidence and limitations.
Local-only: raw source snippets, raw SQL, config values, secrets, local absolute paths, raw repository remotes, and private sample identities.
Local-only: raw fact streams, SQLite indexes, combined SQLite files, generated scan directories, analyzer logs, and copied local report archives.
Not safe: claiming the visual board proves full impact, runtime reachability, production dependency understanding, endpoint performance, or release approval.

Need the same evidence as a sequence?

The demo evidence trail walks one public-safe static question through the packet with the same rule, tier, coverage, and limitation boundaries.

The visual board is a map legend, not the territory.

Use it to help reviewers recognize the shape of a demo evidence packet. Then follow the generated reports, rule IDs, evidence tiers, coverage labels, counts, and limitations before making any public conclusion.

For incident-adjacent readers, use visuals only to orient.

The incident review orientation concept explains how these public-safe demo visuals can help a team recognize static evidence shapes before inspecting generated reports. The visuals do not prove runtime cause, production behavior, endpoint performance, or release safety.

Source material

Follow the visuals back to public-demo evidence.

Role-based first look Incident review orientation Manager packet Demo proof upgrades Proof path index Current demo result Evidence packet guide Capability matrix Limitations Public roadmap Demo script source Demo assertion helper