Interactive implementation view
Explore the connected system.
Inspect the same synthetic system through system, authority, control and evidence views. A connection is never treated as proof of authorisation, successful invocation or exploitability.
This page uses a different synthetic scenario from the home page: a refund agent rather than the procurement agent. Both are invented for illustration.
Bundled synthetic example
Every object and relationship in the synthetic system. 12 of 12 relationships shown.
Scroll sideways to see the whole graph.
- Relationship, drawn from source to target
- UNKNOWN: evidence is absent, insufficient or materially conflicting.
- Selected
- Ring colour: ontology family (Artifact #12, Appendix A)
- Actors, accountability and organizational roles
- Identity, access and authority
- AI behavior and decision influence
- Action surface and workflow execution
- Data, retrieval, memory and knowledge
- Assurance, governance and evidence
- Graph, boundary, path and consequence
Object · Actor
Analyst
The human analyst who starts the refund workflow.
Ontology definition
A human, organizational or machine-associated entity capable of initiating, approving, influencing or being accountable for activity.
Family: Actors, accountability and organizational roles. Artifact #12, Appendix A, verbatim.
Outgoing (1)
Incoming (0)
None in this graph.
Relationships in this view
Select a row, an object or a relationship label to inspect it.
Illustrative implementation only. The bundled example is modelled on the ontology’s synthetic pattern E.1 Agent delegated action (Artifact #12, Appendix E), with the approval, limit and evidence relationships that pattern says may constrain the path; its names, conditions and values are invented. Type and relationship definitions are quoted verbatim from Artifact #12. The public methodology remains vendor-neutral; the graph database is a replaceable implementation layer, not a source of methodological authority.