Team Sync
Team Sync gives developers and coding agents a shared evidence brief for the same repository: which files are changing, where PR scopes overlap, which critical surfaces need proof, and what handoff context should survive between sessions.
Product boundary
V1 does not need a new package. The hosted app owns the shared brief, snipara-companion owns local workflow commands, and snipara-orchestrator stays Enterprise-only for proof gates and multi-agent execution.
The flow
Plan segmentation
Team should get the visible coordination value. Enterprise should get enforcement, audit, retention, org-scale controls, and proof automation.
| Capability | Team | Enterprise | Rationale |
|---|---|---|---|
| Team Sync Brief | Included | Included | Daily coordination should be evidence-based and visible in Team. |
| Companion start-work, handoff, resume, what-changed | Included | Included | Low-friction local workflow drives adoption. |
| Merge Readiness Signals | Preview / advisory | Included | Governance and org-scale proof create Enterprise value. |
| Required proof gates | Advisory only | Included | Enforcement affects compliance, audit, and release policy. |
| Audit retention and export | Limited | Included | Retention and evidence export are Enterprise buying signals. |
| snipara-orchestrator multi-agent proof | Not included | Included | The orchestrator is reserved for htasks, Snipara Sandbox evidence, proof, and policy. |
Package scope
Hosted app and API
Source of truth for briefs, entitlements, project state, and dashboard UI.
snipara-companion
Local developer commands for start-work, handoff, resume, and what-changed.
snipara-orchestrator
Enterprise proof gates, Snipara Sandbox evidence checks, htasks, and multi-agent policy.
New package
Avoid for V1. It would split ownership before the contract is stable.
Companion commands
The local command surface keeps developer intent and handoffs close to the repository while the hosted brief remains the team-wide view. When the workspace is configured with a project API key, the same commands also call the hosted Team Sync surfaces instead of stopping at local counters.
That means start-work fetches a hosted Start Work Brief, what-changed loads the hosted What Changed For Me surface, and resume can recover the latest hosted handoff plus checkpoint-aware session context.
Agents that do not use the companion CLI can fetch the same continuity bundle directly through hosted MCP with snipara_resume_context: latest handoff match, What Changed, active decisions, execution-memory, and an optional task-scoped work brief.
snipara-companion team-sync start-work --summary "Refactor auth middleware" --files apps/web/src/lib/auth/require-auth.tssnipara-companion team-sync handoff --summary "Moved project access check" --next "Run permissions tests before merge" --attention proofsnipara-companion team-sync what-changedsnipara-companion team-sync resumeWhat Changed For Me
What Changed For Me is a hosted return-to-work surface, not a local scoring fork. The backend composes branch, recent-file, and session context with decisions, stale assumptions, overlaps, failed PR packs and index jobs, document index health, code graph freshness, and recommended actions.
That keeps snipara-companion team-sync what-changed, the dashboard, and future API clients aligned on the same evidence instead of rebuilding partial scoring logic in each client.
When an agent needs one compact return-to-work payload instead of composing multiple surfaces manually, snipara_resume_context uses this hosted change summary as one component inside the larger continuity bundle.
Enterprise gates
Enterprise gates are where the perceived value should be concentrated. Auth, billing, database, deployment, MCP contract, and memory persistence changes can move from advisory warnings to required proof gates backed by snipara-orchestrator.
- Proof gates can require test evidence, htask completion, and Snipara Sandbox evidence checks.
- Merge readiness can retain who approved the gate and why.
- Audit export can package the timeline for internal review or compliance.