APCC is an agent-first project context framework for software repositories.
It gives a repository a structured project context control plane so human developers and development agents can share the same project overview, end goal, execution tree, governance records, and local docs-site view without collapsing authored documentation into mutable runtime state.
This repository is the source of truth for:
- the installed
apccCLI - the shared prebuilt docs viewer shell
- the public docs package
- the regression suite used to validate packaging, docs-site lifecycle, and workspace behavior
The npm package is consumer-facing. The GitHub repository is maintainer-facing.
Install the published CLI:
npm install -g apcc
apcc --helpOr install it locally in another project:
npm install apcc
npx apcc --helpThe consumer-facing npm README is staged from assets/npm-readme.md during publish preparation so npmjs can stay focused on package usage.
Install dependencies:
npm installRun the CLI from source:
npm run dev -- --helpRun the main verification loop:
npm run check
npm run test
npm run build
npm run verify:package-install
npm run verify:site-lifecyclesrc/: CLI and control-plane implementationsite-runtime/: shared prebuilt docs viewer shell sourcedocs/public/: external usage docsdocs/internal/: maintainer-only documentationassets/: packaged workflow guidance and npm publish assets.apcc/: this repository's own APCC control plane
GitHub and npm deliberately serve different audiences:
README.md: repository and maintainer context for GitHubassets/npm-readme.md: consumer-facing package README for npmjs
Prepare a publishable package directory with the npm README:
npm run prepare:publish-package -- --out .tmp/apcc-publish
npm run prepare:publish-package -- --out .tmp/apcc-scoped-publish --name @rendo-studio/apcc