Impact Room reference environment

A small room for understanding agent impact.

Impact Room turns the boundary model into a visible scenario. The agent can observe the room and propose actions - the core decides.

Impact Room static reference environment showing an agent, scoped capability, boundary check, and guarded impact door

Agent observes

The agent can inspect the visible room state and propose what it wants to do, but observation does not include direct impact control.

Boundary checks

The boundary checks state, scope, approval, and evidence before any action is allowed to change the room.

Impact stays guarded

The door only changes after an admitted decision. Blocked or incomplete requests stop before impact happens.

How to read the room

The room is a simple target system. The door is the protected impact. The agent can propose an action, but the boundary decides whether that action may change the room.

01

Room state

The visible state the agent must read before proposing an action.

02

Scoped capability

The action the agent is allowed to request, not direct authority to execute.

03

Boundary decision

The check that decides whether the request is admitted, blocked, or incomplete.

04

Impact Door

The protected change that only happens after admission.

Why it matters

A visible demo and a minimal adapter pattern.

Impact Room does not only demonstrate a real-world use case for the Core. It also gives a compact example of how an adapter is shaped: expose public state, bind proposed intent to policy, and materialize only admitted work.

State view adapter

A read path for what the agent is allowed to see.

agent_surface.go
agent sees
http.go
filtered view
store.go
Impact Room adapter

A real adapter path from agent intent to guarded impact.

agent_surface.go
bind
http.go
admitted only
worker.go