Resources, tools and trust boundaries
Connect organizational permission to enforceable access, resource limits and observable tool effects.
#Resources are part of the organization
Resources include computation, model access, storage, documents, credentials, communication channels and human attention. Record who provides each resource, what it may be used for and how exhaustion is detected. A research organization may have local read access and a bounded inference allowance without permission to publish. Owning a tool connection does not establish authority for every operation that the connected service exposes.
#A tool call crosses a boundary
A mediated call should connect actor, task, permission, input and outcome. AxiomAO’s documented v0.3 development work includes scoped grants and receipts for its common file API. That is a specific path with a specific scope. Native client tools outside the common API do not automatically inherit its checks. State the covered operations explicitly and avoid describing an application permission mechanism as protection against processes that can directly modify its database.
#Containerization needs an explicit profile
The target architecture places execution in a containerized environment. Its profile must specify filesystem mounts, network reachability, operating-system privileges and resource limits. Docker’s security documentation describes several interacting mechanisms; a container label alone is not an assurance claim. The inspected AxiomAO profile runs locally without a supplied container image. Container packaging, engine authentication and isolation tests therefore remain separate implementation work, rather than an installation step this site can presently promise.
#External material is evidence to assess
A document, web page or incoming message can contain useful information and misleading instructions in the same payload. Its content should not grant new authority or alter the organization’s purpose. Keep source attribution, validate important facts and use an explicit path for legitimate policy changes. For example, a research page asking the agent to upload private documents is not authorization from the owner, even if the page appears relevant to the assigned topic.
Sources & context
Reference edition 0.1 · 2026-10-14. Read the editorial method.