Entity Model Integration Report
Date: 2026-06-28
Status: Shipped (Stable tier) — Phases 1–18 complete; SDKs 0.4.2 on crates.io, PyPI, npm
Summary
The Unified Entity Model integrates registry, graph, query, traceability, verification, readiness,
health, and trust across REST, gRPC, CLI, SDKs, and Control Center. Every managed object routes
through EntityRegistry while preserving existing program- and device-level APIs.
Deliverables
| Deliverable |
Status |
Location |
| Entity registry & graph |
✅ |
crates/spanda-config/src/entity.rs |
| Verification engine |
✅ |
crates/spanda-readiness/src/entity_verify.rs |
| Readiness / health / trust engines |
✅ |
entity_readiness.rs, entity_health.rs, spanda-trust/entity_trust.rs |
| REST API (14 routes) |
✅ |
crates/spanda-api/src/sdk_ops.rs, entity_mutations.rs |
| gRPC entity RPCs (proto 1.0.14, 164 RPCs) |
✅ |
crates/spanda-api/proto/spanda/v1/control_center.proto |
| CLI |
✅ |
spanda entity * in crates/spanda-cli/src/entity_cli.rs |
| Rust / TS / Python SDK |
✅ |
crates/spanda-sdk, sdk/typescript, sdk/python |
| Control Center Entities tab |
✅ |
packages/web/src/EntityGraphPanel.tsx |
| CI smoke |
✅ |
scripts/entity_model_smoke.sh |
| API reference |
✅ |
entity-apis.md |
| SDK reference |
✅ |
entity-sdk.md |
| Topic guides |
✅ |
verification, readiness, health, trust, graph, query, migration |
| Examples (8 programs) |
✅ |
examples/entity/ |
Architecture change
flowchart TB
subgraph before [Before Phase 2]
V1[spanda verify] --> HW[hardware engine]
V2[spanda verify-fleet] --> FV[fleet_verify]
V3[spanda device *] --> DR[device registry]
ER1[EntityRegistry] --> API1["/v1/entities/* read"]
end
subgraph after [After Phase 2]
EV[verify_entity] --> ER2[EntityRegistry]
EV --> HW2[hardware]
EV --> MV[mission]
EV --> FV2[fleet]
EV --> DP[device pool]
EV --> QZ[quarantine]
EV --> CFG[config validation]
CLI2["spanda entity verify"] --> EV
API2["POST /v1/entities/id/verify"] --> EV
end
Verification routing by entity kind
| Entity kind |
Engines invoked |
robot, drone, vehicle |
Device pool, quarantine, hardware (optional program), mission (optional program), linked missions |
fleet, swarm |
Member graph, fleet verify (optional program), per-robot checks |
mission |
Mission verify (optional program), participant graph |
human, team |
Human registry availability and certifications |
device, sensor, actuator, … |
Device pool, quarantine |
package, provider |
Provider/manifest registry |
facility, building, zone |
Child entity graph |
| All |
Health/readiness/trust snapshot, relationship integrity, optional dependency chain |
Backward compatibility
| Surface |
Change |
spanda verify |
Unchanged |
spanda verify-fleet |
Unchanged |
spanda device * |
Unchanged |
/v1/programs/verify/* |
Unchanged |
/v1/devices, /v1/robots, /v1/fleets |
Unchanged |
/v1/entities/* |
Additive POST …/verify |
Migration notes
- Prefer entity verify for operational checks —
spanda entity verify rover-001 replaces
ad-hoc combinations of device inspect + verify when you need a single report.
- Program context is optional — hardware and mission checks run only when
--program (CLI) or
file (REST) is provided.
- Dependency traversal is opt-in — pass
--dependencies or "include_dependencies": true to
verify the full depends_on chain.
- Existing workflows unchanged — CI pipelines using
spanda verify do not need updates.
Validation results
cargo fmt --all
cargo clippy -p spanda-readiness -p spanda-api -p spanda -- -D warnings
cargo test -p spanda-readiness entity_verify
cargo run -p spanda -- entity verify rover-001 --config spanda.toml
scripts/entity_model_smoke.sh
Next phases (roadmap)
| Phase |
Focus |
Status |
| 1 |
Entity Registry Integration |
✅ Shipped |
| 2 |
Verification Integration |
✅ Shipped |
| 3 |
Readiness Integration |
✅ Shipped — evaluate_entity_readiness |
| 4 |
Health Integration |
✅ Shipped — evaluate_entity_health |
| 5 |
Trust Integration |
✅ Shipped — evaluate_entity_trust |
| 6 |
Relationship Graph |
✅ Shipped |
| 7 |
Control Center Entity Explorer |
✅ Entities tab shipped |
| 8 |
SDK EntityClient |
✅ Shipped + verify |
| 9 |
REST generic APIs |
✅ Shipped + verify |
| 10 |
CLI entity commands |
✅ Shipped |
| 11 |
Entity Query Language |
✅ Shipped |
| 12 |
Traceability |
✅ Shipped |
| 13–17 |
Documentation & diagrams |
✅ Shipped (overview, APIs, SDK, guides, architecture, examples) |
| 15 |
Example programs |
✅ examples/entity/*.sd (8 programs) |
| 18 |
Full workspace validation |
✅ fmt, clippy, grpc + entity smoke in CI |
Entity model tier is Stable as of 2026-06-29. SDKs published at 0.4.2 (sdk-python-v0.4.2,
crates-sdk-v0.4.2, npm-sdk-v0.4.2). See
entity-model-stable-promotion.md for gate history.