Demo Troubleshooting

When to use it

Use this when a public demo signal is confusing, stale, or incomplete.

Route confusionA public demo, proof, or adjacent route is missing, moved, or hard to connect to the claim.

Summary driftDemo summary wording appears older than the visible proof expectation or route metadata.

Proof mismatchThe page points to proof a public visitor cannot follow through public routes.

Coverage boundaryA reduced, partial, unavailable, or unknown label needs to remain visible.

Private-only materialEvidence may exist outside the public site but has no public summary yet.

Wording concernCopy needs downgrading, removal, validation context, or limitations context before it is repeated.

What it is not

This is guidance for reading the public demo, not a stronger proof surface.

Not a support contract, response-time promise, ticketing channel, or guaranteed answer path.
Not runtime diagnosis, production proof, endpoint performance proof, release approval, operational proof, or complete coverage.
Not an AI or LLM impact-analysis claim, prompt-based classification, embedding search, or vector database analysis.
Not a replacement for validation, tests, owner review, or human review.
Not a way to turn private or raw material into public proof without a public summary route.

Troubleshooting matrix

Each row keeps the public symptom, check, owner, stop condition, and non-claim attached.

Public demo troubleshooting rows. The final two columns are marked as non-claims because they say what the public route cannot prove.
Scenario	Symptom	Likely public-safe cause	What to check	What not to conclude	Next owner/route	Stop condition	Non-claim
Missing route	A linked public demo or proof route is missing, redirects unexpectedly, or is absent from discovery.	Route not implemented yet, moved, intentionally omitted, or not published in the current public build.	Check the demo runbook, demo start-here, sitemap or discovery metadata, and visible deferral labels.	Do not conclude the evidence exists, does not exist, proves the claim, or disproves the claim.	Site owner or demo owner; route to demo runbook, demo start-here, or limitations.	Stop before repeating proof wording until a resolving public route or explicit deferral exists.	Missing route is not proof, runtime diagnosis, release approval, or complete coverage.
Outdated demo summary	Public summary text appears older than surrounding demo routes or proof wording.	Summary copy may be stale, a proof upgrade may be planned, or validation language may have changed.	Check demo result, proof upgrades, validation expectations, visible date metadata, and visible claim-level metadata.	Do not conclude current-head, current-release, current-proof, or live production state.	Demo owner or site owner; route to demo result, proof upgrades, or validation expectations.	Stop before current wording until the public summary and proof expectation match.	Stale summary is not current proof or a clean-demo claim.
Broken proof expectation	A page promises proof that a public visitor cannot follow or validate.	Link, label, route, artifact summary, or explanation may be incomplete or intentionally deferred.	Check the named proof route, validation expectations, limitations, and any visible deferred or unavailable label.	Do not conclude public proof exists or that private or raw material may stand in for public proof.	Demo owner, validation owner, or site owner; route to validation expectations or limitations.	Stop before public proof wording until the proof path is public and resolvable.	Incomplete proof path is not production proof, runtime proof, or release safety.
Reduced coverage label	Demo copy shows reduced, partial, syntax fallback, unavailable, or unknown coverage.	The public demo may be preserving a real evidence boundary rather than hiding a result.	Check the coverage label, evidence tier wording, limitation, validation expectation, and adjacent explanation.	Do not conclude complete coverage, absence of impact, clean repo, release safety, or Tier1 semantic certainty.	Validation owner or limitations route; route to validation expectations and limitations.	Stop before strengthening the claim or removing the reduced label.	Reduced coverage is review input, not complete proof.
Private-only evidence	The demo refers to internal support, private-only evidence, or unavailable details.	Evidence may exist outside the public site but lacks a public summary.	Check for a public summary, limitations note, proof-upgrades plan, or owner handoff.	Do not cite private-only material as public proof or publish private details.	Site owner or reviewer; route to limitations or proof upgrades.	Stop before public proof wording until a public summary exists.	Private-only evidence is not public proof.
Unsupported claim wording	Copy implies stronger proof than the visible public evidence supports.	Claim wording may have drifted ahead of the proof route, validation state, or limitation.	Check the exact wording against the visible proof route, validation expectations, limitations, and public claim level.	Do not repeat support SLA, runtime diagnosis, production proof, release approval, endpoint performance, complete coverage, AI/LLM, or replacement-of-review claims.	Site owner or reviewer; route to limitations, validation expectations, or questions and objections.	Stop, downgrade, or remove wording until evidence and non-claims match.	Unsupported wording is not evidence.
Validation mismatch	Demo text and validation route describe different expectations or status.	Validation copy, demo copy, or discovery metadata may be stale or scoped differently.	Check validation expectations, route metadata, sitemap or discovery metadata, and the demo page's visible validation expectation.	Do not claim validation passed, failed, or covers the demo unless the public validation surface says so.	Validation owner or site owner; route to validation expectations.	Stop before validation-pass wording until the public validation expectation is aligned.	Mismatch is not validation evidence or runtime proof.
Where to ask next	The visitor cannot tell which public page or owner should resolve the question.	The route may need a clearer handoff, owner label, or adjacent-route pointer.	Check owner labels, adjacent route links, non-claims, and whether the question belongs to demo, validation, limitations, or objections.	Do not conclude the question is resolved, approved, or diagnosed because it was handed off.	Demo owner, site owner, validation owner, or reviewer; route to the most specific public adjacent page.	Stop after recording the evidence question, requested public next check, and non-claim.	Asking next transfers the question; it does not prove or approve anything.

