What is this change meant to achieve?
Authored outcome, non-goals, and decisions—kept separate from what the code happens to do.
Software change intelligence
Know what changed. What it affects. What proves it.
Connect a GitHub repository. Putnami turns every pull request into a revision-specific view of intent, impact, constraints, risks, and evidence—for reviewers, builders, and agents.
Private betaNo full-stack migration required.
Change #842
4fa8c2eRoute EU checkout through regional gateway
Opened by Maya Chen · 18 minutes ago
- Intent
- Confirmed
- Impact
- 4 projects
- Evidence
- 12 / 12
- Unknowns
- 1 open
Keep EU payment data in-region without changing the US checkout path.
Source: checkout-routing spec · decision 04
checkout-apidirect change
billing-workercontract consumer
web-storedownstream
Payment contract changed
Billing ownership and regional failover require confirmation.
- Contract checks6 passed
- Passed
- Impacted tests6 passed
- Passed
- Runtime outcomeNot observed
- Open
The outcomeIntent Impact Evidence Unknowns
One change. The answers needed to move it forward.
A diff says which lines moved. Putnami explains the system decision around them, so the next person does not have to reconstruct it from code, CI, documents, and conversations.
What else moves if it merges?
Affected projects, dependencies, contracts, owners, environments, and downstream risk.
What proves the important claims?
Executed checks, artifacts, sources, freshness, and the exact revision each result supports.
What still needs a decision?
Missing evidence and unresolved contradictions stay explicit before they become production surprises.
How it works
From repository to decision in four steps.
Putnami derives what it can from systems that already own the truth and asks humans only for the intent and decisions that cannot be inferred.
- 01
Connect a repository
Keep GitHub, your CI, your documentation, and your runtime. Putnami begins with the system you have.
Repository connected - 02
Index an exact revision
Putnami maps projects, dependencies, ownership, contracts, checks, and declared intent to the commit they describe.
Revision-specific model - 03
Open a change
See the same change intelligence in the App, on a pull request, or from an agent through MCP.
Shared decision brief - 04
Decide from evidence
Review impact, constraints, executed checks, source links, and unresolved unknowns before the change moves forward.
Explainable decision
Product viewsRepository overview Change intelligence Agent and PR access
See the repository. Inspect the change. Use the answer anywhere.
Know what Putnami knows.
See the indexed revision, freshness, discovered structure, coverage, warnings, and the next useful action.
- Revision
- main · 4fa8c2e
- Structure
- 48 projects mapped
- Freshness
- Indexed 2 min ago
Review the whole change, not just the diff.
Bring intent, affected components, owners, constraints, risks, evidence, and unknowns into one revision-specific view.
- Impact
- 4 projects · 2 owners
- Evidence
- 12 checks passed
- Unknown
- Runtime outcome pending
Ask from the tools where work happens.
Give people and agents the same repository facts through pull-request checks and MCP—without another copied context file.
- Pull request
- Decision brief posted
- MCP
- Sources attached
- Answer
- Bound to 4fa8c2e
Trust by construction
Every answer shows its work.
Putnami does not ask a team to trust a confident summary. It keeps the facts, sources, checks, and gaps inspectable at the revision where a decision is made.
Exact revision
Every fact and check stays attached to the repository state it actually describes.
Visible sources
Follow an answer back to code, contracts, specifications, owners, and executed checks.
Separated truth
Human-authored intent remains distinct from derived facts and observed runtime evidence.
Honest unknowns
Missing, stale, or contradictory evidence remains visible instead of becoming generated certainty.
Progressive adoptionStart here Optional depth Managed expansion
Start with your stack. Go deeper only when it helps.
Intelligence is the entry point. Putnami Tooling, Frameworks, and Cloud add stronger guarantees capability by capability; they are not prerequisites for understanding a repository.
Your systemGitHub · CI · docs · runtime
PutnamiRevision-specific intelligence
Shared surfacesApp · pull request · agent
Putnami Intelligence
Connect an existing repository and make its structure, changes, and evidence usable by reviewers and agents.
Tooling & Frameworks
Adopt native contracts, deterministic jobs, impact selection, and application declarations where they remove friction.
Putnami Cloud
Add durable history, policy, delivery, environments, observability, and recovery when stronger guarantees are needed.
Private beta
Start with one change your current system cannot explain.
Bring a representative repository or pull request. We will identify the lost context, hidden impact, and evidence gaps—without asking you to migrate the platform first.