Capabilities#
The independently versioned things the ecosystem builds and runs. Each capability is documented by a spec — the why and the what — and a design — the how and the what we build — kept side by side in the capability's folder. See the Documentation Model for how spec and design relate and evolve.
A capability whose design composes other capabilities is called a framework — an adjective, not a different kind of document. It lives here with the same spec-and-design shape as any other capability.
| Section | Description |
|---|---|
| Release Management | How a source change becomes a versioned, immutable artifact, driven entirely on the GitHub platform. |
| Repository Governance | How every repository in an organization is classified, protected, and continuously reconciled against the controls its classification declares. |
| Dependency Updates | How a repository's pinned dependencies are kept current and secure through automated update pull requests. |
| Merge Automation | How a pull request's required status checks become the machine-readable signal that drives automated approval and merge — green merges, red holds, nothing bypasses the gate. |
| Downstream Release Propagation | How a release in one repository propagates to the repositories that depend on it, via a delegated agent pull request. |
| Deployment | How a change to managed resources is approved together with its effect and deployed exactly as approved — one spec, and one design for each combination of deploying a service provider from a CI/CD platform. |
| VS Code Extension Framework | How a VS Code extension is built, tested, versioned, packaged, and published — one GitHub-native pipeline, opt-in from a template and a single settings file. |
| PowerShell on GitHub | How we make GitHub a first-class platform for PowerShell through reusable modules, actions, and capability gaps we close over time. |
| Agentic Development | The framework for org-scoped documentation that gives agents project-specific standards and behavior. |
Where this connects#
- Documentation Model — the spec-and-design model every capability here follows.
- Ways of Working — how the work that builds these capabilities happens.