Handbook

Known limitations (alpha)

This list is intentionally candid. It is not exhaustive; it highlights boundaries that often surprise new adopters.

Sprint / product scope

Narrow patch units — create_patch_units emits rule-based plans; it does not understand full-repository refactors. Treat output as a starting point for review.
Ambiguous architecture — The library does not resolve underspecified product or system design; contracts and human intent must be explicit.
Granite / live environments — Integration tests may use optional Granite or gateway configuration (FORGE_LCDL_GRANITE_ENV_FILE, etc.). That path is not a guarantee of parity with every deployment.
MCP — Prefer local MCP tools and least-privilege credentials. This repo documents patterns; it does not operate a hosted MCP service.
Security-sensitive edits — Changes touching auth, crypto, sandbox boundaries, or secret handling require human review regardless of model tier or LCDL hints.