Project Intelligence, without the icon wall.
Snipara is easier to understand when grouped by hierarchy: Project Intelligence First, Workflow Continuity second, and memory, MCP, Sandbox, automation, and code graph as supporting surfaces.
- Project Intelligence is the five-question model behind Snipara agent work: what changed, why, impact, next step, and safety.
- Code Context keeps workspace-wide engineering rules separate from project files, shared collections, project scopes, and health.
- Workflow Continuity is the mechanism: Start Work Brief, What Changed For Me, and PR/MR Answer Packs.
- snipara_context_query stays the default path for docs and narrative context.
- Code structure belongs to the code graph and the snipara_code_* tools.
- Context authority keeps source_url, commit_sha, freshness, confidence, validation state, and stale warnings visible.
- Team Sync turns parallel repository work into a shared brief with advisory Team evidence requests and enforceable Enterprise proof gates.
- Adaptive Work Routing can recommend cloud or local workers from provider-neutral requirements, then measure quality-adjusted accepted-outcome cost.
- Safe Parallel Coding adds hosted presence, expiring collaboration leases, heartbeat renewal, guard checks, Git hooks, and GitHub checks.
- Snipara Orchestrator is the Enterprise control plane for proof gates, drift checks, htasks, and explicit multi-agent coordination.
- PR/MR Answer Packs turn GitHub pull requests and GitLab merge requests into scoped context artifacts for Claude Code, GitHub Copilot, Codex, Cursor, and other AI coding clients.
- Supported PDF, DOCX, PPTX, SVG, and VSDX files now enter a deterministic binary parser lane instead of being ignored.
- Helvabase owns RFP, proposal, and client dossier workflows while Snipara stays focused on developer context.
- Shared context is project-aware, so one team can keep different rules and reference libraries per project.
- Memory is an input; Project Intelligence is the output.
- Full automation is optional; the simple path is still hosted MCP plus Project Intelligence retrieval.
Give the agent shared project state before it edits.
Use Project Intelligence to combine context, decisions, active work, impact, outcomes, and verification signals into the starting point for agent work.
Turn intelligence into execution only when the task needs it.
Snipara can stay Project Intelligence only, or extend into Snipara Sandbox, proof gates, and workflow execution when validation, automation, or multi-step work is worth the extra layer.
Make repository context visible inside code reviews.
Use the code graph for structural questions, let repository sync route docs, code, and supported binaries into the right lane, then publish PR/MR Answer Packs, Team Sync briefs, and collaboration guards so agents start from scoped repository cognition.