Home / Docs / The briefs / The ABP Is A Fractal Semantic Graph: One Row Crosses Nine Universes, Each Keeps Its Own Ontology, And The Ladder Runs Up To The Estate Of Agents

The ABP Is A Fractal Semantic Graph: One Row Crosses Nine Universes, Each Keeps Its Own Ontology, And The Ladder Runs Up To The Estate Of Agents

version v0.4.0 date 20 September 2026 from The site's agent, for the project lead to Whoever models the ABP graph, whoever builds the pages of abp.sgit.ai, and the teams at riskmandate.ai and store.sgit.ai who render against its data

type Dev brief (the mapping of the Agent Behaviour Policy onto Fractal Semantic Graphs: the universes an ABP crosses, the ontology each one keeps, the edges that join them, and the changes to this site in build order)

Written after reading this site at v0.3.0 in full, the platform guidance at sgit.ai/llms.txt, riskmandate.ai at v1.26.2 with its sixteen published behaviour policy vaults and seven lab pages, store.sgit.ai at v0.3.24, the Fractal Semantic Graphs page at sgit.ai/demos/fractal-graphs/ and graphs.sgit.ai at v0.6.22, including the correction it took at v0.6.21 that the grammar survives every zoom and the ontology is meant to change. Nothing here is implemented. It is a map, and the build order at the end says what each release would carry. Limitations: the universes above and beside the ABP are described by who owns them and by the edges into them, and their inner ontologies are named rather than written, because they are not this site's to write.

What This Is

The ABP, mapped onto the discipline the rest of the network now calls Fractal Semantic Graphs: this site already holds the ABP as a semantic graph, with fifteen verb edges, thirteen node type formulas and a lexicon in which read.file.project is three nodes, and by the zoom test as graphs.sgit.ai now states it that graph is mostly a well addressed hierarchy, because every zoom from a capability to its verb, object and reach lands in the same vocabulary; the fractal property lives at the edges of that graph, where a deployment shape opens into a vendor's vocabulary of tools, scopes and settings, where a barrier opens into a world of enforcers and layers, where a grant row opens into observations and probe runs, where a mandate opens into a deployer's own words about jobs, people and whose material, and where the whole ABP is one node in the licence and acceptance world that riskmandate.ai owns and this site must never hold; the finding is that an ABP is a junction object, its four objects are each owned by a different party who speaks a different vocabulary, and that is precisely the case Fractal Semantic Graphs exists for, so the right model is not one bigger ontology but nine small ones joined by named edges, with the grammar shared and nothing else; this brief names the nine universes one capability row crosses, from the source bytes to the licence condition, defines the ontology each keeps, lists every edge that crosses a boundary with its owner, settles the words altitude, level and universe so that the ruling of 20 August survives, answers the three open requests riskmandate.ai has published against this site by placing each in its universe, applies the zoom test row by row and reports which zooms are fractal and which are decomposition, and ends with the site changes in build order, one universe per release, with the universes that are gaps named as gaps rather than drawn. New here: the nine universes and their ontologies, the junction edge set, the lexicon scopes that let policy and control and grant mean different things in different worlds without a merge, the position on a connector that is present and switched off, and the rule that levels run up and down while universes run across, which is the one distinction that stops this map from becoming a hierarchy.

What Was Read, And What Each Source Settled

Three facts from that reading decide the shape of the map.

The first is the corrected definition of fractal. The first edition of graphs.sgit.ai defined it as one grammar and one schema at every zoom, and this site's own graph module still quotes that version: if zooming into a node needs a new format or a special case, the system is hierarchical rather than fractal. The second edition corrected it on 23 August and propagated it on 20 September: what survives every zoom is the grammar, being verb edges with inverses, meaning in connectivity, supersede never delete and provenance; the ontology is meant to change at every altitude, and a system whose types and verbs are identical all the way down is a hierarchy. This brief is written against the corrected definition, and the module docstring on this site needs the same correction.

The second is that riskmandate.ai has already built the instance this site describes. Sixteen behaviour policy vaults, each with a grant, a starting mandate, a derived delta, a licence to operate and the files an agent reads, nine of them for this site's shapes and seven for shapes this site's data does not carry. The instance exists; what does not exist is the join between the instance and the worlds around it, and that join is what this map is for.

