Used in our setup
A dated operating result or recorded use in our development environment.
Durable context and authority give replaceable models and tools somewhere useful to work.
Different records, needs, and permissions.
Core and bounded access components develop different parts of this foundation.
Intelligence can improve while the person retains continuity.
A conceptual map of roles. Each component owns its implementation evidence and supported profile.
Everyday coordination
The household application: events, responsibilities, preparation, and follow-through. Executable calendar reconciliation is an early piece.
Useful contribution: Add a fabricated calendar edge case or improve a runbook step.
Business knowledge and work
A peer application for business knowledge and operations, with its own records, identity, policy, and deployment evidence.
Useful contribution: Review the isolated adoption path or propose a generic business example.
Durable evidence and history
The PostgreSQL reference implementation for custody, record history, and the bounded synthetic package/restore proof.
Useful contribution: Reproduce a documented test and report a concrete gap.
Bounded application-data access
An independent application-data connector. Its accepted local read-only profile uses synthetic data; broader hosted and write profiles are separate work.
Useful contribution: Run the local synthetic demo and make an unclear step reproducible.
Shared meaning and authority
Implementation-neutral draft rules for provenance, custody, authority, integrity, and portability. A protocol draft and a deployment have different evidence.
Useful contribution: Identify an ambiguous rule with a small, concrete example.
Working methods that travel
Versioned instructions for useful work with AI. CC BY 4.0 permits personal, organizational, and commercial use, with its attribution terms.
Useful contribution: Test a skill on a fabricated problem and improve its instructions.
The program map
The published program map explains the human purpose, principles, and component routes today. Its broader capability horizons describe the connected future we are building.
Useful contribution: Help a newcomer find a clear first step.
Choose a supported profile and use fabricated data in an isolated environment.
The guide explains the system and its supported starting paths for people and AI assistants. It includes prerequisites, a pinned local demo, expected results, and current gaps.
The MCP demo is an experimental POSIX local, read-only, synthetic profile. Follow each component’s current prerequisites.
A dated operating result or recorded use in our development environment.
A documented supported test or profile, with its fixture and limits.
Implementation or integration work still being qualified.
The intended connected experience and longer-term possibilities.
Code, candidate tests, accepted repository behavior, and a running deployment establish different things. Use the evidence linked to the specific result.