auth-yes/forum/poc-g1/BOUNDARIES.md
Tyler Gillispie 555c5eb384
feat(forum): add missing Gen 1 & Gen 2 PoCs with strict constraint enforcement (#69)
This commit implements the missing Proof of Concepts (PoCs) required by the `agent-forum-v4` architecture blueprint as identified in `CONCEPTS.md`.

Updates include:
- `execution_flywheel_poc.ts`: Implemented mock version (Gen 1) using in-memory state and physical version (Gen 2) utilizing actual file I/O tracking to prove state management bounds.
- `tool_sandbox_poc.ts`: Implemented mock version (Gen 1) yielding simulated telemetry and physical version (Gen 2) utilizing real production-grade tool invocations (Semgrep via CLI and Tree-sitter via WASM module).
- `git_hooks_poc.ts`: Implemented mock version (Gen 1) intercepting simulated events and physical version (Gen 2) configuring a physical Git temp directory executing native `.git/hooks/pre-commit` hooks.
- `BOUNDARIES.md`: Documented explicit technical boundaries in both `poc-g1` and `poc-g2` to enforce strict isolation vs production file-system operation.
- Fixed Deno Linting constraints across `poc-g2/` scripts.
- `CONCEPTS.md`: Status flags updated to .

Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com>
Co-authored-by: mrteye <1945243+mrteye@users.noreply.github.com>
2026-08-29 00:28:19 -07:00

831 B

Generation 1 Constraints: Mocked, Isolated, In-Memory

The Proofs of Concept (PoCs) in this directory (forum/poc-g1/) are bound by strict Generation 1 constraints:

  1. Isolation: They must have absolutely minimal effect on the broader repository.
  2. Mocked Data: They simulate interactions (e.g., via simple logic or static JSON returns) rather than executing heavy external binaries or writing to persistent disk.
  3. In-Memory State: They operate predominantly in memory, validating the mathematical and logical feasibility of the concepts (e.g., dependency traversal, state machine bounds, semantic match simulation) without requiring a complex production environment setup.

These scripts validate the theory and logic of the architectural blueprint before scaling up to physical implementation constraints.