The third is the sentence on the Fractal Semantic Graphs page. abp.sgit.ai's 23 capability primitives are the right shape to attach to a system's actual permission set; no published vault yet imports a real grant and computes the delta against a mandate at scale. The ladder on that page runs from the text of a law to a threat on one compute instance and this site is named as the rung where the graph meets a real permission set. The rung is named and the edges into it are not drawn. Drawing them is the work.

The Zoom Test, Applied To v0.3.0 Before Anything Is Added

The test has two halves. If zooming in lands you in the same types, the same verbs and the same vocabulary, you have a hierarchy. If zooming in needs a different grammar, the claim is false. Every zoom that opens a new ontology joined by a named edge to the last is the claim working. Applied to every zoom this site offers today:

The verdict, honestly. v0.3.0 passes the grammar half everywhere, which is the part that matters for a validator, a query engine and a provenance rule. It passes the recursion half in exactly two places, the reach class disagreement and the bridge to the game, and in three more places it takes one step into another world and finds it empty. Everywhere else it decomposes one vocabulary very well. That is not a defect in v0.3.0. It is the description of what a fractal map has to add: not more nodes in the grammar, but the worlds the existing edges already point at.

Three Words, Settled Before The Map

This site and the Fractal Semantic Graphs page use the word altitude for different things, and the map cannot be drawn until that is settled.

The rule that follows is the one that keeps the map from collapsing into a tree. The four objects of an ABP are not levels. The mandate is not above the grant and the delta is not below the barrier. They sit side by side at one level, and each opens into a different universe owned by a different party. A map that stacks them is a hierarchy with the wrong shape. The ladder runs up, to the licence and to the estate of agents, and down, to the word and to the byte. The four objects run across.

The Map: One Row, Nine Universes

The map is not a picture of everything, because the third graph rule forbids one. It is one query, run against one row of one published example, and it is the query every example page should end with once the universes exist. The row is send.endpoint.world in the shape anthropic/claude-code-remote/ccr-container, which is the shape this site is built from and the shape riskmandate.ai delivered its first vault for.

Read as one sentence, which is the fifth graph rule and the acceptance test: the words authenticate-as, credential and tenant spell a primitive that the shape ccr-container grants through its shell and its harness as a row known by inference, bounded by a boundary that the token's scope enforces and the platform set, which the mandate a coding assistant in a container left unstated, so the derivation of 11 September records it as excess and not unbounded, which the leaflet renders as a prohibition that is enforced today, and which the licence in vault ruj286tr carries as a condition beside its enforcer, for an owner who has not yet signed.

Nine universes, nine vocabularies, one grammar, one traversal. That sentence is the whole argument of this brief, and every clause of it is a node this site can hold or an edge it can declare.

The Universes, One At A Time

Each universe below is stated the same way: who owns it, what its centre of gravity is, what its smallest node is, its node types, its verbs with inverse, domain and range, the formulas that classify inside it, what exists on this site today, its status, and the edges that leave it. The verbs marked reused are in the published edge set at graphs.sgit.ai or in this site's own set already; the ones marked proposed are new here and follow the extension rule: a sentence, a different sentence for the inverse, a domain and a range.

U0 The source bytes

Owner nobody. Centre of gravity the hash. Smallest node a byte range in a file that was fetched on a date. Status live: every promoted file carries its source, retrieval time and content hash, and the build refuses to run if the bytes disagree with their manifest.

What this adds to today. Today the provenance block sits on every data file and says the same thing for every row in it. The Regulation Graph ends every chain in a hash of the retrieved bytes, per node. The per row version is what riskmandate.ai asked for in its Lab 03, request three, and it belongs here: a row's evidence is a node in U3 that is hashed_from a byte range in U0.

U1 The grammar

Owner abp.sgit.ai, promoted from what-can-it-do.games.sgit.ai and bridged back to it. Centre of gravity the primitive. Smallest node the word. Status live at v0.3.0 and complete for what it is: 10 verbs, 9 object classes, 5 reach classes, 9 families, 3 undo classes, 23 primitives, 33 word nodes with their own addresses.

This universe keeps the seven formulas it has: Verb, ObjectClass, ReachClass, Family, UndoClass, Capability and the rule that a specific path, host or mailbox is an instance of a primitive and never a new one. Nothing is added to it by this map, and that is deliberate: the grammar is the shared layer that everybody reads by address and nobody forks, so it has to stay small. Two verbs in it, receive and revoke, have nothing under them and are kept as named absences.

One property is added, on a proposal from riskmandate.ai, and it is added here with a per deployer override in U5. The property is material, with the values own, organisation, third_party and mixed: whose material a capability reaches. Reach answers how far; material answers whose. A property, not a fourth element of the grammar, because a fourth element multiplies the primitives and the vocabulary has to stay readable by address. The value that matters is mixed, because a mailbox is mixed, a shared drive is mixed, and no setting any vendor documents makes mixed into own. The lean riskmandate.ai stated, vocabulary with a per policy override, is adopted: the default lives on the primitive here, the override lives on the mandate in U5, and a delta records which one it used.

Edges leaving U1: granted_by into U2, authorised_by and withheld_by into U5, similar_to across the bridge to the game, hashed_from down into U0.

U2 The deployment shape

Owner the vendor's published words, read on a date, with a hash, and never probed. Centre of gravity the setting. Smallest node a scope, a flag or a line on a documentation page. Status half built: a shape today carries its tools, its reach names and the route each row goes through, as strings in a profile file. None of them is a node.

This is the first universe where the vocabulary is not this site's. A vendor speaks in OAuth scopes such as gmail.readonly, in tool names such as WebFetch, in flags such as dangerously-skip-permissions, in consent screens, in administrator settings and in the sentences on its documentation pages. The ABP does not translate those into its grammar. It keeps them in the vendor's words and draws an edge from each to the primitive it exposes.

What riskmandate.ai has already built in this universe, and what this map does with it. Its Lab 01 holds four vendor contradictions with verbatim quotes and URLs, and its vault directory holds seven shapes this site's data does not carry: two Gmail scopes, a Drive scope, a Microsoft 365 connector, a Dropbox server, the Google Workspace servers and an n8n instance measured live by an early user. Under the three layers those are layer one facts, owned by nobody, and they belong at the address every consumer reads rather than inside one consumer's vaults. The change is an intake path, not a merge: a shape proposed to this site carries its source, timestamp and hash, the gate checks them as it checks every profile today, and riskmandate.ai's vaults then pin this site's version of the shape rather than their own copy. That answers Lab 03 request two by placing it, and it is the request they marked as the one that unblocks a product.

The position on a connector that is present and switched off, which is Lab 03's second convention and the most common state in any real estate. The enforcer test already decides it. If the switch that turns the connector on is inside the agent's grant, the capability is in the grant at barrier setting, one click away, and the label counts it. If the switch is outside the grant, held by an administrator the agent is not, the capability is not in the grant, and it is recorded in U9 below as one setting away for the estate. No new barrier kind and no new label field: a capability is in the grant when the grant includes the means to reach it, and a switch is a means. The profile needs one node for the setting and one edge saying who can move it.

Edges leaving U2: exposes into U1, grants into U3, moves into U4, documented_at into U0, instantiated_by from U9.

U3 The grant and its evidence

Owner whoever observed, or the documentation that was read. Centre of gravity the observation. Smallest node one probe result on one instance on one date. Status one edge deep: every granted row carries an evidence tier and the tier is a node; nothing is behind the tier.

The GrantedCapability node stays what it is, the node that carries the barrier, because the barrier is a property of a capability in a shape and never of the capability itself. What opens behind it is the world that answers how do you know.

The formula that moves. Measured today is a headline, 21 of 99, counted from the observed tier. With observations as nodes it becomes a query: a row is measured when it has a -measured_by-> path to an [Observation] whose [Instance] was one we were entitled to run. The headline is then computed on every build rather than promoted from a sentence, per row, with a date, which is exactly what riskmandate.ai's Lab 03 asked for in request three. And the calibration loop on the delta page, where a deployment that runs and reports back moves a row from derived to measured, becomes an edge somebody adds rather than a paragraph. Lab 07's grant check, eleven of fifteen rows seen present in ordinary work and two probe batches refused by the platform's own classifier, is a SelfReport and two Refusals, and both node types are named here because that check has already happened and had nowhere to go.

Edges leaving U3: bounded_by into U4, authorised_by into U5, derived_into into U6, hashed_from into U0.

U4 The enforcement

Owner whoever set the control: the vendor, the platform, the deployer or nobody. Centre of gravity the enforcer. Smallest node one configuration line at one layer, set by one party, on one date. Status one edge deep: four barriers, three enforcers, one Control formula that the gate walks on every build. The formula is the most important thing on the site and it lands in a world with three nodes.

The dev brief of 11 September on the prohibition's two lives already wrote most of this universe's vocabulary and it was never made into nodes: five layers, prompt, tool schema, client rule, gateway and sandbox, of which only the last three are controls, and the datum that ask is a weak control because people approve roughly ninety three per cent of prompts. Lab 06 added the property the brief did not have: a barrier is perishable, and a classifier that refuses a probe today is a barrier with no row and no expiry.

The formula that carries the argument does not change and gains a second reading. Control is a barrier whose enforcer the grant does not include. With Party and removable_by as nodes and edges, does not include becomes a path: the grant includes the enforcer when the agent's own account is a -can_remove-> party of it. That is the same formula walked one universe further, and it is what lets a customer write EvidencedControl beside it without touching ours. The five layers become nodes so that the leaflet's rightmost column, the layer a control would sit at, stops being a string.

Edges leaving U4: bounds into U3, moved_by from U2, stopped from U3, compiled_from into U7, enforces_condition into U8.

U5 The deployer

Owner the deployer, in their own words, and the named person who will correct the draft. Centre of gravity the job. Smallest node one sentence somebody said about one capability on one date. Status eight starting mandates exist, each a want list, a refuse list and an unstated list over the 23 primitives, with a description and per capability notes in prose. The person, the job, the purpose and whose material are not nodes.

This is the universe where the estate's own rule that customisation and consolidation are one mechanism does its work. A customer's mandate is written in their vocabulary: per role rather than per deployment, per client engagement, per data class. It attaches to the grammar by authorises and withholds and to nothing else.

The interchange form lives here and nowhere else. The W3C rights expression vocabulary has permission, prohibition and duty, constraints on time, purpose, count and place, a conflict strategy in which prohibitions win, and inheritance, and the dev brief of 11 September placed it as the interchange vocabulary through a profile that adds these primitives as actions. In this map that profile is a projection of U5 and U6, written out in U7, and it is never claimed to enforce anything, because enforcement is U4. The name clash is not a problem: an ODRL Policy is a scoped term in U5's lexicon, the insurance instrument is a scoped term in U8's, and the behaviour policy is the root. The lexicon section below says how.

Edges leaving U5: authorises and withholds into U1, derived_into into U6, licensed_under into U8, elicited_from into U9 when a twin exists.

U6 The derivation

Owner the computation, and never a person. Centre of gravity the pinned input. Smallest node one stored record with its inputs, its time and the version of the code that produced it. Status live: nine stored deltas, each pinning the profile version, the mandate version, the pack version, the time and abp.delta/v1, recomputed by the gate on every build. What is missing is the series, the trigger and the crossing.

The delta page already wrote this universe's rules: the delta is a materialised view; reality is the third input; a recompute has a trigger and the trigger has a standard; a threshold crossing is a record and the consequence is a policy somebody set in advance; the history is the business case read rather than constructed. None of that is a node yet.

The rule that does not change is the one that makes this universe safe to open. No field on any node here is authored. A Trigger is received, a Crossing is computed, a Series is appended. The gate's twelfth check, which recomputes every stored delta from its pinned inputs, extends to the series without a new idea: every record in a series recomputes, and a series with a gap in its supersedes chain fails the build. Lab 07's history folder, one entry per recompute, is the live instance of Series and it exists in riskmandate.ai's vault today.

Edges leaving U6: derived_from into U3 and U5, projected_as into U7, crosses into a Threshold that U8 sets.

U7 The projections

Owner the renderer, and the fact diff that has to check it. Centre of gravity the fact set. Smallest node one rendered sentence that traces to one node. Status the label, the leaflet and the prohibitions exist and are generated from one call; AGENTS.md, SKILL.md and LICENCE-TO-OPERATE.md exist in riskmandate.ai's vaults; the fact set is not data and the fact diff, named as the blocker on four consecutive days in September, does not exist.

This is the universe where altitude in the 20 August sense lives. Every projection is a rendering of the same fact set for a different reader, and the diff over leaf assertions between any two projections must be empty. The classes differ by altitude, the facts do not.

Why this universe is where the fact diff finally gets built. The pack's specification was precise: the diff is over leaf assertions, not over structure. With FactSet as a node and every Projection carrying a projects edge to it, the diff is a set comparison over one node's edges, and the gate can run it on every build across the label, the leaflet, the prohibitions and the agent files. The multi audience promise on the store, which cannot be printed until the diff exists, becomes printable the release this ships.

