Engagements
Run the practice against your codebase, or alongside your team. Architectural authority stays with you. The work arrives as verified, recorded, reviewable steps.
Andrew T. Marcus—systems architect (MIT M.Arch). He developed the Ho System and has shipped more than ten production systems with it—including Kanyō, a computer-vision system running at Harvard, built without knowing how to code. He writes about human–AI collaboration at sageframe.substack.com.
Evidence, not adjectives
Kanyō—a production computer-vision system built by a non-developer in six weeks, monitoring falcon cameras at Harvard, still running. The supacode contribution—disciplined work inside someone else's repository: PR discipline, host-convention matching, and a wrong assumption corrected on the record rather than papered over. That last one is the point: the practice's answer to “what is it like when this touches our code” is a visible, honest record.
Two shapes
Brought to your codebase—the practice run against your real project, with you in the room. Or taught to your team—the discipline itself transferred: your environment encoded, your vocabulary built, your first walked together. Both share one front door.
What you receive
- The working record—the sidecar ho-process: every step, its plan, and its look-back.
- The environment encoding—CLAUDE.md, the verification stack, your conventions made explicit.
- Optionally, a tool layer that makes the practice's mechanics available to your agent sessions, installed and configured.
- The discipline itself, transferred to your sessions.
The line
The methodology is open—all of it is on this site. The facilitation judgment is the engagement. That is the whole paywall, stated plainly.
One contact action. No pricing, no packages, no funnel—the front door to a practice should read like the practice.