Solutions · Team Context CurationImprove your context on every interaction
Multiplayer by design: Every chat surfaces issues in your context. An agent drafts the fix, your team bumps up what matters, and data context admins approve it once evals pass.
SignalPilot · Context Factory
Agent chatMarcus · RevOps
What was churn last quarter?
churn· not in your context yet
No churn definition yet, so I drafted one for your data team.
Add a churn definitionIn review
0
Data team reviewContext as code
Define churnIn review
semantic-models/customer.yml+4
Approve and merge
Approved and merged by Hannah, Data
How it runs
Ingest, surface, agree, merge.
- 01IngestWe read your BI tools, dbt, and agent traces.
- 02SurfaceAgents flag missing or conflicting terms.
- 03AgreeTeammates vote in Slack, Claude Cowork, or Codex.
- 04MergeAdmins approve; evals keep it accurate.
How each fix is drafted and checked: see Context & Evals →
Why not Claude Code or Codex
Single-player agents make alignment impossible.
Claude Code and Codex make one person faster. Alignment takes a multiplayer system.
Single-player agent
Claude Code, Codex
- Serves one person
- Definitions in a personal file
- Conflicts go unnoticed
SignalPilot
Multiplayer, for the whole company
- Serves the whole team
- Shared, reviewed context in your repo
- Conflicts flagged and settled in chat
Bring your dbt project. Keep every term agreed.
Open source · Apache 2.0 · GitHub · Slack