Answers Become Interfaces

Chat interfaces are excellent for discovering intent and poor at carrying serious work to completion. A long answer may contain a plan, commands, decisions, evidence requirements, and checkpoints, yet the user must manually convert the prose into an operating environment.

WorkPage OS turns intent and source material into a typed WorkpagePlan, then renders a safe, static, portable, interactive Workpage. A Workpage may be a build runbook, learning surface, troubleshooting tree, decision page, research dossier, creative production board, or completion audit. It includes copy controls, checkboxes, progress, evidence fields, branching gates, notes, and export. Basic use requires no server, account, or model after generation.

The model does not generate arbitrary final HTML on the main path. It proposes a structured plan. A deterministic renderer produces the interface. Projects, plans, revisions, sources, exports, critic reports, and evidence remain durable artifacts. Completion claims require evidence.

The existing v1.1 specification and nineteen-phase runbook define a build-ready local-first Tauri 2 application with Rust, React/TypeScript, SQLite, fixture generation, Ollama and LM Studio adapters, preview isolation, security gates, packaging, and an independent completion audit.

Current evidence state

IMPLEMENTED

This label describes the strongest public-safe state of the specific paper claims. Open the paper's claim ledger for claim-level distinctions and limitations.

Publication

• Full paper: /papers/p20-workpage-os
• Claim ledger: content/papers/p20-workpage-os/claim-ledger.json
• Source manifest: content/papers/p20-workpage-os/source-manifest.json
• Diagrams: 4
• Approximate body length: 1,520 words

Demonstrations

• d14-workpage-generator

Benchmarks

• b09-workpage-os

Public boundary

The research entry publishes a public-safe architecture and evidence record. It does not grant implementation rights or expose restricted claim-ready material.