Repository navigation
ForgetBase v0.1.0-beta.3
Pre-releaseForgetBase private beta 3 is deployed to the existing Railway installation at https://askbase.dev/ from commit 5611aa38c9b10ec91f1ad4b4080d272e419c32ce.
Readers and agents now receive an immutable approved version while editing continues in a private draft. Target permissions and revocation apply across API, CLI, SDK, MCP, search and exports. Saved changes queue durable indexing work, and stale edits can receive a clear conflict instead of overwriting newer work. Persistent attachments and malware scanning are enabled.
Validation completed:
- Exact release CI and isolated full-stack proof passed; 414 tests and 58 contract checks passed locally.
- Live browser UAT passed 143 admin checks and 85 reader checks on desktop and mobile. API, SDK and MCP publication, draft isolation, stale-edit and revocation checks passed.
- All four application services identify the same release. The API runs as UID 1000 and the indexing queue is empty.
- Original content, identities, permissions and policies were preserved across 22 checked tables. All 20 assets, 40 versions and 3 users remain; 19 assets are published. Synthetic test content and credentials were removed.
- A stopped-writer pre-deployment recovery set restored successfully. The final recovery set also restored and passed access and indexing checks. Its database contains no attachment references and its application blob archive is empty; the nonempty attachment restore path passed the isolated full-stack proof.
Download the source archive, manifest and checksums to reproduce the release inputs. release-verification.json records CI, deployment IDs, image digests, recovery hashes and practical limits. The evidence archive contains synthetic browser screenshots and verification summaries; production backups and credentials are not included.
This release supports one API replica. Publish the current version before adding or removing attachments. Structured instruction authoring uses the CLI or SDK; the browser editor authors Markdown. Managed-upgrade and local-agent runtime work remain separate candidates. This is a private prerelease, not a public launch.
Release plan · Railway runbook · Governed authoring workflow