Skip to content

feat(demo): prepared sample request that is always viewable #71

Closed

Description

@Fluory

Goal

Every visitor of the showcase can see a complete case – original, extracted values with sources, review and export – even while the model provider is unavailable. Context: showcase review 2026-09-27 rated the live demo 4/10 because a request stayed "In Verarbeitung"; root cause measured in #67: the Gemini API free tier answers about one call in three with 503 UNAVAILABLE (high demand), and on Vercel Hobby a job retry waits for a user action or the daily cron. Epic #19.

Acceptance criteria

  • A seed step creates, per demo company, one synthetic sample request whose extraction comes from a recorded model response (no live call), stored like any other run
  • The sample is clearly labelled in list and detail ("Vorbereitetes Beispiel – aufgezeichnete KI-Antwort") and its run records the model id as recorded
  • The seed is idempotent: it creates a new sample only if no unreviewed sample exists
  • The sample contains at least one uncertain and one missing field so the value of human review is visible
  • A second sample per demo company is already approved and exported through the normal path (ERP mock), so a visitor sees review decision and ERP reference without any write action (review 2026-09-27: "Original, Extraktion, Prüfentscheidung und Exportbeleg")
  • Runbook §6 names the step

Not part of this task

  • Nightly reset, public guest access

Test plan

Criterion Check
sample created from recording integration test against Postgres
idempotent integration test: second run creates nothing
label visible component or E2E check
exported sample integration test: export row with ERP reference, exactly one

Security/Privacy affected?

Synthetic data only; recorded response is committed as a fixture.

Follow-ups from the same review: #74 (source view), #75 (case study), #76 (evidence), #77 (next action).

Activity

  1. added
    featureNew capability
    readyDefinition of Ready met – may be claimed
    on Sep 27, 2026
  2. self-assigned this
    on Sep 27, 2026
  3. Fluory commented on Sep 27, 2026

    @Fluory
    OwnerAuthor

    Claimed by @Fluory on branch claude/feat-demo-sample-71.

  4. Fluory commented on Sep 27, 2026

    @Fluory
    OwnerAuthor

    Live im Showcase (2026-09-27, nach Merge von #83): Migration 0019 per setup:deploy angewendet (CHECK requests_source_check per SQL bestätigt); pnpm seed:samples → pro Demo-Firma werk-ost → REVIEW, pumpe-p204 → EXPORTED (ERP-Referenzen QR-5E8B99B1C1 Musterbau, QR-AE274F318F Beispielwerk; je genau 1 Export-Datensatz; Läufe recorded:gemini-3.5-flash). Browser-Prüfung (Playwright, Sachbearbeitung Musterbau): Liste zeigt beide Beispiele mit „Vorbereitetes Beispiel – aufgezeichnete KI-Antwort“; Detail „Werk Ost“: Hinweis, Zur Prüfung, „1 Wert braucht Aufmerksamkeit“, Liefertermin „KW 48“ unsicher mit markierter Quelle, zusätzliche Anforderungen fehlt; Detail „Pumpe P-204“: Exportiert mit ERP-Referenz. Folge-Issue für Reste abgebrochener Läufe: #84.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

featureNew capabilityreadyDefinition of Ready met – may be claimed

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions