docs(rules): log a bottleneck as a Problem and design it out

[zolotokrylin]

What this enables

Teams can turn a standing single-person dependency into something the org actually removes, instead of scaling by adding people around the bottleneck.

Change

Adds DEV-155 to the Contribution model band: when a step repeatedly depends on one person to proceed, name it as a barrier (DEV-150), open it as a Problem (DEV-160), and design the dependency out with a framework, delegated bounds, or automation. Scale by building the system, not by absorbing load with more people.

Indexed under "1. Contribution model" in the rules README.

Applied example

The partnerships repo applies this by revising REF-410 so business-development partners close commission within a framework Vadim owns, rather than routing every deal through him.

• https://github.com/holdex/partnerships/pull/36

Summary by CodeRabbit

• Documentation
  • Added rule DEV-155 for documenting recurring single-person bottlenecks as formal Problems.
  • Defined guidance for removing these dependencies through shared frameworks, delegated ownership, or automation.
  • Added DEV-155 to the contribution model rule index.
  • Included acceptance criteria to ensure dependencies are fully removed rather than merely reduced.

[holdex]

Time Submission Status

Member	#	Time	Running Total	Status	Last Update
zolotokrylin			9min	✅ Submitted	Jul 16, 2026, 11:58 AM

---

Submit or update total time with:

@holdex pr submit-time 2h

Add time on top of previous submission with:

@holdex pr add-time 1h30m

See available commands to help comply with our Guidelines.

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: b7b03ecb-04f3-437d-b0b1-99f91fcb40e4

📥 Commits

Reviewing files that changed from the base of the PR and between 6556af8 and 4e149a8.

📒 Files selected for processing (2)

• docs/rules/DEV-155.md
• docs/rules/README.md

---

Walkthrough

Adds the DEV-155 documentation rule for converting recurring single-person dependencies into formal Problems and Solutions, then registers it in the contribution-model rules index.

Changes

DEV-155 rule

Layer / File(s)	Summary
Define and register DEV-155 docs/rules/DEV-155.md, docs/rules/README.md	Defines the bottleneck Problem workflow and acceptance criteria, then adds DEV-155 to the contribution-model rule list.

Estimated code review effort: 1 (Trivial) | ~3 minutes

Possibly related PRs

• holdex/developers#122: Establishes the rules documentation structure extended by this change.
• holdex/developers#123: Introduces the Problem workflow referenced by DEV-155.
• holdex/developers#124: Establishes validation for rule documents and README rule registrations.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch claude/dev-log-bottleneck-as-problem

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[zolotokrylin]

@holdex pr submit-time 9m