LABSPUBLIC RESEARCH INSTITUTE
← Instrument galleryD14-WORKPAGE-GENERATOR

Workpage Generator

A deterministic browser-local research instrument.

Related paperBenchmark contract
DETERMINISTIC FIXTURE · NOT A PERFORMANCE RESULT

Workpage Generator

MECHANISMTyped WorkpagePlan with deterministic static rendering
AUTHORITYValidated plan schema and page-specific evidence contract
COMMIT RULECompletion requires checked work plus attached evidence.
FAIL-CLOSED RULEArbitrary model HTML, remote scripts, and secrets are rejected.
STATEPLAN_DRAFTda50470e
plan version0
tasks completePLAN_DRAFT
evidence attachedda50470e
  1. PLAN_DRAFT
  2. VALIDATED
  3. INVALID
  4. RENDERED
  5. IN_PROGRESS
  6. EVIDENCE_MISSING
  7. COMPLETE_WITH_EVIDENCE
CONTRACT CONTROLS

Each control executes a declared browser-local transition. Repeated dual-outcome controls alternate deterministically.

FIXTURE ASSERTIONS

NOT YET EXERCISEDArbitrary model HTML is not accepted in the main path.

NOT YET EXERCISEDExport contains no remote scripts or secrets.

NOT YET EXERCISEDCompletion requires the page-specific evidence contract.

NOT YET EXERCISEDLocal progress survives reload and can export as JSON.

RECEIPTED EVENT LOG

No transition yet. Operate a declared control.

This transparent browser-local instrument teaches the authored state contract. Exercising an assertion demonstrates fixture behavior only; it is not evidence of production performance, compression ratio, model uplift, cognition, safety, or universal correctness.

Purpose

Turn intent and sources into a validated WorkpagePlan, deterministic interactive page, local progress, and standalone export.

Mechanism

A fixture provider emits a typed plan. The validator checks card types, evidence requirements, actions, and completion contract. The renderer owns accessible HTML/CSS/runtime.

Deterministic fixture

Six page archetypes: build runbook, learning surface, troubleshooting guide, decision page, research dossier, and creative production board.

The fixture must live in content/demos/d14-workpage-generator/fixture.json, validate before the demo renders, and be resettable without a network call. A future live adapter may be added behind a visibly separate mode.

Required controls

  • Choose archetype
  • Edit intent
  • Generate plan
  • Break schema
  • Repair
  • Preview
  • Check tasks
  • Add evidence
  • Export HTML
  • Reset/export state

Visible states

  • PLAN_DRAFT
  • VALIDATED
  • INVALID
  • RENDERED
  • IN_PROGRESS
  • EVIDENCE_MISSING
  • COMPLETE_WITH_EVIDENCE

Every state must have text, iconography, and a non-color-only distinction. State transitions are logged in an in-memory demo receipt visible in the inspector.

Core assertions

  1. Arbitrary model HTML is not accepted in the main path.
  2. Export contains no remote scripts or secrets.
  3. Completion requires the page-specific evidence contract.
  4. Local progress survives reload and can export as JSON.

Layout

The page contains:

  1. a concise mechanism explanation;
  2. the interactive stage;
  3. a state and evidence inspector;
  4. a reset control;
  5. a “what this proves / what it does not prove” panel;
  6. links to the related paper and benchmark contract.

On narrow screens the inspector becomes a bottom sheet. The stage must remain usable at 360 CSS pixels.

Accessibility

  • All operations are keyboard reachable.
  • Pointer gestures have button or keyboard equivalents.
  • Animated transitions honor prefers-reduced-motion.
  • Focus remains visible and returns predictably after sheets close.
  • Diagrams expose concise text alternatives.
  • Status is announced through a polite live region only when the user initiates the transition.

Instrumentation

Record locally:

demo_id
fixture_version
action
prior_state
result_state
validation_result
timestamp_relative

Do not send telemetry. Provide “Export demo trace” as JSON for debugging and reproducibility.

Automated tests

  • fixture schema validation;
  • deterministic reset;
  • every required control transition;
  • every assertion above;
  • invalid and stale fixture handling;
  • keyboard path;
  • 360 px and 1440 px screenshots;
  • zero critical console errors;
  • no request to a paid API in default mode.

Publication boundary

Fixture generation proves the deterministic page path. Provider-backed quality requires separate adapter runs.

The interface must never convert illustrative values into a benchmark claim. A measured result appears only when linked to a versioned run receipt.