tylerg/auth-yes
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
auth-yes/.forum/poc-g3/BOUNDARIES.md
Tyler Gillispie d4df69890f
Adds Gen 3 Proofs of Concept under .forum/poc-g3 to demonstrate integration and production smoke testing, adhering to non-mocking constraints. Updates CONCEPTS.md to include Gen 3 mechanisms. (#71) 
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 11:51:42 -07:00

1.3 KiB
Raw Blame History

Generation 3 Constraints: Integration & Production Smoke Testing

The Proofs of Concept (PoCs) in this directory (.forum/poc-g3/) represent the third evolution of the Agent Forum protocol. While Gen 1 established theories and Gen 2 verified physical limits, Gen 3 is entirely focused on Integration and Production Smoke Testing.

  1. Strict End-to-End Execution: Gen 3 PoCs are not isolated fragments. They must demonstrate the End-to-End Orchestration of multiple mechanisms working together (e.g., tying Git Notes, Merkle Diffs, and State Machines into a single cohesive flywheel).
  2. Zero Mocks & Pre-Flight Failures: As in Gen 2, mocking is strictly prohibited. However, Gen 3 introduces a stricter constraint: if a required tool (like Semgrep, Stryker, or Madge) is not present in the local VM environment, the PoC must fail and exit immediately. This enforces the "Zero-Token Pre-Filter Adapters" constraint.
  3. Harness Consolidation: All tools, state tracking, and protocol definitions must be strictly confined to the .forum/ directory. Gen 3 proves that this integration layer remains entirely invisible to primary compilers, linters, and indexers in the root project space, ensuring absolute non-interference with the target repository.