liveBook · Manning

Subgraph

As explained in Architecting for Autonomy

A subgraph is a selected subset of nodes and relationships from a larger graph.

A subgraph selects the nodes and relationships relevant to a specific enterprise decision. In a contract dispute, it may include the governing agreement, amendment, delivery obligation, evidence, possible defense, and related authorities, together with provenance, version, jurisdiction, effective period, and assertion status. section 5.4.1

Testing a breach claim

A delivery record supports a late-delivery proposition, which may satisfy a breach element only if the obligation applied during the disputed period. Increased order volumes instead connect through volume conditions and change control toward a possible defense. The subgraph keeps evidence, propositions, contractual effects, claims, and conclusions distinct, limiting unsupported semantic leaps. section 5.4.1

Table 5.3 Pattern card: Enterprise Knowledge Graph
Attribute
Definition and requirements
Mandate
Preserve the governed concepts and relationships through which agents interpret enterprise information. In law, this includes instruments, provisions, obligations, conditions, claims, factual propositions, evidence, and judicial authorities.
Scope
Apply it to reusable meaning that can affect retrieval, applicability, evidential sufficiency, explanation, routing, or agent authority.
Operating envelope
Constrain assertions by domain, jurisdiction, matter type, source class, effective period, purpose, and agent authority. Distinguish governed, extracted, inferred, disputed, experimental, and superseded relationships.
Boundary of authority
It defines enterprise meaning. It doesn't establish live facts, determine a claim, authorize action, or replace policy enforcement and professional judgment.
Failure mode
Restrict traversal, downgrade the result, return to authoritative sources, request validation, or reduce agent when you can't establish provenance or applicability.
Evidence & auditability
Preserve ontology and graph versions, source and relationship provenance, approval and assertion status, temporal and jurisdictional conditions, material traversals, and the decision episode influenced.

Use the pattern card to inspect the subgraph's operating envelope and authority boundary: it preserves governed meaning but does not establish facts, determine claims, authorize action, or replace policy enforcement. section 5.4.1

How Architecting for Autonomy covers it

How deep it goes
Defines selected nodes, relationships, and governance metadata, while stopping short of performing the model's language-based analysis.
Examples
Uses contract disputes involving agreements, amendments, obligations, delivery evidence, defenses, claims, and judicial authorities.
What it assumes
Assumes a governed knowledge graph and teaches selection by matter, task, and decision surface rather than whole-graph exposure.
What you can do after
Apply it via retrieval or a graph-query tool to constrain an agent's reasoning to relevant, qualified relationships.
How it connects
Connects enterprise knowledge graphs with retrieval, graph queries, provenance, jurisdiction, effective periods, and trusted context.

Also explained in

Compare how 3 books explain subgraph →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Architecting for Autonomy. The section links point to the parts of the book it draws on.