Components

The capture app

Drops captured material into the vault from outside a session. Writes only to the inbox.

Almost everything else here runs because a person opened a session. This one exists for the moments when they did not.

Something is said in a corridor. A thought arrives while walking. A meeting is recorded and there is no laptop open. The capture app takes that and drops it into the inbox, where it waits.

It writes to two places and reads nothing

That is the whole of its contract with the vault. It appends to the inbox, and it puts audio in the inbox’s audio folder. It does not classify, does not route, does not decide what the material is about, and does not touch a single existing file.

The restraint is what makes it trustworthy. A capture surface that also sorts is a capture surface you hesitate before using, and hesitation is the only thing that can actually break capture. Everything downstream can recover from a badly filed note. Nothing recovers from a thought that was never written down.

What happens next is a person’s decision

The material sits in the inbox until someone opens a session and processes it. That is not a queue waiting to be automated — it is where the judgement enters, and the judgement is the part that cannot be delegated.

This part is not published

It is a companion application on the user’s own machine, in a private repository.

From ecosystem.yaml, contract 41 · core-skills 1.89.4 · read at build 2026-10-08