Public training record only. Fictional records. Not connected to a live court system. Human review controls every official filing, packet, and record action.
Live crawl verification kit

Run a publication route crawl before a reviewer call.

This kit gives the site operator a clean command, route set, and review-safe public posture for checking the deployed static public proof site after upload. It verifies reviewer paths without touching private data, runtime APIs, or a live court system.

Critical live routes
24
Runtime dependency
0
Private records
Excluded
Official action
Human review
publication route crawl

STATIC_DEMO_BASE_URL=https://prose-demo.tahai.net node scripts/static-demo-live-crawl.js

Use this command after uploading the static package. The crawler checks clean URLs, required safety language, metadata, and reviewer-path availability while preserving the no private user data boundary.

CheckWhat must clearReviewer-safe boundary
Route responseEvery critical public proof path returns a readable page.No login, court system, or runtime API required.
Review postureFictional records, not connected to a live court system, and human review language remains visible.Automation assists; official actions stay human-controlled.
Share readinessTitle, description, canonical URL, Open Graph, and Twitter metadata remain present.Forwarded links do not look unfinished.
Presentation safetyNo public HTML comments, no.html action targets, and no visible internal wording.Review-safe public posture stays intact.
Operator sequence
  • Upload the package to the static host.
  • Run the live crawl with STATIC_DEMO_BASE_URL pointed at the deployed domain.
  • Open the control room and readiness check the first-click reviewer paths.
  • Print this page when a reviewer or State IT reviewer asks how the public package was checked.

Commercial path

Home, review, seats, pricing, Pro Se, Attorney, Family Communications, and start-seat stay clean and navigable.

Open seats →

Public e-filing path

Upload, review, service-contact doctor, preflight, repair, relation-back, and fallback packet stay review-controlled.

Open e-filing repair →

Judicial PSA path

Clerk operations, judge decision board, State leadership metrics, State IT review, and pilot readiness stay separated by role.

Open Judicial PSA →

Presentation path

Control room, proof tour, Live readiness results, Publication checklist, and reviewer next actions give the presenter fallback routes.

Open control room →
What this proves

The deployed public package can be checked without touching private data.

Human review remains the control point. This route is a public training record with fictional records and is not connected to a live court system.

  1. 1Deploy package

    Static files only

  2. 2Run crawl

    Clean URL proof

  3. 3Open control room

    Reviewer path proof

  4. 4Record result

    Forwardable review posture

No private user dataReview-safe public posture
No live court connectionReview-safe public posture
No legal decision by automationReview-safe public posture
Production requires configured adaptersReview-safe public posture
Review standard
Automation assists. Human review controls official records.

This public walkthrough uses fictional training records. It does not submit filings, change court records, provide legal advice, or connect to a live court system. Production use requires authenticated access, configured adapters, audit logging, and court-approved integration boundaries.