Canonical · L4 Primitive · Developer Lane·Shipped
Claude Code context governance
Claude Code-style work needs context governance, not just more context. Long-running coding sessions create lessons, corrections, and architectural decisions that should not disappear when the session ends.
Plain definition
Claude Code context governance is the application of capture → review → promote → hydrate to long-running Claude Code work, so lessons become durable instead of evaporating with the session.
Why it matters
Coding agents discover architectural rules, repeat mistakes, fix edge cases, and learn project constraints. If those lessons disappear with the session, the next run starts weaker than it should.
What it is not
- A Claude Code fork.
- An MCP server.
- A prompt template.
- An IDE plugin.
Where it appears in Ubiquity
Context Grapple Gun is the Prompted LLC tool for this developer lane.
Ladder context
Demand ladder
L1 Pain→L2 Contrast→L3 Category→L4 Primitive→L5 Branded
← Up the funnel
Token bloat vs. governed memoryDown the funnel →
Runtime governance for agentic developmentAdjacent transitions
Related terms
Frequently asked
- How can Claude Code retain project lessons?
- Through a governance lifecycle — capture, review, promote, hydrate — that distills lessons into durable guidance the next session inherits.
- What is context governance for Claude Code?
- Treating long-running coding work as a governance problem, not a context-size problem.
- What is CGG?
- Context Grapple Gun — the portable governance lifecycle that proves Ubiquity's grammar inside Claude Code.
- How does CGG relate to Ubiquity?
- CGG is complete without Ubiquity. When flat-file governance runs out, Ubiquity extends the same primitives into deeper substrate infrastructure.