Context Circuit
Maintainers

Source repository layout

Edit the authoritative source; generated output is not the product source.

CLI 2.5.0

Source ownership

PathOwns
product/Shipped instructions, skills, docs, product guide, and 0BSD scaffold license.
template/Blank workspace records and configuration.
cmd/context-circuit/Native CLI entry point.
internal/cli/Commands and output, including the pin hand-off and guard.
internal/workspace/Records, YAML edits, Git, worktrees, and diagnostics; placement.go decides where every record goes.
internal/cow/Native cloning and independent-copy fallback.
internal/installer/Installer acceptance tests.
scripts/release-manifest.txt, assets.goSource-to-output inventory and embedded assets.
product/launcher/The workspace launcher, which runs exactly the pinned CLI.
release/README.md, how releases are cut; publication binding; repository-owned landing files; cli/README.md, the page inside every CLI archive; per-product release requests.
.changelog/One change file per user-visible change, until it ships.
agent-tests/Agent tests and committed baselines, run outside CI.
context/Product knowledge, public and never shipped; a pull request that changes code or agent behavior updates it in the same pull request.

The source checkout is not an initialized Context Circuit workspace. Maintainer changes follow its repository instructions and CONTRIBUTING.md, and merge into main as merge commits. Commit subjects use type(scope): imperative subject.

The CLI and source use Apache-2.0; the scaffold a workspace receives uses 0BSD. See validation before release assembly.

On this page