knowledge pathways
structured journeys through patterns and principles, aimed at specific outcomes.
patterns and principles are atoms. they live in kpp as a reference library — browseable, useful on their own.
a pathway is what happens when you sequence those atoms into a structured journey. which patterns to recognize, which principles to commit to, in what order, with what exercises, against what concrete artifact you walk away with. pathways are how you actually learn to do something — not by reading a glossary, but by working through a built sequence.
first pathways
four artifacts you can ship. each pathway is a structured journey — you walk in with curiosity, you walk out with a real, working thing. drawn from material we’ve operated, not theorized.
an autonomous outreach machine
land ops as case studyyou ship a working outreach machine — acquisition, mail, voice, qualification, all run by agents inside your own system. the playbook we developed at land ops, taught as a sequence against your own surface area.
a real-time financial baseline
onefi as substrateyou ship your version of the system we run our own books on. multi-entity bookkeeping, planner, outcomes — built against the spec, alongside it.
a business operating system
i as modelyou ship the orchestration files — plans, scenarios, outcomes, today.md — installed and exercised in your own repo. the meta-framework one operator runs across financials, ops, and growth.
an idea-to-production pipeline
the recipe-over-app stackyou ship a working idealog and gate stack — capture, triage, and autonomously ship features when the llm is the runtime and the recipe is the product.
how to take one
self-paced — read, work through exercises, ship the artifact. low friction, asynchronous, learn at your tempo.
cohort — small group, fixed window, shared deadlines and critique. higher accountability and momentum.
mentored — direct work alongside someone who’s built it. highest density. limited slots.
get notified when the first pathway opens