Safe wording

Use phrasing that preserves labels, routes, and stop conditions.

Missing routeThe public route is missing or moved; wait for a resolving route or recorded deferral before repeating proof wording.

Stale summaryThe demo summary may be stale, so current-proof wording should wait.

Incomplete proofThe proof expectation is incomplete and needs a public route or summary.

Reduced coverageCoverage is reduced, so the label stays visible.

Private-only evidencePrivate-only evidence needs a public summary before it can support public copy.

Unsupported wordingThis wording should be downgraded, removed, or routed to limitations and validation.

Validation mismatchThe validation expectation does not match yet, so passed-validation wording should wait.

Owner handoffAsk the named owner for the next public check; the handoff is not a conclusion.

Rejected wording

Unsupported patterns may appear only as rejected examples.

The demo route is missing, so the claim is proven.
The summary is probably fine, so current release wording is safe.
Private-only evidence is enough public proof.
Reduced coverage proves no impact.
The proof route is confusing, but the release is approved.
The page diagnoses runtime behavior or endpoint performance.
TraceMap provides AI or LLM impact analysis.
The demo uses prompt-based classification, embedding search, or vector database analysis.
Troubleshooting replaces validation, tests, owner review, or human review.

Adjacent routes

This page routes confusion; neighboring pages keep their own jobs.

Demo runbookIntended demo reading sequence and operator checklist.

Demo start-hereFirst-visitor orientation before troubleshooting begins.

Demo resultPublic result surface for bounded demo rows.

Proof upgradesPlanned and completed public proof improvements without implying planned proof already exists.

Validation expectationsValidation method and check-result orientation.

Limitations and non-claimsCanonical boundary surface for what public static evidence cannot prove.

Questions and objectionsBroader stakeholder concerns beyond route-level demo troubleshooting.

Owner handoff

Hand off the evidence question without adding a service promise.

Demo ownerSymptom: demo summary or proof wording drift. Requested next check: public summary, proof route, and stop condition.

Site ownerSymptom: route, metadata, sitemap, or discovery confusion. Requested next check: public route status and bounded link text.

Validation ownerSymptom: validation expectation mismatch. Requested next check: public validation wording and route alignment.

ReviewerSymptom: unsupported wording. Requested next check: downgrade, remove, or route to limitations before repetition.

Stop conditions and non-claims

Stop when public evidence is missing, private-only, reduced, or mismatched.

Stop before repeating proof wording when the public route is missing, broken, or deferred.
Stop before current wording when the summary and proof expectation do not match.
Stop before strengthening coverage wording when a reduced, partial, unavailable, or unknown label is visible.
Stop before public proof wording when the only support is private-only or raw material.
Stop before passed-validation wording when validation expectations conflict.
These stops do not prove, approve, diagnose, certify, guarantee, or replace human review.

When demo guidance does not line up, keep the claim smaller.