AmbitGet startedFAQReferenceGlossaryAll docsGitHubLive demo

The affordance frontier

Theory, ahead of the software. Why Ambit gives the argument; the README describes what runs today.

The object

The affordance frontier is the set of outcomes an assembled human-machine system can bring about. Its reach depends on people, tools, resources, authority and the environment in which they act.

Ambit currently models a narrow slice: a person's agents, tools and machines. The broader theory includes physical, cognitive, social, institutional and economic action.

Tools and target conditions establish technical reach. Authority is a separate requirement for attempting an action; success needs an observed result.

Why the theory says "affordance"

A hammer affords hammering to someone who can wield it, against a suitable target. The ability depends on that relationship.

Digital action works the same way. Shell access contributes to modify this running service only when the credentials, network, target software and authority line up. A robot's gripper contributes to open this door only when its geometry, force, reach and perception suit the door in its current state.

The product uses the plainer word capability. Providers and the capabilities they supply are separate nodes.

The hard cases

Robotics

Consider delivering medication to a patient:

Contribution Example
Planning Route and task selection
Perception Cameras and localization
Actuation Mobile base and gripper
Authority Permission to operate in this ward
Human participation Pharmacist loads the medication
Environment Elevator interface is reachable
Acceptance evidence Recipient confirms delivery

The delivery depends on the whole arrangement. Declaring a robot as infrastructure establishes none of its physical performance or safety.

Physical agency can also be distributed across machines and people. The relevant questions are which actions they can perform together, under what conditions, and through which actuators.

Brain-computer interfaces

A brain-computer interface couples intention, decoding, planning, actuation and sensory feedback. Picking up a cup depends on that circuit.

A person's intention produces a neural signal. The interface decodes it and drives an actuator; the environment supplies sensory feedback to the person.

Human participation takes different forms: approving an action, supplying knowledge or judgment, and using a machine to extend perception or movement. Approval is an authority dependency; knowledge is a contribution to performing the task. The map marks capabilities supplied jointly by a person and machine, but does not model a neural control loop.

From reachable actions to demonstrated outcomes

A dependency chain describes a modeled route. Testing the assembled workflow requires a defined result, an attempt and acceptance evidence. Separate deployment and monitoring checks do not establish that a system can release a service and recover from a bad release.

Each attempt needs its actual target, environment, time and available resources. Reach, permission and observed success remain separate facts. Evidence from staging supports a claim about staging and grants no production authority. Repeated attempts establish an observed success rate for the conditions tested.

Ambit already records outcomes. Roadmap §17 proposes binding versioned success criteria to the setup and evidence from each attempt. That layer is unbuilt.

Applications worth testing

These are proposed applications, grouped by their relation to the current model. Their feasibility and demand need testing.

Changes to an agent setup

Shared work

Other settings

Experiments and accountability

Economic agency

A paid service offers a concrete test: can its operator maintain delivery with less personal attention while retaining control and returns?

Customer acceptance, receipts and expenses need records separate from the assigned value of time. Control includes the ability to contact customers, change terms, export records and replace providers. Possessing code establishes little about those rights.

The same questions apply to collective ownership and options within employment. An operator's gains do not establish benefits for workers or customers; their changed options need separate evidence.

Intellectual genealogy

Field Contribution
Cybernetics Control through feedback
Sociotechnical systems Joint effects of people, technology and institutions
Security and attack graphs Permissions and topology composing into reachable paths
Capability approach Resources distinguished from effective opportunities
Agent evaluation Empirical task outcomes
Systems engineering and CMDBs Dependencies and failure propagation

Ambit combines dependency analysis with evidence and authority for one kind of assembled system. The capability approach motivates the distinction between possessing resources and having an effective opportunity to act.

The theory's longitudinal question is which outcomes become possible or cease to be possible:

C(S_t) = { outcomes S can reliably and legitimately cause at time t }
gained = C(S_t+1) \ C(S_t)
lost   = C(S_t) \ C(S_t+1)

Ambit's frontier history (ambit history) implements a narrow structural version of this comparison. It records gains and losses separately; a net count would hide contractions.

The AGI thesis

This is speculation. General agency might arise through composition: models, persistence, tools, infrastructure and people supporting consequential action across domains.

Model performance and system reach can change independently. Better reasoning may add little practical reach without authority or infrastructure. An unchanged model may participate in more workflows after those conditions change. Both claims can be tested through controlled comparisons across environments.

Cross-domain composition is the hypothesis to examine: can the system pursue varied goals without a separately authored workflow for each? Neither a larger capability count nor a successful scenario establishes that breadth.

What the software does with this

Enforcement applies to apply, execution routed through the control-plane proxy, and Claude Code calls using the installed gate hook. Other runtimes choose whether to consult it. The roadmap records the remaining gaps.

See what your own agents can reach

Ambit reads the MCP configs of Claude Code, Cursor, OpenCode and thirteen more agents into one local map: every server, which ones work, what one more step would open, and what breaks if a piece goes.

Open the live demoa sample setup in your browser, nothing to install

On your machine: npx ambit-cli, with Node 22.18 or newer on macOS or Linux.

MIT licensed · one local SQLite file, no telemetry · on npm and in the official MCP registry