Graph Engineering and the Current Industry

The industry has crossed an infrastructure threshold

Agent systems are no longer limited to one model call followed by a few tools. Current platforms increasingly provide long-running sessions, remote execution, persistent workspaces and Artifacts, coordinator-worker separation, parallel subagents, graph orchestration, checkpoints, Memory and Context management, triggers, approvals, budgets, sandboxes, interoperable protocols, operating-system kernels, and structured long-term Memory. These developments validate several premises of this manifesto. Durable work needs state outside one Context window. Coordination and execution benefit from separation. External effects require monitoring and recovery. Memory needs structure, and security cannot be reduced to prompt wording. The disagreement is no longer about whether serious agent systems require infrastructure; it concerns the abstraction that the infrastructure preserves and the object that remains authoritative when individual models and runs disappear. The comparison below follows the architectural convergence rather than a vendor sequence. Runtime harnesses make trajectories durable, protocols and kernels supply shared substrate, Memory systems make retained state more governable, and semantic IR systems move parts of work meaning outside the trajectory. Graph Engineering names the wider structural transition. None of those directions is dismissed; each supplies a necessary part of the system proposed here.

Durable harnesses solve execution continuity

OpenAI's Agents API exposes a managed Codex harness for work that can run over long periods, preserve files and intermediate Results, use tools, manage Context, and delegate to subagents with their own contexts.^{[1]Current agent systems and engineering evidencesourceOpen bibliography entry →} OpenAI's long-horizon safety work also recognizes that risk accumulates across trajectories and requires monitoring, intervention, and rollback rather than only one-shot evaluation.^{[2]Current agent systems and engineering evidencesourceOpen bibliography entry →} Anthropic's multi-agent research system demonstrates orchestrator-worker decomposition, parallel research, detailed subagent task descriptions, and synthesis.^{[3]Current agent systems and engineering evidencesourceOpen bibliography entry →} Its Managed Agents work separates a coordinating brain from execution hands and concentrates on the harnesses required for long-running tasks.^{[4]Current agent systems and engineering evidencesourceOpen bibliography entry →} Agent Skills package instructions, scripts, and reference material for lazy loading when relevant.^{[5]Current agent systems and engineering evidencesourceOpen bibliography entry →} Cursor Projects provides persistent project Context, a coordinator that plans and delegates rather than writing code itself, many parallel coding agents, and recurring or subscribed work.^{[6]Current agent systems and engineering evidencesourceOpen bibliography entry →} LangGraph contributes checkpointed graph execution, durable threads, stores, interrupts, and human-in-the-loop control, while Deep Agents combines planning, subagents, filesystem Context, and long-term Memory around a tool-calling loop.^{[7]Current agent systems and engineering evidencesourceOpen bibliography entry →[8]Current agent systems and engineering evidencesourceOpen bibliography entry →} Taken together, these systems establish a capable runtime layer: work can persist, recover, branch, invoke specialists, and continue after interruption. Their documented center nevertheless remains broadly similar. An agent or coordinator owns instructions, tools, Context, subagents, and a durable trajectory, while task descriptions and saved plans carry much of the current interpretation. Persistent Semantic Agency can use any of these systems as a cognitive or execution Resource; it changes the layer above them by preserving accepted Commitments, Decisions, Responsibility, Authority, Evidence, and Closure independently from the harness. Coordinator-worker separation therefore improves the architecture before it changes the ontology. It increases throughput and makes specialization practical, but a subagent prompt can still omit parent accountability, effective Decisions, delegated Authority, sibling interfaces, Evidence requirements, and Acceptance rights. A typed DelegationContract turns the handoff into durable responsibility state, while the coordinator becomes one replaceable Resource participating in that state.

Protocols and kernels provide shared substrate

The Model Context Protocol standardizes how applications expose prompts, resources, and tools to model clients, and its evolving specification includes authorization and extension mechanisms.^{[9]Interoperability protocols and extension systemssourceOpen bibliography entry →[10]Interoperability protocols and extension systemssourceOpen bibliography entry →} Agent2Agent defines interoperable communication around Agent Cards, Messages, Artifacts, and stateful Tasks.^{[11]Interoperability protocols and extension systemssourceOpen bibliography entry →} MCP can expose Capabilities and Sources under the proposed architecture; an A2A Task can carry one remote Delegation or Execution. Their proper role is transport, discovery, and interoperability rather than the universal definition of Commitment, Responsibility, epistemic support, compositional Authority, or Closure. Agent operating systems move another class of responsibilities below individual applications. AIOS centralizes scheduling, Context management, Memory, storage, access control, and LLM or tool Resources in a kernel shared by agent applications.^{[12]Graph Engineering and agent operating systemssourceOpen bibliography entry →} AgentKernel advances a more explicitly trust-native direction through mandatory enforcement across identity, perception, Memory governance, and execution.^{[13]Capability security and authorizationsourceOpen bibliography entry →} This is an important systems shift because isolation, scheduling, credential handling, and policy enforcement should not be reimplemented by every agent product. Skills and Plugin systems contribute a related extension discipline:

