OpenMake
01
What changed
The second July week combined implementation with deep inspection. MCP catalog additions, agent-task design, self-learning measurements, frontend audits, and interactive log tooling exposed both progress and unresolved failures.
- Added Kakao and Notion MCP catalog work.
- Reviewed agent-task and self-learning designs.
- Recorded passing and failing test groups instead of flattening them into a success claim.
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