Project Intelligence inputs
Project Intelligence keeps source truth in context, carries active work through workflow continuity, and stores only durable outcomes in reviewed memory. Snipara separates those inputs so agents stop mixing source truth with recalled learnings.
Rule of thumb
Source context first. Workflow continuity second. Reviewed memory only for durable outcomes.
Quick split
| You need to know... | Use | Why |
|---|---|---|
| What does this RFP, spec, PDF, or client doc say? | snipara_context_query or snipara_load_document | Those are source documents and current truth. |
| What are the team standards or reusable business playbooks? | snipara_shared_context | Shared collections are still document context, not memory. |
| What did we decide last week about pricing, UX, or architecture? | snipara_recall | That is durable memory, not a raw document lookup. |
| What preferences or learnings should follow the next session? | snipara_session_memories / session-bootstrap | That restores durable memory state and optional short carryover. |
| What should become reusable memory after this task? | snipara_end_of_task_commit / task-commit | That persists only durable outcomes instead of whole transcripts. |
Context surfaces
In the dashboard, open Projects, select a project, then open its Context tab. That tab contains project files, linked Shared Context, session context, Index Health, and Search Analytics. The legacy workspace-context URL redirects to Projects.
snipara_context_queryfor ranked document retrieval across project docs, parsed business files, and linked context.snipara_shared_contextfor project-linked standards, best practices, and business playbooks.snipara_load_documentwhen you already know the path and need exact source text.snipara_code_*tools for structural code truth that should not be treated as generic document search.
The lean Hosted MCP manifest does not advertise every specialist tool. Use snipara_help for routed guidance or an expanded Companion surface when a tool such as snipara_shared_context or snipara_load_document is not in the client's current tools/list response.
Memory surfaces
snipara_recallfor past decisions, preferences, validated learnings, and scoped memory questions.snipara_session_memoriesfor session bootstrap.snipara_end_of_task_commitfor durable outcomes after work is complete.snipara_rememberorsnipara_remember_bulkonly when you are explicitly storing a durable memory, not uploading source documents.
Default agent workflow
- Start with context retrieval.
- Pull shared standards only when the task needs them.
- Recall memory only for decisions, learnings, preferences, or carryover.
- Do the work.
- Commit only durable outcomes back into memory.
Anti-patterns
- Do not use memory as a substitute for reading a spec, PDF, or client file.
- Do not upload whole source documents into memory.
- Do not treat shared context collections as memory; they are still documents.
- Do not persist noisy task transcripts when a compact task summary is enough.