SEMANTIC LOGICpackaging ≠ semantic contribution
installation ≠ activation
workflow knowledge ≠ Capability
lazy loading
versioned manifests
stable ContributionPoints
isolation

Persistent Semantic Agency generalizes those distinctions. A Plugin packages contributions; an Extension adds semantics or functionality; a Procedure contributes reusable workflow knowledge; a Capability provider exposes Observation or action; a Module composes installed contributions into a domain runtime; Configuration specializes them without weakening Core law. Protocols, kernels, and extension systems therefore supply the substrate through which the semantic architecture can reach external systems without making transport or packaging its center.

Memory is becoming selective, temporal, and governed

Current Memory research increasingly separates active Context from larger stores, uses temporal and graph structure, filters what becomes durable, and distinguishes short-term preference drift from long-term tendency. MemGPT separates limited active Context from larger external Memory.^{[14]Long-term and personalized agent memorysourceOpen bibliography entry →} Zep and Graphiti use temporally aware knowledge graphs for changing relationships.^{[15]Long-term and personalized agent memorysourceOpen bibliography entry →} HeLa-Mem combines an evolving episodic graph with distilled semantic Memory, EMA adds selective Episodic Memory filtering, and preference-aware update work keeps short-term and long-term preference signals distinct.^{[16]Long-term and personalized agent memorysourceOpen bibliography entry →[17]Long-term and personalized agent memorysourceOpen bibliography entry →[18]Long-term and personalized agent memorysourceOpen bibliography entry →} A second group moves from retrieval quality toward governance. Kumiho uses immutable revisions, typed dependency edges, and belief-revision semantics; SuperLocalMemory adds admission, multi-scope access control, verifiable transactions, erasure, and audit; MOSS emphasizes symbolic and inspectable retrieval; MAGE treats long-horizon Memory as execution-state management.^{[19]Long-term and personalized agent memorysourceOpen bibliography entry →[20]Long-term and personalized agent memorysourceOpen bibliography entry →[21]Long-term and personalized agent memorysourceOpen bibliography entry →[22]Long-term and personalized agent memorysourceOpen bibliography entry →} These systems remove any credible claim that selective, temporal, versioned, or governed Memory is new. They also show why Memory alone cannot become the architectural center. Recall continuity and personalization remain different from canonical Work, current epistemic truth, purpose-bound UserModelSlices, Authority, and disposable Context. The manifesto's contribution lies in preserving those boundaries while placing Memory inside a wider constitution of delegated activity.

Semantic handoff and IR move meaning outside the trajectory

