GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Warestack
  • MCP
  • Get started
  • Book a demo →
  • Question? Give us feedback
  • Edit this page on GitHub

This view

  • Original page
  • New address

GeezerVison is showing documentation.warestack.com — Warestack Documentation

Warestack sits in the tools your team already uses. A Linear issue, a GitHub pull request, a human review, checks, a Slack follow-up, and a production deployment stay connected — so you can see what a change is, who owns it, and whether it actually shipped.

You do not need a compliance program to use it. Teams use Warestack to keep reviews moving, keep Slack current, and stop guessing whether a PR is tied to a real ticket.

What you can do here

If this is the problemStart here
A ticket key is in the branch, but the PR may not be linkedRules
Reviews disappear into GitHubSlack live card and Review SLA
You need to know what needs you right nowOverview and attention
You need to know what actually shippedProduction changelog
Several PRs in one repo depend on each otherPull-request stacks
Connect Cursor, Claude, or Codex to the live spaceMCP

See the full use-case map and worked examples.

How the pieces fit

MomentIn Warestack
PlanLinear stores the issue association and can answer from that evidence
ChangeRules flag what is missing on the pull request
ReviewSlack keeps one live card current and reminds the requested reviewer, then the owner
ActOverview and Events show who needs to do what
ShipProduction changelog announces a successful production deploy
SampleReports save a query you can rerun and, if you want, post on a schedule

Start with one or two repositories. Merge-blocking stays off until you choose to require Warestack Rules in GitHub branch protection.

Warestack resolves known ticket references into persisted associations; it does not treat an unresolved string as proof, a bot as a human reviewer, or a merge as a production deployment. If evidence is missing, it says so.

If you also need a sampleable trail for SOC 2 or Vanta, that path is documented separately: SOC 2 and Vanta.

MCP

Connect Cursor, Claude, or Codex at mcp.warestack.com . Install steps, tools, and skills are on MCP. Sign in with the same GitHub account as the console.

npx skills add https://mcp.warestack.com

If you are an AI agent drafting a setup, use For AI agents.

You are visitor 01402520 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.