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
Product Overview
Understand what ShipFoundry does, what it does not do, and how updates become outcomes.
Quickstart
Move from signup to first useful update with one project and one tracked stack.
Working With Agents
Agent Workflows
Choose the right brief and move it into Codex, Claude, ChatGPT, Cursor, MCP, or Linear.
MCP
Connect ShipFoundry to a user-owned coding agent for current context, task packets, and outcomes.
Working With Updates
Investigation Briefs
Learn the core artifact ShipFoundry uses to turn a matched update into scoped work.
Sample Engineering Spike
Read a current example of evidence, missing proof, a bounded agent packet, and a stop condition.
Trust And Readiness
Read the recommendation safety states before acting on or exporting a brief.
Integrations
GitHub Repo Evidence
See how the required read-only repository connection works and what match-specific evidence can and cannot prove.
Linear
Export one generated brief into one Linear issue when the team wants downstream delivery tracking.
Account And Trust
What These Docs Cover
The launch docs focus on this activation path:
- Sign Up
- Create Project
- Add Stack
- Review Update
- Open Investigation Brief
- Check Trust And Readiness
- Deliver Through Copy, MCP, Or Linear
- 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