Intentarium

Agency Map Workbench · Local-first alpha

Make the hidden operating system visible.

Turn a difficult system into an explicit map of who may act, under which conditions, inside which boundaries, with what proof. The workbench code does not transmit or persist your field contents.

No sign-inNo field-content transmissionNo automatic persistenceSchema-valid export

Local-first workspace · v0.1

Map the operating logic.

Work through all eight dimensions, then export a portable Agency Map for people and agents.

Your field contents stay local by design. Intentarium’s workbench code does not transmit or persist them. Import, copy, and download happen only when you choose them; the hosting layer still processes normal page-request metadata.

0 of 8 dimensions ready0%

Begin with your own system, or load the production delivery example to see audit by design in practice.

Intent

Name the outcome before describing the current process.

Actors

Name each person, team, service, agent, or external party by role.

Authority

Connect responsibility to an explicit right to decide or act.

Boundaries

State what must never happen—and the mechanism that prevents it.

Trust signals

Define the current, scoped evidence required before an actor proceeds.

Evidence

Preserve durable proof of what happened, why, and under whose authority.

Escalation

Create a visible route for insufficient authority, confidence, or conditions.

Feedback

Assign ownership and cadence to the signals through which the system adapts.

Completion test

Your map should align accountability with authority, pair every boundary with enforcement, keep trust current, and give feedback an owner and response.

What happens next

A map creates a reviewable starting point.

The export is not a verdict and does not authorize execution. Review it with the people named in the map, test whether authority matches accountability, and carry the artifact into design, policy, implementation, or agent instructions.

Human artifact

Markdown for the room

Use the readable version in a workshop, decision record, architecture review, or implementation brief.

Machine artifact

JSON for the system

Use the structured version as a typed input to tooling after your own validation and authorization controls are in place.