Prometheus Entity Management

One entity graph. Every framework. Realtime everywhere.

Prometheus Entity Management is a normalized, globally reactive entity graph for web, mobile, desktop, realtime, and local-first applications. Each entity lives once at a type + id address. Queries populate the graph, lists keep ordered IDs, and every view resolves the current canonical entity plus an explicit local patch. A single write therefore updates list rows, detail panels, relationships, badges, and policy-controlled generated UI without maintaining parallel query caches.

3.x release status

3.2.0 stable is published. All twelve npm packages are public at 3.2.0 with the latest and next tags pointing at it (published 2026-08-30). 3.2.0 ships the complete optional DevTools distribution, including bounded core event metadata and responsive React inspector search during continuous updates. It retains provider-scoped imperative graph access, A2UI 1.0-RC React/Flutter compatibility, and AG-UI 0.0.59 activity support. 3.0.0 shipped with an unresolved pnpm workspace: protocol in its manifests and is deprecated; 3.0.1 and 3.0.2 were corrective republications. 3.0.4 was published with stale build artifacts and is deprecated. Flutter 3.1.0 consolidates the completed controller and official DevTools companion, including multi-client cancellation. The Chrome DevTools 3.2.0 ZIP is available for developer-mode installation; it is not a Chrome Web Store listing. The production documentation is available at prometheus-ags.github.io/prometheus-entity-management.

Registry snapshot: 2026-08-30T22:54:50.026Z. Expected candidate: 3.2.0.

Package	latest	alpha	next	Release state
@prometheus-ags/entity-graph-core	3.2.0	3.0.0-alpha.0	3.2.0	published
@prometheus-ags/entity-graph-sdl	3.2.0	3.0.0-alpha.0	3.2.0	published
@prometheus-ags/entity-graph-solid	3.2.0	3.0.0-alpha.0	3.2.0	published
@prometheus-ags/entity-graph-svelte	3.2.0	3.0.0-alpha.0	3.2.0	published
@prometheus-ags/entity-graph-sync	3.2.0	3.0.0-alpha.0	3.2.0	published
@prometheus-ags/entity-graph-tauri	3.2.0	3.0.0-alpha.0	3.2.0	published
@prometheus-ags/entity-graph-web-components	3.2.0	3.0.0-alpha.0	3.2.0	published
@prometheus-ags/prometheus-entity-management	3.2.0	3.0.0-alpha.0	3.2.0	published
@prometheus-ags/a2ui-react	3.2.0	3.0.0-alpha.0	3.2.0	published
@prometheus-ags/entity-graph-a2a	3.2.0	3.0.0-alpha.0	3.2.0	published
@prometheus-ags/entity-graph-alpine	3.2.0	3.0.0-alpha.0	3.2.0	published
@prometheus-ags/entity-graph-htmx	3.2.0	3.0.0-alpha.0	3.2.0	published

The stable release is tagged v3.2.0 and was verified live against the public registry after publication. See RELEASING.md for the release contract, the governed OIDC promotion path, and recovery rules.

Why an entity graph

• One identity: canonical data is stored once; lists never copy entities.
• Cross-view reactivity: every projection rejoins the same current entity.
• Backend independence: REST, GraphQL, WebSocket, Supabase, Flint, PGlite, and CRDT providers populate one graph.
• Exact optimistic behavior: local patches stay separate from canonical state and retain the previous state required for rollback.
• Portable architecture: React, Flutter, lightweight web bindings, Tauri, and agent protocols preserve the same state and trust boundaries.
• Inspectable state: entity, patch, list, checkpoint, and offline queue state live in explicit stores instead of UI components or opaque query containers.

Architecture

flowchart LR
  View["Components / Views"] --> Hook["Hooks / ViewModels"]
  Hook --> Store["Stores"]
  Store --> Service["Services / Adapters"]
  Service --> External["REST · GraphQL · Realtime · Local · Native"]
  External --> Store
  Store --> View

Loading

Components → Hooks/ViewModels → Stores → Services/Adapters → External systems. Components render state and submit intent. Hooks or view models orchestrate store methods. Stores own application state. Services and adapters own I/O, subscriptions, authentication boundaries, persistence, and external protocols. Components never call the graph store or external services directly.

entities[type][id]   canonical server-confirmed data
patches[type][id]    local/optimistic overlay, merged at read time
lists[queryKey].ids  order + pagination + fetch state, never entity copies

When Task:42 changes, every list containing ID 42 and every detail or relationship projection reads the same new Task. Queries remain population instructions rather than competing data owners.

Package chooser

Start with the framework-neutral core, then add only the binding or integration packages your application needs. Bindings use an application-owned core peer so they cannot create hidden graph singletons.

