Skip to content

Architecture Docs → ABIO infra

ABIO Data

Organization of the data/ folder and intent-based categories.

  • The data/ folder contains all persistent data managed by the ABIO DAT system.
  • Every folder containing a _spec_.yaml file is a self-describing DAT object with contents and provenance.
  • Top-level categories represent intent - each is an intrinsic type:
  • Each top-level category contains items of that intrinsic type.
  • The top-level item determines the category - it's the "primary" type. Nested DATs inside can be any type.
  • Placement answers: "What is this thing's primary purpose?"
    • chem/kegg1/ = "I built this chemistry to be shared/reused"
    • world/simple1/chem/ = "I built this chemistry for this specific world"
    • test/T1/world/chem/ = "I built this chemistry for this specific test"
  • This allows cohesion when things are built together, while still enabling sharing when components are used across multiple contexts.

See Also

  • ABIO DAT - dvc_dat integration, name resolution, _spec_.yaml format
  • ABIO Files - Full project directory layout