01
What changed
OpenMake started growing beyond basic chat. Skills, memory, schemas, upload security, MCP controls, and deeper testing established the components needed for an extensible AI workspace.
- Expanded skills and MCP management.
- Strengthened memory, schema, and upload boundaries.
- Added security checks and larger test batches.
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