NEW IN 0.5 — FIRST-PACK GUIDE AND VOLUNTARY PILOT Open the First-pack guide for a path from one confirmed requirement through the browser rollout lab to a selected export. Existing work starts with the guide collapsed; you can reopen it. Navigation preserves unsubmitted form entries. The optional pilot is at https://opsproof-evidence-pilot.vercel.app/pilot.html. Choose a learner or reviewer task. Using the workbench needs no sign-up. Only submitting the separate pilot form sends its chosen fields to private pilot storage. Evidence workspace records and attached files remain on device. Contact is optional and separately consented. Download the private submission receipts to withdraw responses later. Receipts are not saved in browser storage. Local feedback downloads/copies are drafts, not submissions. Public feedback is unverified; synthetic tests and human observations must be counted separately. There is no email automation, participant dashboard or workspace cloud sync. NEW IN 0.4 — REPRODUCIBLE BROWSER ROLLOUT Open Exercises, choose Recover an unhealthy rollout, then run the baseline. Change the readiness path, availability policy and rollback retention; run checks. Choose a confirmed requirement, explain your reasoning and disclose assistance. Save run as evidence. In Review & export, select the new artifact, preview and Download ZIP. Extract it and follow the included README.txt in files/. Run node rollout-replay.cjs with Node.js 20+. The eight generated source files include everything needed to compare recomputed and recorded reports offline. No package installation or cloud account is needed. A reproduced failing result is still a failing result. Source Read links show text immediately. Unsaved lab controls/results reset on page reload; saved artifact files persist in browser storage. Workspace JSON backups do not include these bytes. Save and export before clearing browser data. Simulations do not verify production skill. OpsProof 0.3 — Operational evidence workbench Updated 7 October 2026. HOSTED BROWSER WORKSPACE Open https://opsproof-evidence-pilot.vercel.app/app/ to create a pack without installing the Python service. Text records save in that browser's localStorage; selected source files save in IndexedDB. They are not sent to a workspace API. There are no hosted accounts or cross-device sync. Browser cleanup, private mode and storage failures can lose local copies. Keep source originals and backups. PORTABLE HANDOFF Confirm a requirement, save an artifact, and explain their connection. In Review & export, attach UTF-8 text files to a saved artifact, choose the artifacts to share, then Preview shared pack and Download ZIP. Extract the ZIP and open index.html: it includes readable escaped source text, original selected files, Markdown, and a SHA-256 manifest. Hashes describe integrity, not authorship. The shared ZIP includes your role title and confirmed requirements (including gaps), selected linked artifacts and claim limitations. It excludes private requirement notes, applications, raw job description, exercise drafts, reviewer identities and unselected artifacts. Reviews are not included in this UI flow. Metadata edits require removing and reattaching files for the new artifact version. Check the shared preview and files yourself before sharing. Files are limited to 2 MB each, 10 MB total and 100 stored entries. Only selected text formats are accepted; filename/private-key checks are not a complete secret scanner. Filenames must be simple ASCII names without directory paths. JSON backup and full workspace text are private backup/export alternatives; they do not include attached file bytes. Downloaded ZIPs are not workspace restore files. Preserve original source files alongside your JSON backup. START Extract the bundle fully. Open a terminal in the extracted folder that contains this app's opsproof folder, research-and-plan.html and START-HERE.txt. Run with Python 3.10 or newer (no external packages): python -B opsproof/server.py --port 8765 --data-dir ../opsproof-private-data If python is not recognized, use py -3 instead when the Windows Python launcher is installed, or replace python with the path to a Python 3.10+ executable. Then open http://127.0.0.1:8765/opsproof/ in a modern browser. Stop the server with Ctrl+C. If port 8765 is already in use, stop the earlier preview or choose another port and use that port in the browser URL. The command stores workspace.sqlite3 in a sibling private-data directory, outside the served files. Omit --data-dir to use %LOCALAPPDATA%/OpsProof on Windows. Use a consistent browser and URL: localhost and 127.0.0.1 have separate storage. Opening index.html directly also works as a browser-only fallback. It does not start the SQLite service. Browser storage availability depends on your browser. WORKFLOW 1. Paste a role description. Review keyword suggestions in their original context; optional and negated mentions still need manual interpretation. 2. Record concrete requirements, label their priority and confirm them manually. Unlinked confirmed requirements remain visibly marked as missing evidence. 3. Run a local rollout, access or cost lab, or use existing work you may share. Each lab README explains the simulation, commands and limitations. 4. Write observations, hypotheses, decisions, tests, rollback and assistance. Add artifact records labeled simulation, personal project, internship or employment. These origins are self-reported, not authenticated. 5. Connect each confirmed requirement to an artifact with an explanation and limitations. A recorded link is not a quality or job-match score. 6. Record a review's date, scope, rubric version, verdict and notes. Reviewer identity remains unverified. Editing an artifact marks older reviews stale; a new review is needed to assess the changed record. 7. Track application observations manually. They do not establish hiring impact. 8. Export the portable Markdown pack or back up the workspace as JSON. The pack includes all exercise drafts and clearly labeled legacy review notes. SAVING, BACKUPS AND RECOVERY The app saves to browser localStorage and, when connected, the loopback SQLite service. The save-status text shows which copy was saved. A revision check rejects stale service writes. If browser and service copies differ, the app asks which to keep; it does not merge them silently. Export a backup before choosing when both copies contain work you need. Version 1 backups migrate to schema 2 without inventing requirements or reviews. The old opsproof.workspace.v1 browser key is retained; current saves use v2. JSON restore replaces the current workspace after confirmation. The 2 MB UTF-8 limit includes the formatted backup. Record and text limits are enforced. The ZIP download was verified in the tested desktop browser. Check that a requested Markdown or JSON file was actually saved before clearing any data. If Markdown download fails, use Select preview text and copy the full pack. For a JSON backup, open Back up workspace, choose Select backup text, copy the JSON and save it in a UTF-8 file named opsproof-workspace.json. The same dialog also has Download JSON. Verify the saved file before relying on either method. SCOPE AND DATA The hosted app is a static browser workspace; the optional local service below provides an additional SQLite text-record copy only. The service binds only to 127.0.0.1. It checks Host and write-request Origin, uses revision-based updates, and serves an allowlist of app and documentation files. These controls are not user authentication and do not make it a public server. The default and documented SQLite locations are outside the served directory. SQLite and browser storage are plaintext; keep the data folder private and avoid secrets or confidential employer material. No CV, contact details or LinkedIn profile data are embedded in the workbench. There are no remote scripts, fonts or AI calls. ZIP export uses vendored fflate 0.8.3 under its MIT license. There are no hosted accounts, GitHub sync, verified reviewer identities, live cloud infrastructure, automated artifact validation or established hiring gains. Artifact URLs are format-checked; their content and ownership are not verified. All three labs run synthetic deterministic checks locally. Passing them is not a credential or evidence of operating a real cloud environment. RESEARCH AND VALIDATION The original research covers 40 Reddit threads across 20 communities, selected purposively from English-language sources. It is qualitative and biased, not a representative global survey. Research, source qualifications and the original plan remain in ../research-and-plan.html and ../research-evidence.json. ../pilot-kit.html contains a proposed human study and recruitment drafts. No participants have been recruited and no outreach has been sent. See ../VALIDATION.txt for the latest automated and browser verification record. Employer usefulness, reviewer supply, repeat use and hiring benefit are untested. DEVELOPMENT No external runtime packages. UI: index.html, styles.css, app.js, ui-records.js, ui-forms.js. Domain: workspace-schema.js, proof-records.js, export-pack.js and public facade evidence.js. Catalog: missions.js. Service: server.py and workspace_store.py. Sync client: workspace-sync.js. From this opsproof directory: node --test tests/*.cjs python -B -m unittest discover -s tests -p "test_*.py" Run each lab's test file as described in its README. The learner inputs are intentionally faulty; follow the investigation before comparing references. The working product name has not undergone a trademark availability check. WORKED ROLLOUT REFERENCE Open rollout-showcase/index.html from the extracted bundle root, or use the Worked rollout example link in the app. Compare the project README with an OpsProof pack backed by six executed cases and preserved reports. The example was prepared and executed by Codex with reference assistance. No human pilot results or personal unaided exercise are claimed. It uses separate files and does not replace your workspace. See rollout-showcase/STUDY.txt for review steps.