auth-yes/.forum/poc-g2/BOUNDARIES.md

Generation 2 Constraints: Production-Grade Tooling, Physical Limits

The Proofs of Concept (PoCs) in this directory (forum/poc-g2/) are designed to prove the physical feasibility of the architecture using actual, production-ready tools.

1. No Faking: We are explicitly not faking or mocking tools "to save on repo bloat." If the architecture calls for Tree-sitter or Semgrep, these PoCs must demonstrate their execution using actual binaries or WASM payloads.
2. Physical File I/O: These scripts interact with the actual filesystem (e.g., tracking states via real JSON files, parsing real Markdown or YAML, dynamically creating physical temp Git repos) to prove constraints.
3. Architectural Validity: If a required tool is too heavy or fundamentally incompatible with the Local-First/Git-Native bounds (as proven in the Graveyard PoC), it must be flagged for architectural reevaluation. The ability to run the real tool locally is the core pass/fail criterion of Gen 2.