1. Home
Open TraceMap home. Say that public claims should stay attached to deterministic static evidence and visible limits.
Manager demo script
Show the site, follow the proof route, and stop before the claim grows.
This bounded demo script helps a presenter show TraceMap to a friend, teammate, or manager with a short route order, answer shapes, and stop conditions tied to public pages.
Public claim level: concept. No public conclusion without evidence. This is a bounded demo script, not a product capability proof, runtime diagnostic, production incident workflow, release approval checklist, or completeness claim.
Opening context
Say why the demo exists before showing proof.
SayTraceMap organizes deterministic static evidence so a review conversation can move from vague concern to specific evidence questions.
ShowOpen the home page and point to the static evidence model, then open capabilities for what the site can inspect and where boundaries begin.
BoundThe goal is faster orientation, fewer vague review conversations, evidence-backed handoff, and clearer limitations. It is not a runtime, production, release, or ownership decision.
2-minute tour
Use five stops for a low-context manager or teammate.
2. Capabilities
Open capabilities. Compare what the site can inspect with what it deliberately leaves to owners, tests, and telemetry.
3. Demo result
Open demo result. Show public-safe result shape, status rows, and limitations where present.
4. Proof paths
Open proof paths. Follow one route from claim to evidence fields such as rule family, evidence tier, coverage label, and limitation where present.
5. Limitations
Open limitations. Close by naming what TraceMap does not answer from static evidence alone.
5-minute proof walkthrough
Follow one public claim through evidence surfaces.
/Start at home and frame the claim as static evidence orientation, not a final decision./capabilities/Use capabilities to inspect the deterministic capability and boundary language./proof-paths/Use proof paths to follow the claim toward rule ID or rule family, evidence tier, coverage label, and limitation where present./proof-source-catalog/Use the proof-source catalog to map public proof points back to source families without exposing raw artifacts./demo/result/Use the demo result to inspect demo status shape and public-safe summary fields where present./demo/runbook/Use the demo runbook to show the operator checklist and sharing boundary./questions/Use questions to route reader questions to evidence surfaces instead of improvising answers./limitations/Use limitations when the claim needs a visible stop./validation/Use validation to show what public-site checks cover and what they do not settle./static-vs-runtime/End at static versus runtime so static evidence stays separate from telemetry, logs, traces, and owner review.Manager questions and safe answer shapes
Answer by routing to proof or by stopping.
Value: what does this help with?
Safe answer shape: show how the site helps a team inspect static evidence, ask sharper questions, and hand off a bounded summary. Open manager brief, then proof paths.
Trust: why should I believe the claim?
Safe answer shape: follow the route, compare the claim to rule ID or family, evidence tier, coverage label, and limitation where visible. Open proof-source catalog.
Completeness: did it find everything?
Safe answer shape: do not answer as complete. Inspect coverage labels and gaps, then open limitations.
Release decision: can we ship?
Safe answer shape: stop. TraceMap can route static evidence questions, but release decisions need the appropriate owners, tests, telemetry, and release process. Open validation.
Production behavior: what happened at runtime?
Safe answer shape: stop and escalate to runtime owners. Use static versus runtime to separate static references from logs, traces, metrics, and dashboards.
Incident use: can this explain an event?
Safe answer shape: ask what static code question needs orientation, then route to public limitations. Do not settle cause, ownership, priority, or operational decisions from this site alone.
Team handoff: what do I send afterward?
Safe answer shape: hand off public links, the claim boundary, and the next evidence question. Open questions for routing.
What to do next?
Safe answer shape: verify the route, inspect the limitation, and ask the owner for the missing evidence rather than upgrading the claim.
Engineer questions and proof routes
Use public proof routes without exposing local material.
Where are the rule IDs and evidence tiers?
Proof route: open proof paths, then demo result. Look for rule ID or rule family, evidence tier, coverage label, proof path, and limitation where visibly present.
How does source mapping stay public-safe?
Proof route: open proof-source catalog. Inspect source families and public claim levels without expecting complete source, private repository facts, or hidden validation details.
What does the demo result status mean?
Proof route: open demo result, then demo runbook. Compare status, gaps, coverage labels, and sharing boundaries where present.
Where do validation and static-versus-runtime boundaries live?
Proof route: open validation, limitations, and static versus runtime. Use those pages when a question leaves static evidence.
What stays out of public copy?
Do not expose raw facts, SQLite content, analyzer logs, raw source snippets, raw SQL, config values, secrets, local paths, remotes, generated scan directories, private names, or hidden validation details.
Stop conditions
Stop showing or stop repeating the claim when proof is missing.
- Stop when the route is unavailable or the public page does not show the field you want to reference.
- Stop when a claim lacks a visible rule ID or rule family, evidence tier, coverage label, proof path, or limitation.
- Stop when the question asks for runtime behavior, production traffic, endpoint performance, outage cause, release safety, operational safety, complete coverage, or complete dependency understanding.
- Stop when the answer would require raw artifacts, private material, local paths, repository remotes, source snippets, SQL, config, secrets, or generated scan directories.
- Stop when the room asks for an approved, safe, unsafe, affected-at-runtime, blocked, validated for release, production proven, or root cause conclusion from TraceMap alone.
Follow-up handoff
Send public links and the next question, not raw output.
Link bundleSend capabilities, proof paths, proof-source catalog, demo result, questions, and limitations.
Summary shapeState the public claim level, the page shown, the proof route followed, the visible limitation, and the owner or evidence needed next.
ReminderThis script is concept-level. Production, release, incident, and runtime questions need the appropriate owner, telemetry, tests, logs, traces, or release process.
Non-claims
Do not let the demo become a stronger public claim.
- Do not claim production incident diagnosis, runtime proof, production traffic, endpoint performance insight, outage cause, release approval, operational safety, complete coverage, or complete dependency understanding.
- Do not claim AI analysis, LLM impact analysis, embeddings, vector database analysis, or prompt classification.
- Do not say TraceMap replaces managers, engineers, service owners, reviewers, architects, tests, telemetry, logs, traces, incident process, release process, or human judgment.
- Do not publish raw facts, raw SQLite content, analyzer logs, raw source snippets, raw SQL, config values, secrets, local paths, raw remotes, generated scan directories, private sample names, or hidden validation details.