Phase 2 — Rules server, renderers, session gating #4

New Issue

wtclaude · 2026-08-08T19:36:15Z

wtclaude commented

2026-08-08 19:36:15 +00:00

Size: large · Depends on: Phase 1

The core thesis of the project.

Scope

Canonical schema v1 with schema_version and JSON Schema validation: guardrails, patterns, provenance, agent profiles, permissions
Storage and full CRUD admin API
get_rules(project_id, agent_type) plus the gate — any other tool call before it returns a structured error naming the required call
CLAUDE.md and AGENTS.md renderers under golden-file tests
Agent-proposal tools (propose_guardrail, add_pattern) writing to an approval queue; nothing auto-applies

Exit criterion

One edit in Bridle demonstrably changes behavior in a live Claude Code session and a live Codex session; a session that skips get_rules cannot use any tool.

References

ADR-0005 (get_rules + session gating), ADR-0006 (full-document delivery), ADR-0012 (v1 renderer targets)

Review notes

Renderer correctness is this phase's actual deliverable — golden-file coverage is not optional
The gate's error message is product surface: it must be unambiguous enough that an agent recovers on the first try
Structure the renderer so a dialect (same base format, different phrasing verbosity) is a cheap addition rather than a fork — Kimi/DeepSeek land post-1.0
Rules are delivered in full; tool schemas are a separate budget and are filtered per agent in phase 3

**Size:** large · **Depends on:** Phase 1 The core thesis of the project. ## Scope - Canonical schema v1 with `schema_version` and JSON Schema validation: guardrails, patterns, provenance, agent profiles, permissions - Storage and full CRUD admin API - `get_rules(project_id, agent_type)` **plus the gate** — any other tool call before it returns a structured error naming the required call - `CLAUDE.md` and `AGENTS.md` renderers under golden-file tests - Agent-proposal tools (`propose_guardrail`, `add_pattern`) writing to an approval queue; nothing auto-applies ## Exit criterion One edit in Bridle demonstrably changes behavior in a live Claude Code session **and** a live Codex session; a session that skips `get_rules` cannot use any tool. ## References ADR-0005 (get_rules + session gating), ADR-0006 (full-document delivery), ADR-0012 (v1 renderer targets) ## Review notes - Renderer correctness is this phase's actual deliverable — golden-file coverage is not optional - The gate's error message is product surface: it must be unambiguous enough that an agent recovers on the first try - Structure the renderer so a dialect (same base format, different phrasing verbosity) is a cheap addition rather than a fork — Kimi/DeepSeek land post-1.0 - Rules are delivered in full; **tool schemas** are a separate budget and are filtered per agent in phase 3

wtclaude added this to the v1.0 — Agentic Bridle milestone 2026-08-08 19:36:15 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: whitlocktech/Agentic-Bridle#4