Backstop is not an agent runtime, project-management system, or substitute for owning delivery decisions. Those systems can surround it, but they remain separate responsibilities.
Status and Boundaries
What is supported, limited, planned, or intentionally outside Backstop?
Deterministic product truth, presented without changing its owner.
Supported and limited
The first statement names shipped mechanism. The second names the process boundary without turning it into a future commitment.
Boundary states
Public status uses five explicit states: supported, limitation, planned, non-goal, and adjacent guidance. Each state has durable sources and a visitor implication.
Project boundaries
Adjacent guidance
Pack direction
Core stays thin while maintained packs own standards, engines, fixtures, and their release cadence. New coverage belongs in the pack that owns the concern.
Path-filter limitation
Slash-bearing engine path patterns can fail open when a gate supplies explicit changed-file arguments instead of a directory walk; pack validation reports this current limitation as a path-scope advisory rather than treating the ineffective filter as enforcement.
Release history
| Version | Commit | Committed UTC | Subject |
|---|---|---|---|
| v0.3.1 | 7dd4ecde45abf6edd5149e476b2847feb7bd276c | 2026-08-26T00:53:46Z | Reconcile the Bash pack acceptance plan (#11) |
| v0.3.0 | bc532ac172b74a237399d1044909fa236bc76b6c | 2026-08-25T13:20:02Z | feat: support client-owned external pack sandbox (#8) |
| v0.2.0 | 7546cc96036c7ea45d30f52f1cfa121628209ae6 | 2026-08-20T00:00:14Z | issue: close ISSUE-180/164/177 -- gate is fully green on real Linux CI |
| v0.1.2 | e7da80c76317cb80a50219e1313038d7bd8c4782 | 2026-08-10T23:13:18Z | fix(ISSUE-116): carry Line through the hollow-finding join, closes it |
| v0.1.1 | 87b12cf68525d51efdc7b5f6f57411ad5a86f935 | 2026-07-29T13:25:00Z | close(ISSUE-104,105): severity-contract hops delivered — plans completed, issues closed |
| v0.1.0 | a0fb366fec661d2ef7fcd2de5f777ad4ab9d2f31 | 2026-07-28T22:18:44Z | plan(ISSUE-020): final — severity ratification + TASK-032 as-built assertion wording |
Release-specific behavior is identified by immutable version and source provenance. Current adoption instructions target v0.2.0.