This is what a Principal Engineer’s codebase actually looks like — a live, unscripted walkthrough of iching.rocks. This post was generated with an assist from Claude, querying my self-hosted Engram MCP server against the live iching.rocks repository — itself a demonstration of the semantic-memory infrastructure described below. Nothing here is hypothetical; every snippet was pulled […]
Most people treat “AI-assisted development” as a speed story: more code, faster. The part nobody talks about is what fast actually costs you if nothing is checking the work — silent asymmetries, tests that lie, features that should never have shipped in the first place. Using my Continuum process, I just finished the iching.rocks MCP […]
Most MCP servers ship with a static bearer token. It’s one line in .mcp.json, it works on day one, and it’s the wrong answer the moment your server is anything other than a personal dev tool. Engram, the semantic memory layer behind my AI-native development workflow, started there too. A shared bearer header in .mcp.json, […]
When a user gets a paid reading on iching.rocks, the system needs to generate a comprehensive, multi-section I Ching interpretation. Not a single paragraph — a full document covering opening observations, hexagram judgments, changing line analyses, Ten Wings commentary, synthesis, and a conclusion. Each section requires its own carefully crafted prompt with injected domain data. […]