Local-First Studio Documentation
Welcome to the Local-First Studio documentation portal. This site serves as the central knowledge repository for local-first, durable tools built with requirements-driven architectures.
Here, you will find technical guides, operational procedures, design philosophies, and development roadmaps for our active tools.
Active Projects
Select a project from the sidebar or click a quick link below to explore its documentation:
FileCabinet
A mature Windows archive vault utilizing VB.NET, WPF, SHA-256 and BLAKE3 multi-hash integrity, and local indexing pipelines.
Explore FileCabinet Docs →ChatArchive
A provider-neutral ChatGPT conversation database reader utilizing Tauri 2, React, Rust, and durable SQLite app state.
Explore ChatArchive Docs →Core Documentation Scopes
Our documentation is structured around three main scopes to address different operational needs:
1. Architectural Overviews
Understand the technical decisions behind each project stack (e.g. why WPF/VB.NET, why Tauri/Rust/SQLite) and how they fit their respective requirements.
2. Operational Manuals
Find step-by-step instructions on day-to-day operations, maintenance routines (such as Vault Health audits and rescan adoptions), and command-line interfaces.
3. Roadmaps
Review the developmental phases, testing matrices, and long-term curation features mapped out for each utility.
City Hall: Governance & Standards
Beyond individual tools, the Aptlantis workspace runs on City Hall — a set of 15 governance standards that define how projects are proposed, released, documented, hashed, and preserved. Every standard folder below follows the same shape: a spec, an adoption guide, a validation checklist, a changelog, schema references, worked examples, and templates.
| Standard | Acronym | Scope |
|---|---|---|
| Workspace Governance Standard | WGS | Workspace constitution: roots, manifests, lifecycle visibility, agent orientation. |
| Standards Framework Development Standard | SFDS | How standards themselves are authored, versioned, and adopted. |
| Project Proposal Standard | PPS | Mission, boundaries, success/failure criteria before broad implementation. |
| Desktop Application Release Standard | DRS | Release notes, manifests, artifacts, hashes, and verification for desktop apps. |
| Command Tool Standard | CTS | CLI contracts, output streams, JSON envelopes, exit codes. |
| Service and Infrastructure Standard | SIS | Local-first services, daemons, health checks, resource bounds. |
| Website Development Standard | WDS | Website manifests, deployment records, accessibility, rollback. |
| Dataset Development Standard | DDS | Dataset provenance, licensing, validation, splits, integrity. |
| Agent Task Standard | ATS | Agent task records, handoffs, validation summaries, replayable context. |
| Aptlantis Analysis Standard | AAS | Analysis manifests, evaluation runs, metrics, credibility evidence. |
| APTlantis Release Hashing Standard | ARHS | Minimum release-artifact hashes: SHA-256, BLAKE3, KangarooTwelve. |
| Aptlantis Archive Multi-Hash Standard | AAMHS | Archive preservation integrity records and hash manifests. |
| Application as Data Representation Standard | AADR | Application-as-data representation records and component maps. |
| SVG Embedded Semantic Metadata | SESM | Semantic metadata embedded in SVG assets, safe-profile review. |
| NeonInk | NeonInk | Semantic color, visual intent, theme behavior, and design language. |
For the full governance map and how these standards relate to one another, start with WGS and SFDS.