Advanced and experimental

Experimental (alpha). Everything in this section is outside the main path (collision warnings, work intents and the hub), may change without migration, and has had limited testing. See the README for status and the changelog for known limits.

AgentSCM also contains an immutable ledger for exact revisions, their review contexts, approvals and protected-branch moves, plus bridges to and from Git. These parts work on a local, single-operator install and are described here for people who want to try them.

Native ledger

• Review contexts: the brief a revision is reviewed against

• Checks, evidence, the portable evidence verifier and installed policy

• Workspaces, task-scoped source and workspaces, merge sessions, offline sync, source history and the source reader

• Native CLI reference

• Native installation helper: agentscm setup, for contributors working from a source build

• Source-bound skill workflows: run exact-file checks and explicit packaged container commands against an immutable revision; inspect, resume, cancel or recover the run.

• Reusable workflow templates: bind one named, versioned manifest from immutable native source to an existing Change, install its first target requirement and retain a read-only handoff.

• Local workflow and skill library: author immutable skill packages and reusable workflow versions in the Hub, simulate declarations, and export action recipes to the existing operator-local pipeline.

• Agent-owned workflow task contract: strict task, attempt, instruction, assertion, enrolled-collector and recovery schemas with authenticated HTTP/MCP and Unix CLI routes.

• Intent review: compare a Git Work’s human request with current working bytes through a pinned skill in the existing agent; retain findings, bounded corrections and reassessment locally.

• Claude Code workflow loop: an opt-in local Stop trigger, tests/review, failure feedback and exact-current native landing requirements. Existing edit hooks remain contention-only.

• Community workspace pilot: persistent members/settings, independent roles, shared execution and explicit approval/native landing on one server. The legacy token dashboard and MCP remain inspection-only.

• Living Promises: immutable owner-authorized commitments, proposal adoption, stewardship and source-admission boundaries in the Workspace Hub.

• Laptop-to-hosted workflows: bounded source/context exchange and a remote Claude Code Stop hook under installed server policy.

Git bridges (shadow workflow)

Capture a Git commit, work and land natively, reconcile with Git and export to a local mirror you own. Explicit local-bare remote exchange is a separate opt-in command.

• Git snapshot capture, Git reconciliation, Git export and local Git remote exchange and authenticated network transport
• Attached Git worktrees: experimental read-only capture, exact mappings and conservative refresh; publication and nonempty attached-store recovery remain unsupported.

Isolated command checks

• GitHub merge queues: experimental workflow status on merge queue groups, with exact-tree rules, lifecycle recovery and read-only ruleset observations.
• Local validation attestations: experimental signed, Git-bound records of a maintainer’s local gate, verified by a separate workflow.
• Isolated command checks: run a declared command against an exact revision in a locked-down container. Not a sandbox for arbitrary hostile code.

Hub features that are experimental

These live in the hub guide and are labelled there:

• GitHub publishing (agentscm hub publish) and GitLab sync: tested only against in-process fake servers.
• The PostgreSQL profile (postgres in compose.hub.yaml) and S3-compatible object storage.