bicameral-context-sentry

Reconcile knowledge graph context and surface targeted questions before ingestion.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/BicameralAI/bicameral-mcp --skill bicameral-context-sentry
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bicameral-context-sentry
Source: https://github.com/BicameralAI/bicameral-mcp/tree/main/.claude/skills/bicameral-context-sentry
Command: npx skills add https://github.com/BicameralAI/bicameral-mcp --skill bicameral-context-sentry

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The context sentry provides knowledge graph reconciliation and HITL probing to ensure new decisions are grounded in existing context before flowing into the Bicameral pipeline. It derives search probes, evaluates relationships, and surfaces targeted questions when ambiguities cannot be resolved automatically.

Core Features & Use Cases

  • Graph reconciliation: searches the knowledge graph to relate incoming material to existing context and returns a structured reconciliation report with matches, conflicts, and context signals.
  • User probing: when ambiguities are detected, it asks targeted questions and collects answers before handing control back to the calling flow.
  • Flow integration: designed to be invoked by bicameral-ingest, bicameral-preflight, and bicameral-capture-corrections to maintain alignment across the decision lifecycle.

Quick Start

Run bicameral-context-sentry on a new decision batch to reconcile context and surface any required questions before ingestion.

Frequently Asked Questions about bicameral-context-sentry

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

FAQPage Schema
How do I reconcile new decisions with existing knowledge graph context before ingestion?

Knowledge graph reconciliation searches existing context to relate incoming decisions, returning a structured report with matches, conflicts, and context signals. It ensures new decisions are grounded in established context before flowing into the pipeline.

What is human-in-the-loop probing for resolving ambiguities in a knowledge graph?

Human-in-the-loop probing generates targeted questions when graph reconciliation detects ambiguities that cannot be resolved automatically. It collects user answers through Phase 1 and Phase 2 protocols before handing control back to the calling flow.

How do I ensure alignment between product decisions and code when naming new concepts?

To ensure alignment, the context sentry evaluates relationships in the knowledge graph and surfaces targeted questions when new concepts need naming relative to existing context. This grounds decisions in established context before ingestion.

Can I use graph search to detect conflicts between incoming decisions and existing context?

Yes, graph search is used to relate incoming material to existing context and returns a structured reconciliation report highlighting matches, conflicts, and context signals. This identifies misalignments before new decisions enter the pipeline.

When should I use human-in-the-loop probing versus automatic graph reconciliation for decision management?

Use automatic graph reconciliation first to search existing context and evaluate relationships. Apply human-in-the-loop probing only when ambiguities are detected that cannot be resolved automatically, queuing resolutions for user review.

What are the limitations of automatic context reconciliation for decision alignment?

Automatic context reconciliation cannot resolve all ambiguities between new decisions and existing context. When relationships cannot be evaluated automatically, it must surface targeted questions and queue resolutions for human review before proceeding.