01
What changed
The final July week shifted from feature accumulation toward architecture. Provider contracts, desktop boundaries, MCP behavior, operations, and a LiteLLM and vLLM topology were reviewed to keep orchestration ownership inside OpenMake.
- Clarified provider and gateway contracts.
- Reviewed Desktop and MCP boundaries.
- Defined a least-privilege LiteLLM and vLLM deployment direction.
02
How this week was reconstructed
Both relevant Claude Code sessions and Git history were recovered for this period. Large delegated families were grouped only when their parent lineage was explicit.
We audited the available Claude Code main sessions, their proven child lineages, and the repository history. Session notes explain intent and investigation; Git remains the authority for code that actually landed.
03
Team identity and project roles
OpenMake Team is the community identity; openmake_llm is the software project; OpenMake is the product name. Non-developer maker riskpw leads openmake_llm through vibe coding, and professional developer rocky supports its development.
Source evidence
OpenMake