AnyBlock v2 shipped in Anytype 0.57 as the data bridge: flat blocks with an indent, Markdown in text, names instead of ids, so a small model guided by a grammar can write it and a stranger can read it. One shape serves export, import and the API.

It is where "agent-native" becomes a concrete design rule, and it is the format the migration bridge speaks.

One piece of the rebuild shipped in Anytype first, in version 0.57, as the bridge for your data. AnyBlock version two, and an API to go with it. Old exports mirrored the internals. Nested lists through block ids. Bold stored as character offsets.

The new format is flat. Blocks in reading order. Nesting is an indent number.

Formatting lives inside the text, as Markdown. Models cannot keep offset bookkeeping. They can write bold stars.

Options and types are names, not ids. Only objects keep ids. Status: In progress. Not an option id someone must fetch first.

Think of a form a stranger can fill in, and read back. The bar was set at the small end. Would a seven-billion-parameter model, guided by a grammar, emit this correctly? If not, the shape is wrong, not the model.

One shape serves export, import, and the API. Learn to read an export, and you can read what a tool just wrote.

Check yourself. Why are blocks flat with an indent instead of nested?