Workspace Context

Workspace Context separates reusable company knowledge from project-specific truth. Use it to keep business standards, code rules, examples, presentations, diagrams, and client work understandable for humans and reliable for LLMs.

Dashboard Navigation

The dashboard keeps context and administration separate. Use Workspace Context when you are managing what the AI can use. Use Settings when you are administering the workspace itself.

The Workspace Context page is intentionally sober. It uses four tabs: Business, Code, Collections, and Health. Business and Code are edited directly on the page. Collections, diagrams, and health remain linked from their own tab so the page does not duplicate project controls.

What Lives Where?

Business Context

Business Context is implemented as workspace shared collections. In Workspace Context > Business, teams get one clear action per preset: create the missing collection or open the existing one.

• Business Response Playbook: mandatory source-priority, reuse, confidentiality, RFP, and context-health rules that are attached automatically to business/client projects.
• Business Library: reusable company knowledge, methodology, approved examples, offer structure, and delivery standards.
• Offer Templates: base documents, proposal sections, assumptions, exclusions, and reusable commercial language.
• Company Presentations: pitch decks, PowerPoint-derived notes, positioning slides, and presentation scripts.
• Reference Diagrams: reusable schemas, visual conventions, topology patterns, and explanation notes.

These collections can be linked to projects when a client or internal mandate needs that reusable knowledge. They are not treated as the current truth for a client unless you place the relevant material in that client project.

When a business/client project is created from the dashboard or with snipara_create_client_project, Snipara automatically creates or reuses the workspace Business Response Playbook, adds its mandatory document if needed, and links it to the project. The playbook tells the LLM that current client files and the active RFP win over historical examples, while the Business Library and templates provide structure, methodology, and approved language.

MCP clients can manage the same model with snipara_list_business_collections, snipara_ensure_business_collection, snipara_upload_business_document, snipara_list_client_projects, and snipara_create_client_project. Current client files should still use snipara_upload_document or snipara_sync_documents so metadata and health signals remain attached to the project.

Code Context

Code Context stores simple workspace-wide technical rules that should be injected across projects automatically: coding standards, architecture defaults, repository conventions, review expectations, preferred APIs, and technical operating notes. In Workspace Context > Code, existing rules stay visible and the creation form only appears after selecting Add Rule. Use shared context collections inside individual projects when the rules need per-project token budgets, categories, or priority ordering.

Project Scopes

Projects are the operational scopes where current work happens. A project can represent a client, an internal initiative, a codebase, or research.

Workspace Context > Collections routes users to project Context tabs instead of recreating project controls. That keeps reusable workspace knowledge separate from project-scoped files, diagrams, collection links, memories, and query history.

The project UI follows that scope. Code projects show Codebase, Repo Docs, Technical Diagrams, and Attachments. Client or business projects show Client Context, Presentations, Diagrams, and Reference Material. Business Library remains a workspace-level reusable collection, not a lane inside a repository project.

Client-shaped projects also carry a business lifecycle. This keeps active client truth from being confused with past-client precedent or internal company work.

Business Project Lifecycle

How LLMs Should Use It

A well-scoped query can combine reusable business context with active project context. For example, an agent can reuse the diagram conventions from the company library, compare with a historical ACME delivery, and then adapt the answer to the active XYZ project.

Workspace Context
├── Business tab
│   ├── Business Response Playbook
│   ├── Business Library
│   ├── Offer Templates
│   ├── Company Presentations
│   └── Reference Diagrams
├── Code tab
│   └── Workspace-wide technical rules
├── Collections tab
│   └── Project Context tabs own collection links and visual context
├── Health tab
│   └── Freshness, parser quality, stale files, and reindex signals
└── Projects
    ├── Client projects
    ├── Internal projects
    ├── Code projects
    └── Research projects

Related Docs

• Business Context RFP workflow
• Shared Context Collections
• RFP workflow blog post
• Code Context agent workflow
• Index Health and Analytics
• GitHub Sync