01
What changed
In the last week of July we focused on structure rather than feature additions. We reviewed provider contracts, the Desktop boundary, MCP, operations, and LiteLLM·vLLM topologies to ensure orchestration control remains with OpenMake.
- Clarified provider and gateway contracts.
- Reviewed the boundary between Desktop and MCP.
- Defined a least-privilege deployment approach for LiteLLM·vLLM.
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.
证据来源
OpenMake