InquirySpec - Ontological Boundary: The Digitality Interaction Schema models initiator, target, action, and context in cyber-physical exchange. - Not This: Not a UI flow diagram. - Doctrine Dependencies: Digitality Interaction, Scoped_Memory, The_Anatomy_of_Action.
Working Definition
The Digitality Interaction Schema is the grammar for turning situated action into an accountable digital payload. It identifies who or what initiated an interaction, what or whom the interaction targeted, what action was attempted, and what context must travel with the event so later coordination can remain intelligible.
In plain terms, it is the difference between "something happened in the system" and "this entity initiated this kind of action toward this target under these conditions."
The schema is not a screen flow. It is not a chat template, a workflow diagram, or a productivity form. A user interface may collect the information, but the schema names the underlying boundary event: a living situation, machine process, organizational commitment, or content object becomes a discrete record that can be routed, restored, checked, and repaired.
This matters because Digitality depends on boundary crossings. A request becomes a ticket. A decision becomes a logged commitment. A measurement becomes a dashboard event. A model response becomes an artifact another agent may reuse. Each crossing is useful only if the receiving system can tell what kind of action the record represents.
The Phenomenological Problem
Most digital coordination fails in small, ordinary ways before it fails dramatically.
A message says "approved," but nobody can tell whether it approved the idea, the budget, the release, or only the next conversation. A ticket says "blocked," but the target of the blockage is unclear. A dashboard shows a change, but the action that produced the change is not attached. A model output is copied into a document, but its intended use is no longer visible. A repair request moves across teams, but the receiving team cannot tell whether it is being asked to investigate, accept responsibility, escalate, or close the loop.
These failures are not usually caused by people trying to obscure the record. They are caused by systemic gravity. It is cheaper to type a sentence than to classify the interaction. It is easier to move an artifact than to preserve the role, target, action type, scope, and consequence path around it. Under pressure, the thin artifact moves faster.
The cost returns later. People argue over what was meant. Agents act on underspecified instructions. Audits reconstruct intent from fragments. Teams confuse commentary with commitment. A workflow treats a note as an action because the note is the only object the system can route.
The interaction schema is a defense against that drift. It does not make the action correct. It makes the action inspectable.
The Engineering Anchor
The internal interaction doctrine names the core payload as Initiator-Target-Action. That compact form carries a deep constraint: the system cannot responsibly route a cyber-physical event unless it knows where the action came from, where it was directed, and what kind of change or request was attempted.
The initiator may be a person, team, agent, workflow, sensor, content object, or larger scale-invariant entity. The target may be another person, a document, a system state, a future commitment, a past record, or an environment boundary. The action may be a request, claim, update, refusal, repair, escalation, classification, retrieval, restoration, or execution attempt.
This is where the node connects to The Anatomy of Action. Action is not only intention. In a cyber-physical system, action becomes durable when it passes through a form that can be logged and later evaluated against consequence. The schema provides the minimum grammar for that durability.
The connection to Scoped Memory is equally important. A payload should not behave like an open doorway. It may point toward a memory object, but governed access still requires scope, identity, authorization, and restoration boundaries. A reference can help the system find the right context without exposing every context.
This separation keeps three functions distinct:
Routing moves the interaction.
Restoration retrieves the permitted context.
Evaluation asks what the restored artifact can responsibly support.
When those functions collapse into one another, the system becomes brittle. Possessing a reference starts to feel like possessing permission. Seeing a record starts to feel like understanding it. Receiving an action payload starts to feel like accepting its consequence. The schema should prevent that shortcut, not strengthen it.
Boundary Conditions
The Digitality Interaction Schema is not a moral judge. It records the structure of an interaction so later assessment has something inspectable to work with. Accountability still requires human and institutional judgment, consequence review, and repair.
The schema is not total context. It does not carry the whole situation across the boundary. It carries enough structure to keep the event from becoming orphaned: initiator, target, action, state, scope, time, references, and relevant constraints.
The schema is not a universal claim that every interaction should become rigid or bureaucratic. Some contexts need light structure. Some need strong structure. The question is proportionality: how much structure is required for the action to travel without losing its accountable shape?
The schema is not direct agent-to-agent contact inside the machine. Human beings may experience a message as dialogue, but the machine sees discrete events: one entity writes, routes, restores, reads, responds, or acts. The social relation emerges through the sequence; it is not stored as a feeling inside the payload.
The schema is also not a replacement for language. It gives language a skeleton. A paragraph can still matter. Tone can still matter. Situated judgment can still matter. But if the system cannot tell whether the paragraph is a request, a decision, a repair note, or a consequence record, later coordination becomes guesswork.
Drill Path
Start with Digitality to understand why lived situations must cross digital boundaries as portable artifacts.
Move to Scoped Memory to see why references inside interaction payloads require governed restoration rather than open exposure.
Then read The Anatomy of Action to connect initiator, target, and action to capability, workload, warrant, consequence, and repair.
Use this node whenever a workflow says "send it," "log it," "approve it," "route it," or "ask the agent" without specifying what kind of interaction is occurring. The schema turns that vague motion into an accountable event.