Skip to main content
Asakiri uses a content-first domain model with a context-first authoring workflow. Reusable knowledge lives in content records, media lives as independent assets, and lessons and exercises compose references to those records and assets. This is database-like behavior over local project data. It does not mean the course is stored as a single database file. A course is a directory of small JSON files, specified by the course format.

​
The three domains

Content

Reusable semantic records organized into collections. Lessons and exercises reference them.

Media

Local binary assets (audio, image, video) with technical metadata.

Composition

Lessons and exercises bind to records, fields, items, or assets.

​
How a course fits together

  • Structure (Course structure) is the outline learners move through: units, lessons, and parts.
  • Content (Content records) is the reusable knowledge: collections of records with typed fields.
  • Media (Media) owns the binary files.
  • Bindings (Bindings and fragments) connect the outline to the content and media it displays.
  • Exercises (Exercises) separate what a learner sees from how a response is graded.

​
Two ideas that hold it together

A record, a field, a repeated item, and an asset each have a stable ID. Renaming a column or a displayed value never breaks a reference. Editing a record updates every place it is used. See Reference lifecycle.
An exercise renders fragments (what the learner sees) and grades against stable IDs or accepted-value bindings (never against duplicated display text). See Exercises.