ImpactRoom
Definition
ImpactRoom is a reference adapter and local preview created by Impact Boundary Labs. It demonstrates how an external agent can act through a bounded public surface while visible changes depend on state, approval, and adapter-side materialization.
Why it matters
The name refers to both the demo story and the architectural example behind it. If you read it only as a room puzzle, you miss the reason it exists.
Example
An agent tries to open a door, but the result depends on whether the current scoped capability still matches current public state.
Reference adapter
Definition
A reference adapter is an example implementation that shows how to bind a domain-specific adapter into a larger runtime architecture.
Why it matters
ImpactRoom and MazeRunner are not only demos to watch. They are examples for developers who want to study a concrete binding pattern.
Example
ImpactRoom shows how a public action can become staged work, then later become visible impact only after validation and materialization.
Agent Surface
Definition
The Agent Surface is the public route set an external agent uses to connect, read state, move, post observations, and submit intent actions.
Why it matters
It keeps the agent on a guided public contract instead of forcing the agent to know private runtime internals.
Example
The agent starts with /connect, reads /agent/state, and uses returned submit metadata instead of composing raw internal requests.
Public Observation
Definition
A Public Observation is a short public note the agent posts before an intent action. In the current implementation the route name is /agent/thought, but the public meaning is an agent note, not a hidden reasoning channel. The canonical request field is text; observation is accepted as an alias for external-agent handoff compatibility.
Why it matters
It makes impact-oriented intent attempts visible in the public story without turning the system into a transcript of private model internals.
Example
Before trying Admin Override, the agent can post a note saying it sees the override station and wants to test whether the boundary allows it.
Affordance
Definition
An affordance is an action the public surface says the agent may attempt under the current public state.
Why it matters
Affordances are not guarantees of success. They preserve exploration while still keeping the public contract explicit.
Example
go_to_admin_override is an affordance at the start. try_admin_override is only an affordance when the agent is actually at the Admin Override station.
Operator approval
Definition
Operator approval is the separate human authority used for approval actions in the preview.
Why it matters
It keeps approval authority distinct from agent authority, which is one of the main lessons in the demo.
Example
The agent can request the scoped key, but a separate operator action is needed before the key can be issued.
Observer projection
Definition
Observer projection is the sanitized public state the browser reads to render the room, ledger, and current public status.
Why it matters
It shows that a useful public view can be smaller than private adapter state.
Example
The map and ledger update from observer routes rather than from private adapter state or hidden browser-only control paths.
State-bound impact
Definition
State-bound impact means a visible result depends on the state the system currently trusts, not only on the agent’s requested action.
Why it matters
This is the core idea behind ImpactRoom. The system does not treat intent alone as enough for visible effect.
Example
Opening the door depends on a key that is still valid for the current public door state.
Stale capability
Definition
A stale capability is a capability that was once valid but no longer matches the current trusted public state.
Why it matters
It explains why a previously issued key can later fail to create visible impact.
Example
The first scoped key can become stale after the relevant state changes, so the door-open attempt does not produce a door change.
No-impact
Definition
No-impact is a public outcome where the attempted action does not create the visible state change the agent was aiming for.
Why it matters
It is more informative than a generic failure because it preserves the idea that the action was evaluated but did not materialize.
Example
A stale key can produce no-impact feedback when the agent tries to open the door.
Materialization
Definition
Materialization is the step where the adapter applies a visible domain change after the admitted work still passes validation.
Why it matters
It separates “the request was asked for” from “the change became real.”
Example
The door opening is a materialized result. It is not identical to the earlier public request to open the door.
Outcome
Definition
An outcome is the recorded result after the work has been processed through the implemented path.
Why it matters
It marks the point where the system can publish a public result back into the observer story.
Example
After a successful fresh-key path, the outcome leads to a public projection in which the door is open and the agent can move to the final station.
WorkOrder
Definition
A WorkOrder is the admitted unit of work that later becomes claimable for adapter-side validation and possible materialization.
Why it matters
It helps separate public request handling from the later point where visible impact is actually applied.
Example
A public door-open action may be admitted as work, but visible door change only appears after the claimed work still matches the earlier binding.
Raw Broker route
Definition
A raw Broker route is a deeper internal route shape that belongs to the runtime plumbing rather than to the public agent contract.
Why it matters
ImpactRoom is intentionally built so external agents do not need to depend on those deeper route families.
Example
The public demo teaches agents to use /connect and /agent/state instead of reaching for the raw intent submission path directly.
Sanitized public projection
Definition
A sanitized public projection is the public-facing state view that is safe and useful to show without exposing private runtime details.
Why it matters
It is what allows the observer UI to be informative without becoming a leak of private adapter state or internal runtime records.
Example
Compact public door-state codes and public event labels can appear in the ledger, while private runtime identifiers remain outside the public surface.
Why this vocabulary matters
The terminology in ImpactRoom is intentionally small. Each term gives a technical visitor a way to talk about the demo without collapsing every layer into either “the agent wanted something” or “the backend decided something.” That vocabulary is useful for product explanation, architecture review, and adapter design. It also travels well to other reference adapters such as MazeRunner, where the domain changes but the underlying binding discipline remains similar.