Edges leaving U7: projects into U6, compiles_to into U4, licensed_under into U8, traces_to into every universe.

U8 The licence, the acceptance and the risk

Owner riskmandate.ai. Centre of gravity the named person and the date it comes back. Smallest node one condition beside the thing that enforces it. Status exists on riskmandate.ai as a template file in every published vault, unissued, and as the acceptance mechanism the Risk Graph Explorer and the Agentic Browser Isolation vaults already run. This site never holds it. It holds the anchor nodes the licence points at, and it declares the edges that cross into it.

The edges licensed_under, pinned_to, enforced_by on a condition and arises_from are declared by riskmandate.ai in its vault, pointing at this site's addresses by version and hash, which is the three layers construction working as designed: their formulas, their bridges, our facts, and nothing merged. The one sentence this site adds to its own pages is that the score has a home and this is its address.

Beside and above: the four universes this map names and does not draw

Named gaps get filled and unnamed ones do not. These four are named so that the next brief has an address to write to.

The Junctions: Every Edge That Crosses A Boundary

The property that turns a set of graphs into a fractal rather than a pile is the edge that crosses from one universe into another. Each one below is stated with the universe on each end and the party who owns the edge, because an edge is an assertion by somebody.

Twenty two junction edges. Seven are live, two are live in riskmandate.ai's vaults rather than here, one is a sentence on a page, and the rest are proposed or gaps. There is no relates_to among them and there will not be one.

The Lexicon Becomes Scopes, Because Name Clashes Are Not A Problem

One consequence of keeping nine vocabularies is that the same word means different things in different universes, and nothing breaks as long as the definitions are scoped and the overrides are recorded. graphs.sgit.ai holds its book's lexicon exactly this way at v2/lexicon: a root scope any other scope may link to, per source scopes that map their terms onto the root, an override recorded with its authority and the superseded definition kept visible, and a resolution rule: a term at a scope means that scope's definition if present, else the parent's.

The lexicon on this site today is one scope: the 33 words of the grammar. It should become the root of several.

The change is a scopes field on data/lexicon/index.json in the shape graphs.sgit.ai already publishes, with the root scope carrying the grammar and one scope per universe carrying the terms it overrides, each with its authority and the superseded definition kept. A term that appears in a scope and is neither mapped to the root nor marked as a named absence fails the build, which is the gate graphs.sgit.ai already runs.

What This Answers For riskmandate.ai

Lab 03 published three requests against this site on 12 September. Each is answered by placing it in a universe, and the answer is the placement.

The Site Changes, In Build Order

One universe per release, the live ones first, the gaps last and only as named absences. Every release regenerates every page from data, carries a version record with a sentence for a title, and passes the gate.

Three changes are not tied to a universe and belong in v0.5.0. The home page gains one paragraph saying that an ABP is a Fractal Semantic Graph and what that means, linking the definition on sgit.ai rather than restating it. The model index gains a sixth piece, the universes, beside the graph. And a media index at /media/ links, and does not copy, the seven licence to operate shorts and the three risk graph walkthroughs on sgit.ai, because this site was asked to be the home for the ABP's videos and visualisations and the honest way to hold somebody else's vault content is a link with a date.

One boundary sentence belongs on the README and the docs index. abp.sgit.ai is the free public library: the argument, the model, the universes, the examples, the data, the docs and the media. riskmandate.ai is where the ABP becomes a licence, an acceptance and a score, and store.sgit.ai is where one is bought. Each site links across and none restates the other.

What Must Not Change

• No score, anywhere. A score is a node in U8 and there is no edge to it from this site. The map makes the boundary an edge somebody else draws rather than a sentence this site keeps repeating, and that is stronger, not weaker.
• The delta is derived and never authored. U6 has no authored field and the series inherits the rule.
• Every prohibition carries its barrier. U7 renders nothing without an edge into U4.
• Nothing is merged. Nine vocabularies, one grammar, twenty two junction edges, and a scope per universe in the lexicon. A customer who cannot accept our definition of a control writes EvidencedControl and the facts do not move.
• Never render the whole graph. The universes page renders the walk of one row. There is no map of everything on this site and this brief did not draw one.
• Never probe anybody's system. U3 has an Instance node precisely so that every observation states whose system it was and that we were entitled to run it.
• The grammar stays small. U1 gains one property and no primitive. A new verb, object class or reach still needs a probe.

