Where Should This File Go in Snipara?
A practical guide to classifying documents, diagrams, templates, repo files, historical work, and durable decisions across Team Business Context, Team Code Context, active projects, and memory.
Alex Lopez
Founder, Snipara
- Readable in 8 minutes
- Published 2026-04-27
- 6 context themes covered
Most confusion in Snipara starts with a classification error. The product is straightforward once one rule is clear: reusable company knowledge, active project truth, and durable memory are not the same thing and should not be stored in the same place.
Key Takeaways
- Team Business Context is for reusable business knowledge shared across projects.
- Team Code Context is for engineering rules and technical standards that should guide coding work across repositories.
- Client or project context is where current truth for one client, repo, or mandate belongs.
- Memory is for durable decisions and learnings, not for storing raw documents.
The Fast Decision Table
| File or knowledge | Where it goes | Why |
|---|---|---|
| Company methodology PDF | Team Business Context, Business Library | Reusable across many clients |
| Past proposal for ACME | Past client project, historical reference | Useful precedent, not current truth |
| Current XYZ RFP | Current client project, current truth | Authoritative for the active response |
| Engineering review checklist | Team Code Context | Guides coding work across repos |
| Repo README | Code project | Explains one repository or product surface |
| Architecture SVG for a codebase | Code project | Technical implementation diagram |
| Network topology SVG for a client offer | Client project or Team Business diagrams | Business or presales visual context depending on scope |
| Decision: “Use Prisma for new services” | Memory | Durable rule, not a raw source document |
Team Business vs Team Code
Team-level context is for rules and reusable knowledge that should apply across many future tasks. It is not the place to dump active client material or repo-local truth.
Team Business Context
Business Response Playbook, Business Library, offer templates, company presentations, reference diagrams, approved examples, delivery methodology.
Team Code Context
Coding standards, review rules, security requirements, architecture defaults, testing policy, migration rules, local engineering patterns.
Historical vs Current
Past client work is valuable, but it should remain clearly historical. Current client or project context is the active truth. Mixing those two causes the worst LLM mistakes: copied names, outdated constraints, stale diagrams, and false assumptions.
Rule of thumb: if the file answers “what is true for this task now?” it belongs in the active project. If it answers “how do we usually do this?” it belongs in a reusable collection or historical project.
When It Belongs in Memory Instead
Memory is not another document bucket. Use it for decisions, learnings, troubleshooting outcomes, and preferences that should be recalled later without re-reading the entire source every time.
- Good memory: “This client rejects diagrams with vendor branding.”
- Bad memory: the full PowerPoint deck itself
- Good memory: “This repo always runs `pnpm db:push` before MCP deploy.”
- Bad memory: the raw migration SQL file