capture protocol

Each innernet project carries a capture protocol — markdown instructions that innernet returns to your AI when it loads the project. The protocol tells the AI what kinds of context to keep current and what to skip, tuned to this specific project.

why it exists#

A logistics planning project and a screenplay should not get the same advice about what to save. A logistics project wants commitments, stakeholders, and risks tracked precisely; it probably doesn't care about prose voice. A screenplay is the opposite. The capture protocol gives the AI project-specific guidance instead of one generic instruction.

how it works#

On innernet_load_project, the response includes a capture_protocol field. The AI reads it once at session start and lets it shape every subsequent innernet_save_context and innernet_capture call.

Default protocols are baked in by project type (product, code, brand, creative, org). You can override them per project at any time — via the dashboard, or by asking the AI to call innernet_set_capture_protocol.

tuning the protocol#

After a few sessions you'll notice the AI saving things you don't need, or missing things you do. That's the signal to refine. In any session, say:

Update my capture protocol — stop saving design rationale,
start saving every commitment with a date.

The AI reads the current protocol, edits it, and calls innernet_set_capture_protocol to persist it. Future sessions inherit the new behaviour.

defaults by type#

Five built-ins ship today: product, code, brand, creative, org, plus a catch-all for any other type. If you find yourself wanting a new type-default (say, research), open an issue with the protocol text you'd propose.