# Warestack > Change management in GitHub, Linear, and Slack. Vanta stays GRC. Warestack runs the control as work happens. If you are Claude, Codex, or another agent: read this file, then `/catalog.json` and `/agents`. Propose a pack unless the organization connected the [Warestack MCP](https://documentation.warestack.com/model-context-protocol). Do not invent IDs. Write `unknown` when evidence is missing. Label every recommendation `week_one`, `on`, `off`, `later`, `candidate_only`, `not_generally_available`, or `unknown`. Merge-blocking stays off. ## Start here - [MCP](https://documentation.warestack.com/model-context-protocol): connect Cursor, Claude, or Codex at `https://mcp.warestack.com/mcp`. Skills: `npx skills add https://mcp.warestack.com` - [For AI agents](https://documentation.warestack.com/agents): inspect the last 14 days and propose rules, chains, reports, teams, owners, and readiness - [Machine catalog](https://documentation.warestack.com/catalog.json): stable IDs, availability, mappings, scope, honesty, and MCP tools - [Full agent brief](https://documentation.warestack.com/llms-full.txt): this index plus the full proposal protocol in one file - [Start the pack](https://documentation.warestack.com/start): what humans enable in 48 hours - [Use cases](https://documentation.warestack.com/use-cases): map delivery problems to shipped or explicitly draft capabilities - [Worked examples](https://documentation.warestack.com/examples): response shapes when evidence exists or is empty ## Operate - [Overview and attention](https://documentation.warestack.com/overview) - [Events and timelines](https://documentation.warestack.com/events) - [Pull-request stacks](https://documentation.warestack.com/events/stacks): same repository only - [Rules](https://documentation.warestack.com/rules) - [Rules catalog](https://documentation.warestack.com/rules/catalog): 24 catalog rules on pull requests, issues, workflows, and deployments. Cite **name** and `rule_key`; console chips Rule 1–13 are aliases - [Custom rule interpretations](https://documentation.warestack.com/rules/interpretation): reviewed ordinary checks, repository instructions interpreted at runtime, and bounded cross-repository context from the rule description - [Chains](https://documentation.warestack.com/chains) - [Chain kinds](https://documentation.warestack.com/chains/kinds) - [Dry-run](https://documentation.warestack.com/chains/dry-run): supported historical evidence, no side effects - [Automation activity](https://documentation.warestack.com/chains/activity): actual executions and delivery outcomes - [Slack live card](https://documentation.warestack.com/slack) - [Review SLA](https://documentation.warestack.com/slack/review-sla) - [Slack commands](https://documentation.warestack.com/slack/commands) - [Digests](https://documentation.warestack.com/slack/digests) - [Production changelog](https://documentation.warestack.com/slack/changelog) - [Linear](https://documentation.warestack.com/linear) - [Reports](https://documentation.warestack.com/reports): versioned reviewed definitions, scoped execution, server-owned draft commits, run history, async briefs, and CSV - [Metrics](https://documentation.warestack.com/metrics) ## Manage and trust - [Scope](https://documentation.warestack.com/scope) - [Teams and owners](https://documentation.warestack.com/teams) - [Repositories](https://documentation.warestack.com/repositories) - [People](https://documentation.warestack.com/people) - [Identities and owners](https://documentation.warestack.com/identities) - [SOC 2 and Vanta](https://documentation.warestack.com/soc2) ## Integrations - [GitHub](https://documentation.warestack.com/integrations/github) - [Slack](https://documentation.warestack.com/integrations/slack) - [Linear](https://documentation.warestack.com/integrations/linear) - [MCP](https://documentation.warestack.com/model-context-protocol): Cursor, Claude, Codex at `https://mcp.warestack.com/mcp` ## Availability - `available`: shipped surface or authorable template. - `week_one`: recommended for first enablement. - `later`: shipped, but not recommended for first enablement. - `candidate_only`: the individual may opt in; an admin cannot enable it. - `not_generally_available`: not a self-serve control yet. - `unknown`: missing evidence; do not guess. ## Hard boundaries 1. Candidate Linear references come from a known team key in the branch or title, a terminal `Refs:` trailer, or an explicit Linear issue URL. Arbitrary body mentions are ignored. Report linkage only after Warestack returns the persisted association. 2. A Linear parent does not cover child issues or sibling PRs. Associate each PR with the issue that describes its diff. 3. Bots and the PR author do not count as human approvals. 4. Pull-request stacks are same-repository. A custom rule may read bounded context from named related repositories only after a space admin approves the binding. Each referenced repository independently selects paths or directories and one revision source: branch, immutable revision, or pull request; different repositories may use different sources. Approved selected content, including private repository content, is sent to the Space’s configured evaluation model. This context is not a stack or blanket repository access. 5. “Later” chain kinds can still be shipped and authorable; it is rollout guidance. 6. A reason-required blocking-finding acknowledgement is revision-bound and audited. A GitHub user with Maintain or Admin access may use the exact standalone `/warestack ack :<64-hex-reference> --reason ` command from the current check without a Warestack account; dedicated SOC 2 period export and a complete exception register with owner and expiry are not shipped self-serve surfaces. ## Optional - [FAQ](https://documentation.warestack.com/faq) - [Help](https://documentation.warestack.com/support)