skills.rest
BicameralAI
BicameralAIOFFICIAL
Explore all skills by this author →
GitHub

bicameral-resolve-collision

Resolve decision collisions and context-for signals in bicameral.ingest.

Updated Aug 23, 2026
Search Tags:#collision#human-in-the-loop#ingest#ratification#decision-management#context-for
One-click install
npx skills add https://github.com/BicameralAI/bicameral-mcp --skill bicameral-resolve-collision
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bicameral-resolve-collision
Source: https://github.com/BicameralAI/bicameral-mcp/tree/main/.claude/skills/bicameral-resolve-collision
Command: npx skills add https://github.com/BicameralAI/bicameral-mcp --skill bicameral-resolve-collision

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ingest and decision-logging systems can yield overlapping decisions or pending context-for links. This Skill provides a structured workflow to resolve collisions (supersede vs keep_both) and manage context-for (confirmed vs rejected) to maintain a clean decision ledger.

Core Features & Use Cases

  • Collision resolution: choose how a new decision relates to an existing one, ensuring the decision graph remains accurate.
  • Context-for linking: attach new spans to existing decisions with clear confirmation or rejection, enabling smoother ratification.
  • Recovery and governance: supports recovery from session termination and prepares decisions for ratification when context is resolved.

Quick Start

Resolve the latest collision or context-for suggestion by calling bicameral.resolve_collision with the new and old decision IDs.

Frequently Asked Questions about bicameral-resolve-collision

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I resolve ingest collisions when overlapping decisions occur?▼

Resolve ingest collisions by applying supersede or keep_both modes to update decision statuses and maintain a consistent decision ledger.

What is the best way to handle supersession candidates during data ingest?▼

Handle supersession candidates by evaluating new decisions against existing ones and selecting a collision mode to supersede or retain both entries.

How do I confirm or reject context-for links during decision ingestion?▼

Confirm or reject context-for links by processing context_for_candidates during ingest, attaching new spans to existing decisions to enable smoother ratification.

How do I recover from a session drop with unresolved decision collisions?▼

Recover from session termination using preflight recovery workflows that identify and resolve unresolved collisions and pending context-for links.

Can I keep both decisions instead of superseding an existing one?▼

Use the keep_both collision mode to retain an existing decision alongside the new one, ensuring the decision graph remains accurate without losing data.

Related Skills

Explore More Software Engineering Skills→
ming1zhou88ming1zhou88
3

minemap-collision-and-bounding

Implement BVH-based collision detection and geometric intersection tests for MineMap scenes.

Community
Advanced
ronniegeraghtyronniegeraghty
3

history-hygiene

Records final confirmed outcomes to history.md and updates entries on decision reversals.

Community
Intermediate
abdullahhqaiserabdullahhqaiser

langgraph-human-in-the-loop

Manage human-in-the-loop decision points in LangGraph workflows with interrupt and resume.

Community
Advanced
joyce820309joyce820309

autoplan

Automate sequential CEO, design, engineering, and DX reviews using six decision principles.

Community
Advanced