Data Dictionary API — Help & references

Agents & automation — load in one request, straight to the API:

multipart body = manifest.json + the structure CSVs, with Authorization: Bearer <token> (see the auth guide below). The API loads it atomically into the working line — no separate upload step. A JSON bundle can be posted to …/ingest.

People use the Console's Load from store instead: get a one-time upload link, drop the bundle, then load it (curation — this replaced emailing zips). That landing zone is for the human flow and for very large / remote estates; agents don't need it.

Model top-down. Conceptual = business concepts + named relationships (M:N allowed). Logical = normalized entities with domain-typed attributes, keys, and cardinality-bearing relationships (resolve M:N into an associative entity). Physical = tables / columns / foreign keys. A foreign key is the physical realization of a logical relationship — the vertical thread is Concept → LogicalEntity → Table.

Author — address everything by natural key; write to the working line (snapshots are immutable):

Delete is RESTRICT by default (refused with DD030 + the dependent list); pass ?on_delete=cascade to remove the closure. Snapshots are sealed — writes to a snapshot label are refused (DD010).

Explore:

Relationships use Barker per-end cardinality (one|many) + optionality (mandatory|optional); layer and kind are inferred from the two endpoints. Full agent skill — DAMA framing, exact request bodies, a Barker cheat-sheet, and an end-to-end worked example — is served at /skills/data-modeling/SKILL.md (see “Agent skills” below).