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 project 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 project is the opposite. Until now, innernet gave every project the same generic instruction. With the capture protocol, the AI gets project-specific guidance.

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 — either 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 is saving things you don't need, or missing things you do. That's a signal to refine the protocol. In any session, say:

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

The AI will read the current protocol, edit it, and call innernet_set_capture_protocol to persist it. Future sessions inherit the new behaviour.

Default protocols by type

The defaults are stored in the default_capture_protocol Postgres function. Five built-ins ship today: product, code, brand, creative, org. A catch-all default applies to any other type.

If you find yourself wanting a new type-default (say, research), open an issue with the protocol text you'd propose — we add them when they prove useful across multiple projects.