delivery-gate

Topics in the source

• Delivery Gate — Mechanical Quality Gate for Claude Code
• What It Checks
• Why
• Install
• Learning Libraries
• Configuration
• Examples
• Limitations

A Stop hook that checks three things before Claude can finish a session, using only deterministic checks — file modification timestamps, disk usage, and regex patterns on the transcript text. No AI inference. This is distinct from reasoning gates (like self-audit): delivery-gate checks machine-verifiable facts; self-audit checks output quality across four reasoning dimensions. Together they form defense in depth: delivery-gate: "Was the learning library touched today? Is disk space safe?" self-audit: "Is the file content correct, complete, and honest?" This is the same pattern as CI pipeline gates — automated, deterministic checks that verify machine-readable facts rather than trusting self-reported status. | Check | Mechanism | On Hit | |-------|-----------|--------| | Rationalization patterns | Regex on transcript tail | Warning only (never blocks) | | Stale learning libraries | mtime on 5 configurable paths | Warning if some stale; Block on a complex task if >=3 stale OR growth-log stale | | Disk space =3 Edit/Write calls), >=3 learning libs stale OR growth-log specifically stale. If the project memory directory does not exist, the learning-library checks are skipped: the hook o

This is an excerpt. Refer to the complete source and its current requirements.