About this project

# Agent Teams Engineering Foundation This repository provides versioned engineering policy, tooling, and conformance for Agent Teams repositories. It contains reusable development tooling only; product runtime code must not import it. Each consumer remains authoritative for its own domain model, package catalog, dependency permissions, security classifications, and ADRs. ## Scope - Strict data-only consumer configuration and versioned schemas - Executable workspace declaration and source dependency policies - Governed inline suppressions and released public API compatibility - Static executable-specification and consumer-gate connectivity - Repository workflow, SBOM, provenance, and package-content security policy - Portable agent instructions and changed-file preflight routing - Opt-in deterministic composition of existing package-script quality gates - Shared Oxlint and TypeScript 7 baseline presets - Explicit registry and local-link modes - Deterministic attach, status, detach, and registry assertions - Closed deterministic `Intent -> Plan -> Apply -> Receipt` scaffolding - Governed document catalog, deterministic non-reserving planning, create-only publication, and exact-version recovery commands - Isolated package-content and consumer verification - Release automation for immutable public npm versions Capabilities are extracted incrementally from proven repositories. A capability moves here only with parity fixtures and a consumer conformance test. `workspace.dependency-declarations` and `architecture.source-dependencies` are active and dogfooded. The repository uses schema v2 with the explicit `packages` package root, while the published v1 contract remains loadable for existing consumers. ## Commands ```bash pnpm install pnpm check:changed pnpm check:fast pnpm check pnpm verify pnpm package:check pnpm quality:gate:fast pnpm foundation:qualification ``` Consumers use: ```bash pnpm foundation:check pnpm foundation:attach -- /absolute/path/to/engineering-foundation pnpm foundation:status pnpm foundation:detach pnpm foundation:assert-dev-only pnpm foundation:assert-registry ``` Any repository can preview a portable documentation setup without mutation: ```bash docs-protocol init --project-id example/widgets \ --owner documentation/team --dry-run --json ``` After applying the reviewed digest, `docs.config.yaml` is discovered automatically. Search and bounded context remain disposable projections: ```bash docs-protocol find "tenant isolation" --fuzzy docs-protocol context "tenant isolation" --fuzzy --max-documents 12 docs-protocol check ``` Governed document authoring uses the installed Docs Protocol CLI. `owner` and `summary` are explicit Intent authority and never receive Foundation defaults: ```bash agent-teams-docs find "tenant isolation" agent-teams-docs new --type adr --id ADR-0083 \ --title "Tenant isolation" --owner architecture/tooling \ --summary "Defines the tenant-isolation boundary and its verification evidence." \ --dry-run agent-teams-docs doctor agent-teams-docs recover agent-teams-docs-managed upgrade --to docs-YYYY-MM-DD-N --target-generation 2 --json ``` After reviewing a dry run, repeat `agent-teams-docs new` with `--apply`, follow its exact reachability instruction, and run the consumer's standard repository check. `foundation:check` emits one deterministic aggregate report and enforces every declared capability. The optional `repository.agent-workflow` capability keeps `AGENTS.md` canonical across coding agents and routes `check:changed` through the shared Foundation implementation; required CI still runs the complete `verify` evidence as independent fail-closed lanes. `foundation:assert-dev-only` rejects runtime dependency placement. `foundation:assert-registry` additionally proves that the exact declared version has a matching pnpm lockfile importer, npm package entry, sha512 integrity, and snapshot without links, source URLs, overrides, or patches. The scaffolding kernel exposes strict schemas and a journaled filesystem adapter. It includes a testing-only conformance fixture and one generic private Node TypeScript library-boundary recipe. The latter creates only the package envelope; consumer business packages, roles, owner documents, and feature slices remain consumer-owned. See [ownership](docs/architecture/ownership.md), [consistency evidence gate](docs/architecture/consistency-evidence-gate.md), [governance capability acceptance review](docs/research/governance-capability-acceptance-review.md), [local development](docs/development/local-mode.md), and [release procedure](docs/release.md). The complete documentation index is [docs/README.md](docs/README.md).