Package	Candidate	Stability	Role
@prometheus-ags/entity-graph-core	3.2.0	stable	framework-neutral normalized graph
@prometheus-ags/prometheus-entity-management	3.2.0	stable	React 19 hooks and UI
@prometheus-ags/entity-graph-sdl	3.2.0	stable	schema definition language
@prometheus-ags/entity-graph-sync	3.2.0	stable	local-first and CRDT sync providers
@prometheus-ags/entity-graph-svelte	3.2.0	stable	Svelte 5 binding
@prometheus-ags/entity-graph-solid	3.2.0	stable	Solid binding
@prometheus-ags/entity-graph-web-components	3.2.0	stable	Lit web components
@prometheus-ags/entity-graph-alpine	3.2.0	stable	Alpine plugin
@prometheus-ags/entity-graph-htmx	3.2.0	stable	HTMX server adapter
@prometheus-ags/entity-graph-a2a	3.2.0	stable	A2A reference server
@prometheus-ags/a2ui-react	3.2.0	stable	A2UI React renderer and graph bridge after AG-UI migration
@prometheus-ags/entity-graph-tauri	3.2.0	stable	Tauri JavaScript binding and bundled Rust plugin

Package-level READMEs remain the package-specific API sources. The generated multi-package reference is produced from packed tarballs with TypeDoc packages mode under website/static/api/, published at /api/ on the documentation site.

Quickstarts

React 19 + Vite 8

Install the React package together with the matching core:

pnpm add @prometheus-ags/entity-graph-core \
  @prometheus-ags/prometheus-entity-management \
  react@19 react-dom@19

The example runs at http://localhost:5173 and covers normalized list/detail identity, optimistic confirmation and rollback, relationship invalidation, local/remote/hybrid views, REST/GraphQL seams, realtime coalescing, PGlite, Loro, Suspense, DevTools, and accessibility. See the React/Vite guide.

Opt into the optional inspector from a Vite client entry without adding it to production bundles:

npm 3.2.0 ships the optional ./devtools and development-only ./devtools/auto entries. The ordinary package root remains inspector-free.

if (import.meta.env.DEV) {
  void import("@prometheus-ags/prometheus-entity-management/devtools/auto");
}

The development launcher opens Overview, Entities, Views, Activity, and the Graph Pulse causal ribbon. It shows canonical originals beside uncommitted patch/live values, retained entity history, and every registered rendered view containing an entity. The launcher can be moved, compacted, hidden until reload, hidden for the browser, and restored with Ctrl/Cmd+Shift+G. Next.js applications use the explicit client-only ./devtools host after hydration so server markup remains unchanged. See the package DevTools guide.

Flutter + Riverpod 3

Install the public Flutter package from pub.dev:

flutter pub add entity_graph_flutter:^3.1.0

pub.dev snapshot: 2026-08-30T22:55:17.910Z.

Package	Version	State	Published
entity_graph_flutter	3.1.0	published	2026-08-30T22:50:00.407947Z

The published archive passed a clean consumer resolution, import, and analyzer check. pub.dev does not yet associate the package with a verified publisher.

Start with the package README and Flutter/Riverpod guide. The example uses generated Riverpod families, optimistic/offline CRUD, relationships, realtime invalidation, policy-gated GenUI, responsive layouts, and an optional FFI transport.

Flutter 3.1.0 ships an optional, metadata-first DevTools controller, store-isolated VM-service bridge, and official responsive DevTools package extension. Import package:entity_graph_flutter/devtools.dart only from a debug bootstrap; the ordinary package entry and product-mode builds remain free of the debugging surface.

Frameworks, transports, and platforms

Category	Supported 3.x surfaces
UI bindings	React 19, Flutter/Riverpod 3, Svelte 5, Solid, Alpine, Web Components, HTMX
Application runtimes	Vite 8, Next.js App Router, Tauri 2 desktop/Android/iOS
Transports	REST, GraphQL, WebSocket, Supabase Realtime, Flint Realtime Fabric
Local-first	PGlite persistence, Loro convergence, offline queues, reconnect recovery
Agent protocols	A2A JSON-RPC, official A2UI surfaces, default-deny action policy, optional human approval
Native seams	Tauri commands/events/capabilities, optional Flutter FFI transport
Schema/tooling	Entity SDL, generated declarations/providers, Rust CLI and MCP deliverables

Flint Realtime Fabric

createFlintAdapter translates watchEntities events into ChangeSet values, then RealtimeManager coalesces graph writes. publishFlintMutation delegates caller-owned mutations to mutateEntity. Tenant, channel, consumer, checkpoint, offset, issuer, kid, JWKS, role, and key-separation boundaries are explicit. Reconnect resumes from an acknowledged checkpoint; service-role/Forge credentials never enter client examples. The portable deterministic contract and live sibling-source evidence are separate and fail closed. Read the Flint guide and the portable release contract.

Example applications

All five applications use the shared Project/User/Task/Comment/Activity domain and scenario contract. “Implemented” is bounded evidence, not a claim that all npm packages, app stores, native signing, or stable npm promotion have occurred.

