GraphSpecDrafting
The domain vocabulary layer of SpecScore — entities, relationships, commands, events, and policies as graph artifacts.
Why
If many apps share one graph, the graph’s vocabulary — what entities exist and how they relate — must be specified once, not re-invented per app.
Connects to
A component of SpecScore; entities reference ModelSpec models; the Sneat graph is its validation pilot. This website’s node/edge format deliberately mirrors it.
What it makes possible
The shared graph gets a schema with a lifecycle — and tools (including this site’s engine) can be generated from it.
In the graph
- GraphSpec inspired Trakhimenok.com — graph-native navigation becomes a site
- The Shared Graph specified by GraphSpec — the graph needs a vocabulary
- SpecScore enables GraphSpec — hosts
- ModelSpec connects GraphSpec — model: refs