ShipFoundry Docs

Activation and trust docs for turning stack updates into agent-ready work.

ShipFoundry turns upstream software change into project-specific work: relevant updates, evidence-backed briefs, agent handoffs, and recorded outcomes.

Best Starting Path

Use these docs when you want to set up one project, understand why an update matched, decide whether the recommendation is ready for action, and hand the work to a coding agent without losing the trust boundary.

Start Here

Working With Agents

Working With Updates

Integrations

Account And Trust

What These Docs Cover

The launch docs focus on this activation path:

  1. Sign Up
  2. Create Project
  3. Add Stack
  4. Review Update
  5. Open Investigation Brief
  6. Check Trust And Readiness
  7. Deliver Through Copy, MCP, Or Linear
  8. Record Outcome

What These Docs Do Not Cover

These docs do not publish API references, GitHub issue export, broad Linear sync, automated implementation, or source-operator internals. Those should only appear when the product surface exists and the trust boundary is documented.

Product CTA

Start with Quickstart, follow the Agent Workflows path, inspect the Sample Engineering Spike, or create an account with Start 7-Day Trial.

Was This Page Useful?

Send a short note if this page is unclear, overclaims a capability, or is missing the proof you expected.

Send Docs Feedback for ShipFoundry Docs

On this page