Something went wrong. Try again.
A mental bridge between a hacker and their LLM(s) of choice.
Something went wrong. Try again.
name: data-model-scope description: Arcadia's rule for what noid's knowledge data model stores — file paths, connections and metadata, never on-screen positions. metadata: type: project #
noid's knowledge data model is limited to:
- paths to files on disk (the objects on the board are files; the db stores their paths, not their content),
- connections between them, including relationship types and notes,
- metadata about both.
It does not store the visual layout, such as absolute positions of nodes on the board. Layout is view state, computed (e.g. by a force-directed simulation) or kept ephemerally in the renderer, and stays out of the knowledge model and its saved file.
Why: Arcadia stated this on 2026-09-13 when she answered a question about where board positions should live. It keeps the graph descriptive (what relates to what, and how), not a picture of one arrangement.
How to apply: when a design needs a new attribute, ask whether it describes knowledge (files, relations, notes, authorship) or presentation. Presentation goes in view state, not the DataScript schema or .noid/graph.edn. See [[design-partner-workflow]].