Example	Status	Source	Verification
react-19-vite-8	implemented	examples/vite-app	pnpm run verify:vite-react19
nextjs	implemented	examples/nextjs-app	pnpm run verify:nextjs-app-router
agentic-a2ui	implemented	examples/agentic-a2ui-app	pnpm run verify:agentic-a2ui
flutter-riverpod	implemented	examples/flutter-riverpod	pnpm run dart:ci
tauri-desktop-mobile	implemented	examples/tauri-universal	pnpm run verify:tauri-universal

Capability and scenario coverage

Every stable capability maps to release artifacts, semantic scenarios, executable examples, documentation, and evidence receipts in examples/coverage.json.

Capability	Stability	Scenarios	Evidence status
Normalized entities and ID-only lists	stable	example.graph.normalized-cross-view	implemented
Local patches remain separate and globally visible	stable	example.crud.optimistic-confirm example.crud.optimistic-rollback	implemented
CRUD with optimistic confirm and rollback	stable	example.crud.optimistic-confirm example.crud.optimistic-rollback	implemented
Relationship traversal and cascade invalidation	stable	example.relationship.cascade-invalidation	implemented
Local remote and hybrid view completeness	stable	example.view.local-remote-hybrid	implemented
Realtime batching and cross-view updates	stable	example.realtime.coalesced-cross-view	implemented, partial
Offline persistence reconnect and convergence	stable	example.offline.persistence-convergence	implemented
REST and GraphQL normalization equivalence	stable	example.transport.rest-graphql-equivalence	implemented
One application-owned graph across JavaScript bindings	stable	example.graph.normalized-cross-view	implemented
A2A task and A2UI policy-controlled surface flow	stable	example.protocol.a2a-a2ui-policy	implemented
Per-request SSR graph isolation and hydration	stable	example.runtime.ssr-isolation-hydration	implemented
Tauri desktop and mobile adapter boundary	stable	example.platform.adapter-boundary	implemented
Flutter graph and Riverpod adapter boundary	stable	example.platform.adapter-boundary	implemented
SDL and generated artifact structural round-trip	stable	example.schema.roundtrip	partial
Engine lifecycle Suspense errors and diagnostics	stable	example.runtime.lifecycle-security	implemented
Tenant action approval and secret safety boundaries	stable	example.runtime.lifecycle-security example.protocol.a2a-a2ui-policy example.platform.adapter-boundary	implemented, planned

Browse the allowlisted evidence gallery. Its generated manifest records scenario IDs, captions, alt text, source paths and SHAs, receipts, dimensions, certification status, and SHA-256. Gallery generation excludes failure diffs, blank captures, icons, bundles, internal paths, and token-shaped content.

Compatibility

Runtime	Supported line	Notes
Node.js	^22.14.0, ^24.0.0, or >=26.0.0	npm libraries and documentation tooling
pnpm	>=10.33.0 <12	pnpm 10.33.0 is pinned; pnpm 11 consumer workspaces are supported
React	19.x	vanilla core remains React-free
Next.js	App Router / 16.x example	one graph per server request
Flutter	3.44.8+	entity_graph_flutter@3.1.0; Riverpod 3 generated providers; official DevTools companion; A2UI 1.0-RC compatibility via GenUI 0.10.2
Tauri	2.x	shared desktop/mobile application and native plugin
npm module formats	ESM + CommonJS + loader-specific declarations	verified from packed tarballs

Development and verification

Purpose	Command
Install	pnpm install --frozen-lockfile
Site type/content contract	pnpm run docs:check
Site unit contracts	pnpm run docs:test
Site desktop/mobile routes	pnpm run docs:test:browser
Site production build	pnpm run docs:build
Packed TypeScript API	pnpm run docs:api
Dart and Rust APIs	pnpm run docs:native-api
README parity	pnpm run verify:readme-parity
Example coverage	pnpm run verify:example-coverage
Packed npm contracts	pnpm run verify:package-contracts
React/Vite showcase	pnpm run verify:vite-react19
Next.js showcase	pnpm run verify:nextjs-app-router
Agentic A2UI showcase	pnpm run verify:agentic-a2ui
Flutter workspace	pnpm run dart:ci
Tauri universal contract	pnpm run verify:tauri-universal
Flint portable contract	pnpm run verify:flint-contracts
npm trust relationship	pnpm run release:npm-trust:verify

Tier discipline matters: run cheap type or targeted unit feedback while editing; run full package/docs builds at phase completion; run Playwright, device, bundle, Lighthouse, and deployed-route gates only at delivery/release boundaries.

Migration, security, and operations

• 2.x and alpha migration
• Security and tenant boundaries
• Testing and troubleshooting
• RC and trusted-publishing runbook
• 3.0 release contract
• Architecture rules

At real trust boundaries, validate untrusted transport data, tenant and actor scope, A2A/A2UI actions, native capabilities, and secrets. Never ship service-role credentials to a client or treat protocol validity as application authorization.

Documentation, contribution, and license

• Production documentation: Prometheus Entity Management 3.x
• Documentation source: website/docs/
• Examples and scenario contract: examples/
• Contributing: CONTRIBUTING.md
• Changelog: CHANGELOG.md
• Release operations: RELEASING.md
• License: MIT