A capability describes the work.

An agent profile, a skill, or a workflow describes how work might be done. It can define instructions, tools, context, models, dependencies, and tests. Teams need to know which version they are using, where it can run, and what evidence supports it.

This is the problem Rangoon is being developed to address: composing and inspecting SI capabilities before deployment. The workspace records compatibility, provenance, evaluation inputs, and interfaces between components.

Configuration is not a grant.

A workflow that includes a database connector describes an available integration. Each database write requires exact authorization.

Authority is a separate decision.

Consider an agent proposing a catalog correction. The request should identify the actor, resource, exact operation, parameters, environment, and applicable limits. An authorization record names the requested catalog change.

LNSAT is the separate execution-authorization and evidence engine in this architecture. Policy evaluates a bounded action. When human review is required, approval attaches to that exact action. A changed target or payload requires a new approval.

Tool access and action authority answer different questions. MCP can provide a tool interface. The application authenticates requests and enforces what a specific actor may do; the owning system grants that authority.

Evidence closes the loop.

Completion is confirmed by the observed result. Systems distinguish proposed, approved, authorized, attempted, completed, failed, and unknown outcomes. Timeouts and partial failures make that distinction important.

Execution evidence should connect the requested operation to the observed result. Reconciliation can then investigate ambiguity without repeating a consequential write by default. This is why authorization, one-time use, idempotency, and audit records are part of architecture rather than interface decoration.

LNSAT remains pre-release source software focused on bounded execution authorization and evidence. Rangoon is in development.

What this means for a business.

Start with an existing workflow and a bounded outcome. A first release might retrieve evidence, summarize exceptions, or prepare a change for a person to review. It should be useful before it is autonomous.

  • Keep business records and source systems authoritative.
  • Define what a current model can read, propose, and request separately.
  • Test ordinary paths, denied actions, retries, and unavailable dependencies.
  • Give operators a clear record and a recovery path.

The goal is not more automation at any cost. It is software that can do useful work without obscuring ownership, risk, or what actually happened.

Rangoon LNSAT Our approach