Boundary Design

Draw the line where it costs least. Use for build-vs-buy calls, "where does this module/team/service boundary belong?", APIs and abstractions forcing users into implementation vocabulary, tools that should augment rather than automate, hardcoded decisions that belong at runtime, or information nobody can find.

cdeust Updated 8 repo stars
Zetetic reasoning for AI agents: sourced evidence, explicit uncertainty, one epistemic standard

File contents

cdeust/zetetic-team-subagents commit 05325f6c02

Frequently asked questions

npx get-skill add cdeust/boundary-design