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.
mdr add cdeust/zetetic-team-subagents/boundary-design@git:20260805.e8cc65emdr add cdeust/zetetic-team-subagents/boundary-design@sha256:9599ef0e6a74c8fb[](https://markdownregistry.com/a/art_ci6khozquuyjjace)
0 badge views in 30 days
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260805.e8cc65e latest | 2026-08-05 | e8cc65e | 3,090 B | A | view · diff |
| git:20260722.b89f9c1 | 2026-07-22 | b89f9c1 | 3,064 B | A | view |
cdeust/zetetic-team-subagents · 7 stars · license MIT · pushed 2026-09-05 · branch main
GET https://markdownregistry.com/api/v1/artifacts/art_ci6khozquuyjjace GET https://markdownregistry.com/api/v1/resolve?ref=cdeust/zetetic-team-subagents/boundary-design GET https://markdownregistry.com/api/v1/blob/9599ef0e6a74c8fb974c376d533c0d7eebee0ae68f1fa3c3456ba91f002471c1