Skip to content

Concepts

Four graphs

Syderial rebuilds four graphs from the journal, one for each question a read must answer. All four come from the journal and nothing else.

Syderial computes its graphs from the journal and can discard and rebuild them at any time. There are four, one for each question a read must answer.

Permissionswho may see what
person · team · boundary · grant
Entitieswhat the entries are about
asset · person · organization · document
Ontologypolicies and decisions
policy · decision · applies to · supersedes
Capability and provenancewhat may act, and what it did
tool reach · agent · ingested · performed
The recordthe journal of signed entries
entry · line · evidence · receipt
Figure 1. Four graphs, rebuilt from the record. They connect only through the shared keys tenant, boundary and entity. A read crosses them in order, starting with permissions.

Available to design partners as it ships.

Who may see what. People, teams and roles, the boundaries they belong to and the grants between them. Syderial computes a reader’s clearance here, and reads this graph before the others on every request.

What the entries are about. Assets, people, organizations, places, documents and concepts, and the mentions that tie lines to them. Each relationship records how well the evidence supports it, and each entity belongs to a boundary.

Policies and decisions. Which decision a policy came from, where it applies and what it supersedes or adjusts. Syderial uses it to explain an outcome, such as why a reader can see a line. It never grants access.

What may act, and what it did. The capability half lists tools, agents and connectors and the reach of each. Syderial reads it before an action, and it can only narrow what the action may touch. The provenance half records what was ingested, extracted, invoked and performed. Syderial writes it after each action and uses it to explain.

A read crosses the graphs in order: who may see, what the question is about, which policy applies and what may act. The graphs connect only through the shared keys tenant, boundary and entity, so information can’t pass between them any other way.

The journal wins. Syderial rebuilds the graph from the journal, which corrects it.