When should I use the /bound command?

Use it when starting a new complex task where you want to explicitly set the level of autonomy Claude has over different project areas or when ownership is unclear.

What is the Horismos protocol?

Horismos is a protocol that defines epistemic boundaries, ensuring both the user and the AI know who is responsible for specific decisions before a task begins.

How does this differ from simple task instructions?

Unlike static instructions, Horismos dynamically probes for undefined domains and creates a BoundaryMap that adapts to the specific context and complexity of the current task.

How does Horismos interact with other protocols?

Horismos typically follows goal-setting (Telos) and provides a boundary framework that downstream protocols like Aitesis use to focus their context gathering.

What is a BoundaryMap?

A BoundaryMap is a classification directory that signals to Claude which domains require user input, which need AI proposals, and which are safe for AI autonomous action.

Horismos: Decision Boundary Manager

Name: Horismos: Decision Boundary Manager
Author: jongwony

byjongwony

•

Productivity & Workflow

Defines clear ownership boundaries for decisions to establish whether the user provides input, the AI proposes options, or the AI acts autonomously.

Horismos is a specialized epistemic protocol for Claude Code designed to eliminate ambiguity in human-AI collaboration by explicitly defining decision-making responsibility. By generating a structured BoundaryMap, it classifies project domains into specific ownership categories—User-Supplied, AI-Proposes, or AI-Autonomous—ensuring that Claude neither oversteps its authority nor stalls due to lack of direction. This skill is essential for maintaining project integrity and user control during complex development tasks where the lines of responsibility might otherwise be blurred.

Key Features

01Classifies domains into User-Supplied, AI-Proposes, or AI-Autonomous categories

0288 GitHub stars

03Generates a comprehensive BoundaryMap to track and enforce epistemic ownership

04Scans codebases and configurations for boundary signals to enrich decision context

05Ensures 'Definition over Assumption' by resolving ownership before execution proceeds

06Proactively identifies undefined decision domains within any given task scope

Use Cases

01Resolving delegation uncertainty during multi-step refactoring or system migrations

02Defining collaboration levels when onboarding Claude to a large or unfamiliar codebase

03Setting clear decision boundaries at the start of complex architectural implementations

Key Features

01Classifies domains into User-Supplied, AI-Proposes, or AI-Autonomous categories

0288 GitHub stars

03Generates a comprehensive BoundaryMap to track and enforce epistemic ownership

04Scans codebases and configurations for boundary signals to enrich decision context

05Ensures 'Definition over Assumption' by resolving ownership before execution proceeds

06Proactively identifies undefined decision domains within any given task scope

Use Cases

01Resolving delegation uncertainty during multi-step refactoring or system migrations

02Defining collaboration levels when onboarding Claude to a large or unfamiliar codebase

03Setting clear decision boundaries at the start of complex architectural implementations