PaperForge v3.7.5 is READY FOR CONTROLLED PUBLIC BETA. This page is the public documentation entrypoint; current release and production facts are maintained in PROJECT_STATUS.md and the production runbook.
- Project README — product scope, workflow, local setup, and current boundaries.
- Public evidence — evidence-backed public claims and non-claims.
PaperForge is deployed and running in production at aetherislab.xyz. The sanitized production landing capture is included in the project README. No local or Preview image is labeled as production evidence. See Production Screenshot Audit.
The production New Task capture is retained at assets/screenshots/production/production_04_new_task.jpeg for review, but its login-state redaction affects layout and it is not used as a primary README image. The supplemental UI gallery is in assets/screenshots/current/. These assets were captured from the current main local runtime with a synthetic preview workspace and test DOCX. They are sanitized workflow material, not production evidence or benchmark evidence.
The current gallery intentionally excludes the legacy docs/archive/screenshots/ set and the local Preview rendering capture with character-encoding corruption. No screenshot values should be read as product accuracy or success-rate claims.
- Architecture overview — the verified Agent loop and component boundaries.
- Detailed architecture — API, task, document, execution, verification, and governance layers.
- Agent Trace — traceability fields exposed by the runtime.
- Production deployment runbook — authoritative release and deployment facts.
- Docker deployment — local container startup and configuration.
- Backup and restore — backup and recovery boundaries.
- Release review checklist — current-release review checks.
- Repository governance — source-of-truth, secret, and release workflow rules.
- Risk level system — supported automatic actions and human-review boundaries.
- Public project facts — concise current capability and limitation reference.
- Limitations — supported scope, non-goals, and review expectations.
- Test corpus notes — test-data boundaries and provenance.
Historical archive contains prior showcase, release, deployment, screenshot, and engineering-audit material. Archived files preserve their original conclusions but are not current product specifications or current UI evidence.