Department · Engineering & Product · schema_pack: 6 types
Your team already decided this. The next agent should know.
ADRs, conventions, and decisions delivered to Claude Code, Cursor, Codex, and Devin via MCP, with version, source, and inherited permission.
Scenario
How context circulates when ValorBrain is in the flow.
- 01
Claude Code closes the API standard definition in ADR-007; the decision-extractor logs the decision with its source and owner, pending human validation.
- 02
The next day, Cursor receives the current standard via context-surfacing, right as it builds the listing endpoint.
- 03
Nobody re-explains: the new code ships in line with the ADR, consistent across agents.
- 04
Codex finishes part of a refactor and leaves the webhook tests pending; the handoff-generator records the state and cites the module's known antipattern.
- 05
ValorBrain routes the handoff to Devin with the permissions inherited from whoever opened the task.
- 06
Devin picks up exactly where the previous agent stopped, with the source cited in context.
- 07
The nightly ingestion cross-checks INFRA.md against real hostnames, finds a divergence, and the curator-nudge routes it to sre/platform for review.
- 08
The next morning, session-bootstrap opens the day with what changed: a new decision, a drift under review, a pending handoff.
- 09
The drift gets resolved before it becomes a production incident.
Schema pack
Unit types that give structure to what's worth remembering in this area. Every record carries source, owner, version and validity.
schema_pack:types: - decision - bugfix - feature - refactor - discovery - antipatternNext step
Less starting over. More continuity
Bring a real project. In one conversation we map where context gets lost between the people and agents on your team, and where to start.