‹ Product recipesProduct · Agent Blueprint
Cross-team architecture review
Where are two teams making conflicting decisions? Two decisions, overlapping scope, opposite polarity - caught before they ship.
Side by side: token usage, with and without Paperbase
~143k tokens saved · 84% less work for the agentWithout Paperbase
~170k tokens
- Read each team's recent design docs and decision records.
- Attach decisions to their teams manually.
- Search for overlapping scope by comparing terminology.
- Infer polarity from tone and wording.
- Discover the conflict when the systems collide in production.
With Paperbase
~27k tokens
- Pull recent Decisions across teams with their scope.
- Ask Paperbase to detect overlapping Decisions and compare polarity.
- Surface the conflict with both rationales and the teams involved.
- Pull the interactions where each decision was made.
Agent prompt
You are scanning for cross-team conflicts before the architecture review.
Using Paperbase:
1. Pull Decisions made in the last {{days}} days across all teams.
2. Ask Paperbase to detect overlapping scope: decisions that touch the same system, interface, or data.
3. For each overlap, compare the polarity of the two decisions - do they agree or conflict?
4. Pull the principle and rationale behind each side.
Output:
- Every pair of decisions with overlapping scope.
- For each: the conflict (if any), the two rationales, the teams, and where they will collide if both ship.
- A one-line recommendation for the review.Placeholders in {double_braces} are inputs the agent will ask for at runtime. Give the prompt to any agent connected to Paperbase, and the rest grounds in your own memory graph.