Graph Path Properties: Reading as Language, and Multi-Graph Creation Paths
The sentence test, stated as a requirement rather than a nicety.
team/humans/dinis_cruz/briefs/06/26/semantic-graph-and-query-paths/v0.33.35__arch-brief__sg-send-path-properties-read-as-language-ontology-of-ontologies-multigraph-creation-paths.md
Commitb561fa6b14 · carried 23 August 2026
LicenceApache-2.0 (repository) · CC BY 4.0 stated in the file
Bytes10,370 · 1,681 words · SHA-256 809b5f6a01868216
Dated26 June 2026
Why it is here
The site's grammar rule that a path must read as a sentence comes from here, and so does the reason it is a rule rather than a style preference: a path that does not read as a sentence is one whose edges were never named properly, and the failure shows up as soon as a reader tries to follow it. The graph explorer's path readout is this document, built.
What it says
- A path should read as a natural sentence in the reader's language and context.
- The recurring edge, such as managed-by up an org chart, is the clearest case for why direction matters.
- The model errs toward understanding over a standardised schema.
- Nodes and edges are nearly free, so anchor nodes can connect vocabularies and languages.
- Build the universe wide, then narrow it with queries: build the graph for the story.
Worth re-reading for. Compare its acceptance criteria against what the graph explorer now does. Two of the four are built; the other two are not.
Where this document lands on the site
The document is the peak. Below it hang the concepts measured in its text and the places on this site that rest on it — and the two are different kinds of link, drawn differently: a measured edge is dashed and carries its count, an authored edge is solid. The method is stated in full on the hub.