The closest contemporary precedents are systems that give some accepted meaning, admission, or reconciliation an identity outside one model's run. LoopX's accepted Capable Agent Manager and Semantic Work Handoff RFC preserves purpose, Context, Decisions, constraints, Evidence, current Commitments, and expected return across manager-to-worker and worker-to-worker collaboration. It also separates receipt, assessment, plan change, completed work, and delivered answer.^{[23]Semantic persistence and workflow/state representationssourceOpen bibliography entry →} LoopX therefore provides direct prior art for durable semantic continuation and authoritative work transitions outside one forwarded sentence. Its center remains a capable persistent manager plus LoopX-owned Goal and Todo semantics; the proposed architecture removes that manager from the ontological center and broadens the surrounding fabric. Workflow as Knowledge represents workflow definitions, workflow instances, inference records, Context snapshots, and dependency relations as persistent knowledge objects. It separates deterministic derive operations from LLM-mediated infer operations under declared Context and executor-controlled Capability Policy.^{[24]Semantic persistence and workflow/state representationssourceOpen bibliography entry →} The proposal is preliminary and workflow-centered, but it establishes stable identity and inspectable inference beyond individual model calls. Several software-oriented systems make the same move through domain IR. Spec defines language-agnostic IR families for autonomous software development, preserving requirements, architecture Decisions, invariants, tests, traceability, and specialized agent contributions.^{[25]Recent semantic compilers and domain-specific IR systemssourceOpen bibliography entry →} Cohesive treats software semantics as first-class persisted values, separates authoring projections from deterministic lowering and Acceptance, and reuses the same meaning for execution, validation, simulation, migration, observability, and Verification.^{[26]Recent semantic compilers and domain-specific IR systemssourceOpen bibliography entry →} LoomLoom compiles AI work into a reusable workflow and execution IR with typed inputs, Dependencies, model and tool Policy, Memory, recovery, budgets, validation, and Artifacts.^{[27]Recent semantic compilers and domain-specific IR systemssourceOpen bibliography entry →} Its public use of AI work IR is an explicit terminology precedent; the generic phrase Work IR cannot be claimed as unique here. Mozaiks defines an immutable canonical SemanticGraph, ImplementationBinding, and derived CompilationPlan for application generation. Agents produce candidate content, while deterministic mechanisms own serialization, reference closure, validation, rendering, and promotion.^{[28]Recent semantic compilers and domain-specific IR systemssourceOpen bibliography entry →} Software Control IR exposes structured application state and actions, validates before mutation, detects host divergence, and re-observes the actual application rather than trusting the action result.^{[29]Recent semantic compilers and domain-specific IR systemssourceOpen bibliography entry →} This group establishes substantial prior art for canonical semantic IR, compilation, candidate-versus-authority boundaries, immutable revision lineage, explicit execution Policy, and observed-state reconciliation. The important remaining boundary is scope: each system focuses on workflow, software generation, application control, or a persistent manager. Persistent Semantic Agency proposes a domain-independent constitution in which those domain IRs and managers become Resources or Modules inside a larger system of Commitment, epistemics, Responsibility, Authority, Observation, Assurance, and Closure.

Graph Engineering names the structural transition

The 2026 paper Graph Engineering in the Era of LLM Agents: From Individual Intelligence to System Intelligence frames a shift from isolated agent capability toward System Intelligence. It identifies task-organization, agent-coordination, and runtime-state graphs, and points toward ontology engineering, graph-native operating systems, and system evolution.^{[30]Graph Engineering and agent operating systemssourceOpen bibliography entry →} This is one of the closest contemporary descriptions of the movement addressed by the manifesto. It recognizes that intelligence increasingly depends on structure among heterogeneous agents rather than on the capability of one model. Persistent Semantic Agency takes a stronger ontological step: heterogeneous Resources are broader than agents; Responsibility topology is independent from agent topology; semantic continuity survives the end of inference; epistemic and normative validity remain distinct; Memory, State, Knowledge, and Context follow different laws; and Closure is derived from Obligations and Evidence. Graph Engineering is therefore a structural toolkit and a signal of convergence. A graph can expose task organization, coordination, capability, runtime state, Memory, Authority, Evidence, and Provenance, but those views become an architecture only when their object types, ownership, admission rules, and transition laws are defined. The representation makes relations visible; the semantic constitution tells the system what those relations permit.

The convergence has several persistent centers

The current generation supplies the substrate for a stronger center

Several conclusions are now well supported. Long-running work needs durable state outside one model Context. Context should be scoped and reconstructable. Coordination, execution, Observation, and Verification benefit from separation. Structured Memory is superior to raw transcript retrieval. Tool schemas need Authority and effect semantics around them. External effects require reconciliation, and system-level structure contributes intelligence beyond the capability of one model. The same review removes several possible novelty claims. Canonical IR, semantic compilers, proposal and Acceptance boundaries, versioned belief revision, governed Memory, explicit constraint state, commit-time Authority, semantic handoff, independent Observation, and effect reconciliation already exist in narrower systems. The proposed architecture depends on that work and should be evaluated as a synthesis rather than defended through ingredient-level priority. Its remaining contribution is architectural scope:

Use a domain-independent semantic constitution for delegated activity whose persistent state integrates Commitment, semantic Work, epistemics, governed Memory and User Models, independent Responsibility, compositional Authority, federated admission, Observation, obligation-based Assurance, and derived Closure, while domain-specific IRs, protocols, kernels, and harnesses operate beneath it. I have not found a prior architecture that combines that complete set around the same persistent center. This is a dated research finding with explicit limits, not proof that no adjacent implementation or unpublished system exists. The current generation has become durable, coordinated, extensible, and increasingly governable. Those advances make the stronger proposal plausible. The unresolved move is to transfer semantic continuity from the agent trajectory into a governed system whose models remain essential without remaining central.