IntentForge has reached a new milestone: it can now generate and validate more complex Python application shapes under deterministic Patch VM control, including Level 5 ACB profiles.
The key achievement is that we pushed the system beyond cautious incremental growth. Instead of only moving from simple apps to slightly less simple apps, we tested whether the existing foundation could support a much richer target. It could.
The current harness can now work with multi-artifact Python applications that include application modules, CLI/API-style interfaces, SQLite-backed persistence, JSON/CSV fixtures, contracts, tests, documentation, quality gates, generated-code inspection, and public-safe evidence. It can also expose live run events and file diffs so a future TUI or API consumer can show what is changing while the harness is working.
The biggest lesson is architectural: the local model does not need broader authority to create more complex software. It needs sharper targets. IntentForge keeps the model constrained to structured coding intent while the harness owns validation, application, verification, scoring, and evidence.
We also learned that the system was more capable than our development pace assumed. Jumping from lower complexity targets to Level 5 showed that the deterministic foundation was already strong enough to support richer app profiles, as long as the target included exact examples, clear file roles, contracts, tests, and quality gates.