Projects
From useful help to the code behind it.
Household and business applications give the work its practical purpose. Shared memory rules and bounded tools support them while keeping providers replaceable.
Household OS
Keep household knowledge connected to action.
A long-lived household layer for permitted preferences, responsibilities, resources, and history. It should help people and agents prepare for events and follow through without repeatedly asking you to reconstruct the context.
Assisted calendar intake is an early building block. Public code delivers events with stable IDs, receipts, and retries; display integration is experimental. Repeatable setup, routine reconciliation, and preparation work remain in progress.
Household architecture & implementation ↗Sovereign Vault
Keep business decisions connected to their evidence.
A peer application for business knowledge and operations, with separate data and permission boundaries. Its schemas and documentation explore how a business can keep operational state in a database it controls.
Deployment-specific risks remain. Public reference code does not establish that a particular business system is ready for production.
Business architecture & status ↗Protocol foundation01
Sovereign Memory Protocol
The implementation-neutral foundation for provenance, custody, authority, integrity, and portability in AI-accessed information systems. The dedicated repository holds the draft specifications and conformance material.
Public draft under development. Repository access does not establish a stable protocol release, implementation conformance, or a public license grant.
View protocol repository ↗Program guide02
Sovereign AI OS
The overview of the work: why durable context matters, how the components fit together, and where each part is being developed.
A guide to the program and future plans. It does not define protocol requirements.
View repository ↗Reference implementation03
Sovereign Memory Core
A PostgreSQL reference implementation of memory custody and provenance rules. It keeps source and change history alongside memory and provides evidence for checking and moving it.
v0.3-alpha is released with bounded PostgreSQL restore evidence. Production readiness remains deployment-specific; the release does not establish cryptographic identity proof.
Read the release evidence ↗
View repository ↗Data access04
Supabase User MCP
A self-hosted connector being built to give AI tools access to the application data you authorize. You choose the Supabase project; your user and application permissions define what each client can do.
Private alpha. Repeatable installation, durable sessions and broader tool coverage are being built. Storage-backed artifact access is planned through the same connector. Production use remains unsupported.
View repository ↗Read earlier validation results ↗
Household use05
Household OS
A long-lived household knowledge and execution layer. Early work connects assisted calendar intake with event delivery; the wider goal is preparation, coordination, and useful follow-through.
Early implementation with synthetic public examples. Routine operation and governed follow-through are still being built; no finished self-serve product is offered.
View repository ↗Business use06
Sovereign Vault
Public schemas and documentation for keeping business knowledge and operational state in a PostgreSQL database the business controls.
Experimental. Read the repository’s status and open limitations before considering it for business data.
View repository ↗Skills07
Public AI Skills
Reusable instructions for problem solving and working through unfamiliar tasks with AI tools. You can inspect the instructions before using them.
Intended for reuse and collaboration. See the repository for the license terms currently in effect; this website grants no rights.
View repository ↗