docs: record D29 (modular monolith with agent-ownable module boundaries) #255

Merged
pdurlej merged 1 commit from claude/decisions-d29-modular-monolith into main 2026-06-26 13:21:16 +02:00
Collaborator

Records the 2026-06-26 operator decision on architecture shape, as a docs-only decisions.md change (summary-table row 29 + full ## D29 section).

What D29 settles

  • Patchwarden stays a modular monolith — one stdlib-only package, many bounded modules, not microservices (rejected as over-engineering for a stdlib-only single-operator dogfood tool, consistent with D27/#235).
  • New boundary criterion: boundaries must be crisp enough that a dedicated per-module agent can own + periodically health-check each module in isolation. Context-economy is a first-class boundary test: "can one agent own this module without loading half the repo?"
  • Aggregation god-files are debt: cli.py (~4k) and operator_status.py (~1.9k) grow O(modules) via inline wiring → invert to per-module registration (tracked in #254).
  • Sequencing discipline: record direction + de-godfile incrementally now; spin up the per-module-agent fleet only after boundaries are crisp and the single loop + live-lap are proven (no substrate-before-proof).

Boundary / floor

Docs-only. No code, no floor change (D20/D24/D26 untouched), no new capability, no new dependency. Companion implementation issue: #254. Operator may adjust the framing before merge — this captures the chat intent faithfully.

Vistula

  • Value: docs
  • Effort: small
  • Lead time: same-day
Records the 2026-06-26 operator decision on architecture shape, as a docs-only `decisions.md` change (summary-table row 29 + full `## D29` section). ## What D29 settles - **Patchwarden stays a modular monolith** — one stdlib-only package, many bounded modules, **not** microservices (rejected as over-engineering for a stdlib-only single-operator dogfood tool, consistent with D27/#235). - **New boundary criterion:** boundaries must be crisp enough that a **dedicated per-module agent** can own + periodically health-check each module *in isolation*. **Context-economy is a first-class boundary test:** *"can one agent own this module without loading half the repo?"* - **Aggregation god-files are debt:** `cli.py` (~4k) and `operator_status.py` (~1.9k) grow O(modules) via inline wiring → invert to per-module registration (tracked in #254). - **Sequencing discipline:** record direction + de-godfile incrementally now; spin up the per-module-agent fleet only after boundaries are crisp **and** the single loop + live-lap are proven (no substrate-before-proof). ## Boundary / floor Docs-only. No code, no floor change (D20/D24/D26 untouched), no new capability, no new dependency. Companion implementation issue: #254. Operator may adjust the framing before merge — this captures the chat intent faithfully. ## Vistula - Value: docs - Effort: small - Lead time: same-day
docs: record D29 (modular monolith with agent-ownable module boundaries)
All checks were successful
fallow-py / fallow-py-advisory (pull_request) Successful in 17s
status-drift / status-drift (pull_request) Successful in 13s
patchwarden-contract-pr / contract-pr (pull_request) Successful in 15s
161a8e40c8
pdurlej referenced this pull request from a commit 2026-06-26 13:21:16 +02:00
Sign in to join this conversation.
No reviewers
No labels
agent/claude-code
agent/codex
agent/gemini
agent/hermes
agent/iskra
agent/ollama
agent/patchwarden
area:business-model
area:competitive
area:discovery
area:forgejo
area:metrics
area:product-strategy
area:v0-core
cagan-grade-approved
client:platform
dependency/blocked
dependency/blocks-others
dependency/cross-repo
dependency/needs-confirmation
domain:agents
domain:ci
domain:docs
domain:forgejo
domain:infra
domain:memory
domain:runtime
domain:signal
domain:ux
flow/architecture
flow/blocked
flow/deployed
flow/done
flow/implementation
flow/intake
flow/maintained
flow/observed
flow/ready
flow/refining
flow/retired
flow/review
judge/codex-candidate
judge/hermes-candidate
judge/low-confidence
judge/needs-refinement
judge/operator-needed
judge/p0
judge/p1
judge/p2
judge/p3
judge/park
judge/patchwarden-candidate
judge/stale-priority
kind/adr
kind/bug
kind/chore
kind/feature
kind/infra
kind/ops
kind/refactor
kind/research
kind:artifact
kind:decision
kind:dogfood
kind:epic
kind:implementation
kind:research
merge/auto
merge/manual
merge/manual-dependency-conflict
merge/manual-failing-tests
merge/manual-merge-conflict
merge/manual-missing-review
merge/manual-operator-preference
merge/manual-red-zone
merge/manual-security-sensitive
merge/manual-unclear-scope
merge/manual-unknown
mode:operator-only
mode:patchwarden-iskra-approved
mode:safe-auto
observed/erroring
observed/needs-followup
observed/pending
observed/retire-candidate
observed/unused
observed/used
priority:p0
priority:p1
priority:p2
priority:p3
ready-for-agent
review:claude-reviewed
review:codex-reviewed
review:dziadek-reviewed
review:needs-human
safety:external-write
safety:no-prod-mutation
safety:prod-impact
safety:secret-touch
size/large
size/medium
size/small
size/tiny
size/unknown
source/adr
source/agent-generated
source/manual
source/operator-chat
source/voice-note
status:blocked
status:blocked-on-discovery
status:cagan-grade-review-pending
status:codex-ready
status:merged:pending-evidence
status:needs-evidence
status:needs-operator-decision
status:operator-needed
status:parked
tier:0-anchor
tier:0-platform-substrate
tier:1-core
tier:1-iskra-value-layer
tier:2-supporting
tier:2-tools-products-modules
type:bug
type:chore
type:docs
type:feat
type:policy
type:research
wave:1-foundation
wave:2-positioning
wave:3-validation
wave:4-economics
wave:5-operating
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
pdurlej/patchwarden!255
No description provided.