‹ Engineering recipesEngineering & SRE · Agent Blueprint
Design doc prep
Has this design pattern been debated before? Prior design-review threads on the same idea, so you do not re-litigate.
Why this is memory-only: the prior debate lives in historical interactions, objections, and rejected decisions that no ordinary artifact preserves.
Side by side: token usage, with and without Paperbase
Memory onlyWithout Paperbase
Not recoverable from search alone
- Search docs for the pattern name and related terms.
- Ask senior engineers whether it has come up before.
- Skim old review threads if any survive.
- Re-litigate a settled debate because no one remembers the answer.
- Ship a design that repeats a rejected decision.
With Paperbase
Persistent memory layer
- Ask Paperbase whether this idea or pattern has ever been discussed, across all historical interactions.
- Pull the prior threads, the objections raised, and the stances taken.
- See the decision that resolved it, if one exists.
- Write the new design doc already knowing what the room said last time.
Agent prompt
You are preparing to write a design doc.
Using Paperbase:
1. Search the full memory graph for {{pattern_or_idea}} - across meetings, threads, decision reviews.
2. Return every prior discussion of the idea, with date and participants.
3. For each, summarize the objections raised and the stance each participant took.
4. Note any Decision that resolved the question, and the rationale.
Output:
- Whether this idea has been debated before, and when.
- The recurring objections, quoted.
- The resolution, if any, and why.
- Your recommendation: proceed, revisit with new evidence, or drop.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.