Operational personal system
Cross-Agent Continuity and Knowledge System
A working system that preserves context across AI tools, devices, and work sessions without making any proprietary agent memory store the source of truth.
Claim boundary: The personal continuity system is in daily use. A managed multi-user Continuity Assistant is a separate product-development effort and is not represented as complete.
The problem
AI tools could help with individual tasks, but the administrative work between those tasks still fell to the person using them: finding old conversations, moving conclusions into durable notes, remembering what had been decided, synchronizing devices, checking email, and reconstructing where a project stopped.
The system was designed to hold that thread without silently taking authority over the work.
What the working system combines
- Searchable conversation archives across multiple coding-agent environments.
- Local semantic retrieval for finding related work when the exact wording is unknown.
- A portable Markdown vault as the durable, human-readable source of truth.
- Mobile capture for recording decisions and ideas where they occur.
- Cross-device and server synchronization.
- Scheduled reporting and bounded maintenance tasks.
- Written recovery procedures and explicit operational boundaries.
Information governance
I defined rules that keep the system useful without allowing automation to flatten important distinctions:
- Current decisions remain distinct from historical conversations.
- Ideas and proposals remain distinct from commitments.
- Source links and provenance remain available for verification.
- Automated tools may organize records but may not silently rewrite their meaning.
- Private records remain private, and credentials are not stored as knowledge.
- The person retains authority over consequential actions and corrections.
Research, integration, and verification
The work began by comparing existing search, memory, retrieval, synchronization, and agent tools before adding custom components. The operating system was assembled from reusable tools where they fit, with custom rules and integration only where a demonstrated gap remained.
I tested retrieval boundaries, synchronization behavior, scheduled delivery, permissions, unattended maintenance, and recovery paths. Failures were preserved and diagnosed rather than folded into a clean success narrative.
What the project demonstrates
- Knowledge-system and information-architecture design
- Semantic search and information retrieval
- Workflow automation and systems integration
- Human-in-the-loop governance
- Failure diagnosis and operational recovery
- Accessibility-oriented product thinking
Public writing
The Administrative Work Between Doing the Work explains the practical problem and the assembled system for a general technical audience.