Inochi2D
Native data

Projects and version history

Know what is saved locally, what reaches the cloud and how revisions avoid silent overwrite.

The native project is the source of truth

The Editor does not maintain a simplified SaaS JSON copy of your Puppet. Creator Core combines a lossless INP1 authoring document with the source-built Inochi2D runtime. Unknown compatible fields remain preserved through edit and export.

D1 metadata and R2 model bytes

D1 owns users, projects, access, revision ancestry, hashes and the current head. R2 owns immutable INX objects. A successful save uploads the candidate, verifies access again and atomically advances the head with a quoted revision precondition.

Browser INX bytes
  → R2 immutable object
  → D1 conditional revision insert
  → new project head

Version History

The Dashboard lists immutable revisions. Download validates stored length and SHA-256 before returning native bytes. Restore creates a new head from the selected historical bytes; it never rewinds or overwrites an existing object.

Conflicts fail closed