Tools — How the Continuity Substrate Is Used in Practice
This page documents the tools I actually use to work inside the Continuity Substrate. These tools are secondary: they assist correct behaviour, but they do not define continuity. The substrate functions without them.
Status
Living practice (descriptive, not prescriptive)
The Operating Principle
Add your material to your continuity substrate.
The moment a file is placed into a governed folder, continuity rules apply. From that point onward, work is recorded, lineage accumulates, and changes are tracked rather than overwritten.
Core Tools
1. Governed Folders (The Substrate Itself)
What it is
A deliberate folder structure that marks where continuity applies.
How it is used
- Folders are created first (empty folders are inert).
- Files are added intentionally.
- The first file marks substrate activation.
What this gives me
- A clear boundary between draft work and continuity‑governed work.
- An unambiguous start point for lineage.
2. Block Tiles (Structured Records)
What it is
Small, self‑contained records captured in a stable, repeatable structure.
How it is used
- Key moments, decisions, definitions, or summaries are captured as Block Tiles.
- Tiles are stored as plain files that can be read by humans and machines.
What this gives me
- Atomic continuity units.
- Zero reliance on a specific application or platform.
3. FLIE Engine (Ingestion Discipline)
What it is
A disciplined way of deciding what may enter the substrate and under what identity.
How it is used
- Files are checked for structure, attribution, and intent before ingestion.
- Nothing enters the substrate by accident.
What this gives me
- Governance without bureaucracy.
- Protection against drift and noise.
4. Memory Core (Continuity Archive)
What it is
A long‑lived archive of continuity‑governed files.
How it is used
- The Memory Core grows over time through normal work.
- Older material remains readable and attributable without special tooling.
What this gives me
- Continuity across projects, systems, and years.
- A usable history, not an archive of dead files.
5. Local LLM + RAG (Optional Intelligence Layer)
What it is
A local language model with retrieval over the Memory Core.
How it is used
- Reads from continuity‑governed files.
- Writes outputs back into the substrate as new records.
- Does not hold continuity itself.
What this gives me
- AI assistance without surrendering context or custody.
- Intelligence that improves as continuity deepens.
6. Outlook Email Export to PDF (Email Ingestion Tool)
What it is
A Windows desktop application that exports Outlook emails into continuity‑safe PDF files for ingestion into the substrate.
How it is used
- Connects to Outlook to access selected mail folders (Inbox, Sent, etc.).
- Exports emails to a chosen destination folder inside the continuity substrate.
- Emails are written as PDFs, ordered chronologically, with sanitised filenames and an export log.
What this gives me
- Email history becomes files, not trapped messages.
- Correspondence gains identity, provenance, and long‑term readability.
- Email enters the same continuity rules as documents, records, and tiles.
Implementation note: Built as a Windows desktop tool (.NET 8 WPF, MVVM). Uses Outlook access, PDF generation, progress tracking, and logging. This tool assists ingestion; it does not define the substrate.
7. Working Inside the Substrate (Read, Tag, Comment)
What it is
The day‑to‑day interaction with continuity‑governed files once they are in the substrate.
How it is used
- Files can be read, tagged, and commented on.
- Notes are added for things to do, things done, decisions, and follow‑ups.
- Annotations live alongside the files and accumulate over time.
What this gives me
- Context grows without rewriting history.
- Work state is visible without changing the underlying record.
- Continuity captures intent, progress, and outcome.
8. Scoped AI Access (Entity‑Bound Assistance)
What it is
Granting an AI limited, explicit access to specific folders inside the substrate.
How it is used
- Access is granted per folder (e.g. a correspondence folder for a specific entity).
- The AI reads only what it is permitted to read.
- The AI can summarise, track updates, and surface changes over time.
What this gives me
- Ongoing awareness of communications with a specific person or organisation.
- AI assistance that is context‑rich but scope‑limited.
- No global context leakage; continuity remains governed.
How New Tools Are Added
Tools are added only when lived use reveals a need.
- No speculative tooling
- No roadmap promises
- No platform dependence
A tool exists to reduce friction after a rule has proven durable in practice.
What This Page Is (and Is Not)
This page is:
- A description of real use
- A reference for others working with their own files and data
This page is not:
- A setup guide
- A mandatory workflow
- A product catalogue
Stability Notice
The Continuity Substrate definitions and doctrine are stable.
This page may evolve as practice evolves, but the governing rules do not change.
Continuity is demonstrated by use, not explained by plans.