OpenAPI defines endpoints. Terraform defines infrastructure.
DIS defines what AI agents are allowed to do, say, and reach.
A formal grammar, a W3C RDF/SHACL ontology, and a conformance suite.
Write your domain once, as a validated graph: who acts, on what, in which mode, through which system.
Why modern enterprise AI agents fail in production, and how DIS provides structural guardrails.
Six grammar fixes from the Argus trial give a triplet executable provenance: what it reaches, what it mutates, and what it is allowed to call.
A READ triplet cannot bind a function whose endpoint mutates; CREATE, UPDATE and DELETE triplets must bind one that does.
A function calling a mutating endpoint declares the entity it changes with writesEntity, and the triplet's target must match readsEntity or writesEntity.
A triplet with no executable function declares a bindingStatus (BOUND, MANUAL_PROCEDURE or ABSTRACT_UNBOUND) and an unboundReason, so a human step or roadmap gap is stated, not implied.
Endpoints declare a transport (HTTPS, MQTT, RTSP, NATS, gRPC and more), and an Application declares a networkScope so private-network systems can be modeled.
An access gate can name the exact catalog functions a role may run on an entity with allowedFunction, so “may disable, may not re-enable” can be stated.
A dossier is validated as one merged graph with the DIS vocabulary; scripts/validate-dossier.sh is the canonical recipe.
Validated with pytest, pySHACL and CUE. 196 automated tests cover the grammar, the shapes, the SPARQL queries and every reference dossier.
Pure RDF/Turtle knowledge graphs validated by SHACL shapes โ fully auditable with standard SPARQL.