JDBON

JDBON can be described as the higher-level structured representation used for publication control, validation, and active-state description alongside the JDBIN path.

Why separate this from JDBIN?

Because one format can focus on efficient reads while the other focuses on clear semantic and operational control.

Practical role

According to qa-cheat-sheet-kokous.tex, JDBON is the JSON-based control layer that tells:

• which base object is active
• which delta objects belong to the chain
• which database version the chain points to
• which manifest is active through the pointer

Why two layers

JDBIN optimizes reading. JDBON optimizes publishing, version control, rollback, and delta-chain control.

The benefit of this split is clear:

• the read path stays tight
• the publish path stays controlled
• rollback becomes easier to manage