Skip to content
@bounded-systems

Bounded Systems

Bounded authority for AI agents — drawn at the door, not the process, not the container. prx + guest-room.

Bounded Systems

Keeping AI agents honest when they build and ship software.

Agents are increasingly trusted to write and ship real code. The moment you let them, the bottleneck stops being "can the agent do the task" and becomes "can you trust what it did" — across many changes, many tools, and many agent-authored components that all have to stay consistent as they evolve.

Bounded Systems builds that machinery: software delivered by agents but governed like infrastructure. An agent's git-writes are signed and attributable to their owner today — egress and external reads next — and every change moves through one content-addressed, auditable pipeline to a merged PR. Most tooling secures a single action — the harder, unsolved problem is enforcement between components, keeping a growing set of agent-authored contracts honest against each other.

We hold our own claims to that same bar. Every one on this page is graded against the running code — Enforced, Partial, or Aspirational — by an instrument built to catch our own over-statements and file the gap. Docs generate from source and fail CI on drift; guest-room's specs execute against its engine. We keep ourselves as honest as we keep the agents.

The capability model lives in two codebases: guest-room distills it into a single, readable library, while prx is the flagship that runs it at full scale on a stack of small, single-responsibility capability libraries — one for each kind of system authority (filesystem, network, env, subprocess).

Start here

guest-room — the model in one library

A guest-agnostic capability runtime built on rooms and doors. A door is a single unit of authority: you hold a socket to a brokered service, never the keys behind it. A room is a named bundle of doors, and authority can only ever be narrowed as it is handed onward, never widened. Its behavior specs execute against the engine, so the docs cannot drift from the code. Read this to see the capability model made physical.

prx — the flagship

The agent-run work-unit CLI — a work unit is one scoped task an agent owns end-to-end. Capability-scoped agents — git-writes signed and attributable to their owner — driving each work unit through one content-addressed, auditable pipeline to a merged PR. The @bounded-systems/* libraries below live in its monorepo under packages/.

The @bounded-systems/* libraries

Each is a narrow capability seam — the one sanctioned access point for one kind of ambient system power — so that effects stay attributable and policy stays enforceable.

Package What it is
anchored-chain Derivation chain with contract validation, signing, lineage tracking, and invalidation
anchored-chain-sqlite SQLite/Drizzle-backed implementation of the anchored-chain stores
audit-context Ambient runtime context for gh-call audit attribution
auth Service-credential resolver (GitHub, Notion) through a single sanctioned access point
bd Typed interface to the beads CLI with policy enforcement
cas Content-addressable storage: bytes addressed by their SHA-256 digest
disposition Pure classifier mapping work-unit state to a disposition (ok/prune/repair/review)
env The one sanctioned reader of process.env
fs Filesystem capability seam — the one allowed filesystem-access point
gh GitHub CLI wrapper with policy enforcement and budget audit logging
git Git CLI wrapper with policy enforcement and stale-lock recovery
github-budget Rate-limit-aware gh wrapper with bucket classification and audit trail
host The one sanctioned reader of host/OS ambient state
machine-schema Brands, handoff envelope, and state/phase primitives for work-unit machines
policy Tool-policy engine enforcing subcommand allowlists by tool, state, and role
proc The one allowed subprocess spawn point
repo-root Repo-root resolution capability
scout Content-addressed surface reads with anchored-chain provenance
slack Policy-gated, provenance-tracked Slack read surface
surface-sync Type ontology for work-unit change-detection across GH/branch/worktree/tmux/beads

Beyond the seams

Not every @bounded-systems/* package is a capability seam:

  • verbspec — spec-driven CLI core: author a verb once as a typed VerbSpec, then project it to CLI, MCP, OpenAPI, and Anthropic tool surfaces. One source, many surfaces.
  • prx-config — TUI configuration schema parser/emitter for the L1/L2 tools.

Links

prx, guest-room, and the libraries are source-available under PolyForm Noncommercial 1.0.0.

Pinned Loading

  1. prx prx Public

    The agent-run work-unit CLI: capability-scoped agents whose every privileged effect is verified against its signed owner, driving a work unit through one signed pipeline to a merged PR.

    TypeScript 1

Repositories

Showing 10 of 37 repositories

People

This organization has no public members. You must be a member to see who’s a part of this organization.

Top languages

Loading…

Most used topics

Loading…