Honest Tensions

Open Questions

1. Is nine the right count, or should U0 fold into U3 and U7 into U6? The map keeps them apart because their owners differ: bytes belong to nobody, evidence to whoever observed, projections to the renderer and derivations to the computation. If the project lead reads owners differently, the count changes and nothing else does.
2. Does the material property go on the primitive or only on the mandate? The lean is adopted; the alternative is cleaner for the grammar and worse for the connector shapes.
3. Who owns the intake path for a proposed shape, and does a shape measured by a consumer's user carry a lower tier than one this site measured itself? The evidence tiers already have self reported; the question is whether a consumer's observation is documented or observed.
4. Should the universes be a vault rather than pages, given that riskmandate.ai's Lab 03 asked the same question of its own request list? The data files are the shared facts and belong at this address; the discussion about them may belong in a vault with write access on both sides.
5. Does the ODRL profile get published under this site's name, which the 11 September brief left open, or does it stay an unpublished projection until somebody compiles one?
6. What does a Trigger cost to receive? The continuous access evaluation profile is named as the right shape and its status was not confirmed. Nothing is wired and nothing here changes that.
7. Is a media index a page this site should hold, or does linking the shorts from the examples they demonstrate do the same work with less chrome?

Relationship To Previous Briefs

From the foundation document, it takes the four objects, the label and the two gaps, and gives the gaps addresses: U11 for quantity, U12 for interaction between agents.

From the dev brief on the behaviour policy as a graph, it takes the projection pattern, the W3C vocabulary as interchange, the five enforcement layers and the empty diff rule, and turns each into nodes in U7, U5, U4 and U7 respectively.

From the dev brief on the delta, it takes the materialised view, the three clocks, the trigger standard and the crossing as a record, and makes U6 and the second clock's home in U9.

From the pack's model document, it takes the ruling that altitude is for stakeholder and depth for detail, and keeps it by adopting a different word for the worlds.

From graphs.sgit.ai's second edition, it takes the corrected fractal claim, the zoom test in two halves, the scoped lexicon and the rule that name clashes are not a problem.

From the Fractal Semantic Graphs page on sgit.ai, it takes the definition, the word universe, the ladder, and the sentence that names this site as the rung where the graph meets a real permission set.

From riskmandate.ai's Lab 03 and Lab 07, it takes the three requests and the delivered vault, and answers the first by placing each request in its universe and reads the second as the live instance of U5, U6, U7 and U8.

Key Claims

Sources

All read 20 September 2026.

This site. abp.sgit.ai v0.3.0: the home page, the foundation document, the model pages, the lexicon, the graph pages, the five examples, every file under data/ and the four briefs and six pack documents under docs/.

The platform. https://sgit.ai/llms.txt and https://sgit.ai/docs/guidance/index.html. The Fractal Semantic Graphs page at https://sgit.ai/demos/fractal-graphs/index.html and its markdown twin. The licence to operate vault page at https://sgit.ai/demos/vaults/licence-to-operate/index.html and the risk mandate vault page at https://sgit.ai/demos/vaults/risk-mandate/index.html.

The discipline. https://graphs.sgit.ai/llms.txt at v0.6.22. The corrected fractal claim at https://graphs.sgit.ai/v2/books/fsg/content/06__fractal-is-a-testable-claim.md. The scoped lexicon at https://graphs.sgit.ai/v2/lexicon/data/lexicon.json. The edge set at https://graphs.sgit.ai/v1/grammar/edge-set.html, for observed_on, backed_by, measured_by, exposes, defeated_by and gives_rise_to.

The commercial sites. https://riskmandate.ai/llms.txt at v1.26.2, with https://riskmandate.ai/abp.md, https://riskmandate.ai/agent-behaviour-policy.md, https://riskmandate.ai/licence-to-operate.md, https://riskmandate.ai/how-it-works.md, https://riskmandate.ai/lab-abp-requests.md and https://riskmandate.ai/lab-vault-delivered.md. https://store.sgit.ai/llms.txt at v0.3.24, for the boundary between the three sites.

Outside the estate, as cited by the briefs this one builds on. The rights expression vocabulary at https://www.w3.org/TR/odrl-model/. The continuous access evaluation profile from the shared signals working group, whose status the delta page says to check before citing as settled.

This document is released under the Creative Commons Attribution 4.0 International licence (CC BY 4.0).