Knowledge, memory, and human control overview

Venture Brain

Brain is the venture knowledge surface. It stores structured knowledge and memory produced or used by agents. Users can browse entries, inspect details, search and filter the knowledge set, and review how the venture's operating context evolves.

Knowledge may include facts, decisions, lessons, research, and workflow-derived context. Correct source information when it changes; stale memory can influence later agent work.

Brain is scoped by organization and venture. Workflows mount or retrieve only the knowledge and resource contexts authorized for that run. Retrieval is context, not a command: the workflow should still treat the canonical repository, provider, strategy record, or project-management item as authoritative.

For observations, versioning, schedules, thresholds, freezing, models, analytics, and synthesis cost, see Brain and synthesis.

Memory

Agents can use persistent memory primitives to retain useful information across work. Memory is scoped and authorization-checked. It is not a replacement for the canonical strategy, repository, or project-management system.

Review important memory against its canonical source. Correct the source first, then record the correction so later synthesis can incorporate it.

Escalations

CXO agents create durable escalation records when an off-platform blocker needs CEO or human help. Pending actions expose these records in the product.

An escalation may ask for:

• clarification or missing context;
• approval of a consequential action;
• a selection between alternatives;
• review of a workflow output;
• operational intervention after repeated failure.

Resolve escalation records from the venture Escalations surface. The response becomes a high-importance observation for later agent use.

An escalation record is not automatically a signal to a waiting workflow. Workflow-specific approval and input controls continue their associated run; generic escalation resolution does not guarantee that behavior.

For categories, urgency, ownership, structured responses, retirement, and 14-day auto-expiry, see Escalations and human control.

Approval controls

There is no single universal review inbox. Each workflow exposes its own named approval steps — for example task approval after scoping, plan selection, discovery approval, and elaboration review.

Use the workflow's primary detail or pipeline view for its available approval actions. The sidebar pending-actions badge is a counter, not an inbox: it breaks down open escalations, discovery runs awaiting approval, and developer tasks waiting for input, but each item is still resolved on its own workflow surface.

Agent actions use contextual permissions and guardrails. See Agent tool access (MCP).