3in3.dev is where I build and share systems for cooperation, commitment, and software delivery — helping client–vendor teams align before misalignment becomes expensive.
A connected set of systems that span cooperation, commitments, and delivery.
A way to look at teams as human cooperation systems – not just roles, tickets, and ceremonies. HCS helps you notice conditions like trust, safety, clarity, and alignment, and translate them into concrete actions.
A system for making commitments explicit, testable, and survivable in real projects. CDS helps teams design agreements around scope, risk, change, and responsibility before they harden into contracts, plans, or unspoken expectations.
A software delivery framework for client–vendor work where products, teams, and contracts must align. 3SF connects engagement, delivery, and value so you can see where projects really drift.
Analytical work that informs and stress-tests the delivery systems.
Tri-Contour Dynamics (TC). An analytical model for understanding how systems allocate constrained resources across competing structural demands. Published on Zenodo with a DOI. Includes macroeconomic case diagnostics and stress-test experiments.
System Design Lens (SDL). A design lens for reasoning about systems before they solidify into frameworks or tools — boundaries, assumptions, failure modes, and legitimacy.
CLRF, EAH, DPPL, and other tools across relationships, estimation, and product practices. Some are live, others in the lab.
Most software projects don’t fail because people lack frameworks or tools. They fail when cooperation breaks before code is written: discovery and delivery drift apart, vendors and clients optimize for different realities, and nobody has a shared view of what’s really happening.
HCS, CDS, and 3SF grew out of years inside client–vendor projects, trying to make those invisible dynamics visible and actionable.
3in3.dev is the place where I publish these systems, test them in real work, and keep them evolving.