Product Overview
What ShipFoundry does, what it does not do, and how relevant updates become outcomes.
ShipFoundry watches the software stack around your product and turns important upstream changes into scoped, evidence-backed work for each ShipFoundry project.
When To Use This
Use ShipFoundry when your product depends on fast-moving frameworks, platforms, APIs, SDKs, models, devtools, infrastructure, or external services, and you need to know which changes are worth investigating or shipping.
ShipFoundry is useful when the question is not just "what changed?" but:
- Does this matter for my product?
- Where might it touch my stack or repo?
- What evidence supports the recommendation?
- What should a human or coding agent inspect next?
- How should we record the outcome?
How It Works
ShipFoundry separates four surfaces:
| Surface | Purpose |
|---|---|
| Update Match | A public stack update appears relevant to a tracked product. |
| Brief Output | ShipFoundry routes the opportunity into a Research Brief, Engineering Spike, Workflow Brief, Strategy Brief, or Hand To Agent packet. |
| Agent Handoff | A brief becomes bounded enough for copy/paste, MCP, or explicit Linear export. |
| Outcome | A user or agent records whether the update was investigated, useful, adopted, waiting, needs review, ignored, or a false positive. |
Step-By-Step
- Create a project.
- Add the stack items that matter.
- Connect one GitHub repository for required read-only project context.
- Review relevant updates.
- Open the recommended brief and check its output lane.
- Hand bounded work to an agent through copy/paste or MCP, or explicitly export it to Linear.
- Record the outcome so future matching improves.
What ShipFoundry Does
- Watches external vendor changelogs, release notes, docs updates, and source surfaces.
- Matches upstream updates against product context and tracked stack items.
- Checks the connected repository and adds match-specific evidence when applicable proof exists.
- Routes briefs into Research Brief, Engineering Spike, Workflow Brief, Strategy Brief, or Hand To Agent lanes based on evidence and uncertainty.
- Supports MCP and Linear as optional workflow layers.
What ShipFoundry Does Not Do
- It is not a generic RSS reader.
- It is not your product changelog.
- It does not automatically modify repositories.
- It does not create PRs or commits.
- It does not claim repo proof when no repo evidence has been collected.
- It does not require Linear. Project setup does require one selected read-only GitHub repository.
- It does not force an agent packet when the evidence cannot support useful work.
External Stack Updates Vs Product Changelog
External stack updates are inputs. They come from providers such as framework teams, API vendors, model providers, infrastructure platforms, and devtool maintainers.
Your ShipFoundry changelog is different. It describes changes to ShipFoundry itself.
Not every external update becomes a relevant update. ShipFoundry filters for product fit, stack fit, readiness, and evidence.
Troubleshooting
If the update list feels too noisy, tighten the tracked stack and ignored sources for the product.
If no updates appear, add more stack items, confirm the product context is current, and check whether the source coverage for that stack exists yet.
If a recommendation feels wrong, record the outcome instead of deleting the signal. False positives are useful feedback.
Related Pages
- Next setup step: Quickstart
- Core artifact: Investigation Briefs
- Agent workflow: Agent Workflows
- Example artifact: Sample Engineering Spike
- Safety model: Trust And Readiness
- Product CTA: 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 Product Overview