decisions(0018): agentic-first systems fix root causes, not workarounds #283

Merged
pdurlej merged 1 commit from claude/adr-0018-agentic-first-no-tech-debt into main 2026-05-14 12:03:41 +02:00
Collaborator

Summary

Codifies operator's 2026-05-14 framing as formal governance ADR. Agentic-first platforms cannot carry tech debt the way human-operated ones can — context-compressed successor agents read carried debt as fire signals, panic, regress, drift. Compare Iskra/OpenCode false-Honcho-down history.

Why this matters

This is the meta-rule that justifies rejecting the watchdog-workaround for #260 (PR #282 dispatch). Without ADR-0018 written down, future cousins will re-litigate the workaround-vs-fix decision every time they encounter recurring red signals in agent-readable state. With ADR-0018, the rule is durable, lookup-able, and dispatch-citable.

What's in

  • decisions/0018-agentic-first-fix-root-causes.md (new ADR, ~170 lines):
    • Context: human-first vs agentic-first asymmetry
    • Decision rules (when fix mandatory; when workaround conditionally allowed)
    • Consequences (positive + negative)
    • Operational rules for dispatch authors, executors, reviewers, status authors, ADR authors
    • Case study: #260 runner pickup as concrete example
    • Boundary clause (what this ADR does NOT cover)
  • AGENTS.md § Conventions: new subsection between risk-tiers (ADR-0007) and size-classes
  • state/pan-herbatka-day1-checklist.md:
    • § don't-do list: new rule #6
    • § ADR map refreshed (0010, 0011, 0017 no longer drafts; 0018 added)

Tier

Full per ADR-0007 (new ADR). Operator merge only; no auto-merge.

Canary status

Not fired by me — this is pure governance prose, no runtime/CI/sacred-path impact. Operator may choose to fire 3+3 if desired before merge; I default to defer-to-operator for governance ADRs.

Refs #260 #142

## Summary Codifies operator's 2026-05-14 framing as formal governance ADR. Agentic-first platforms cannot carry tech debt the way human-operated ones can — context-compressed successor agents read carried debt as fire signals, panic, regress, drift. Compare Iskra/OpenCode false-Honcho-down history. ## Why this matters This is the meta-rule that justifies rejecting the watchdog-workaround for #260 (PR #282 dispatch). Without ADR-0018 written down, future cousins will re-litigate the workaround-vs-fix decision every time they encounter recurring red signals in agent-readable state. With ADR-0018, the rule is durable, lookup-able, and dispatch-citable. ## What's in - `decisions/0018-agentic-first-fix-root-causes.md` (new ADR, ~170 lines): - Context: human-first vs agentic-first asymmetry - Decision rules (when fix mandatory; when workaround conditionally allowed) - Consequences (positive + negative) - Operational rules for dispatch authors, executors, reviewers, status authors, ADR authors - Case study: #260 runner pickup as concrete example - Boundary clause (what this ADR does NOT cover) - `AGENTS.md` § Conventions: new subsection between risk-tiers (ADR-0007) and size-classes - `state/pan-herbatka-day1-checklist.md`: - § don't-do list: new rule #6 - § ADR map refreshed (0010, 0011, 0017 no longer drafts; 0018 added) ## Tier Full per ADR-0007 (new ADR). Operator merge only; no auto-merge. ## Canary status Not fired by me — this is pure governance prose, no runtime/CI/sacred-path impact. Operator may choose to fire 3+3 if desired before merge; I default to defer-to-operator for governance ADRs. Refs #260 #142
decisions(0018): agentic-first systems fix root causes, not workarounds
All checks were successful
base-is-main / guard (pull_request) Successful in 2s
canary-required / collect-diff (pull_request) Successful in 5s
canary-required / canary (pull_request) Successful in 13s
0cd1277308
New governance ADR codifying operator's 2026-05-14 framing: agentic-first
platforms cannot carry tech debt the way human-operated ones can.
Context-compressed successor agents read carried debt as fire signals,
panic, regress, drift. Compare Iskra/OpenCode false Honcho-down history.

Case study preserved: #260 runner pickup. Watchdog auto-restart works as
workaround (~150s pickup delay) but every future cousin reads the journal
as live fire. Proper RCA chosen instead (PR #282 dispatch).

ADR rules:
- Root-cause fixes mandatory when symptom is agent-readable
- Workarounds conditionally allowed only with: upstream-blocked cause +
  expiry condition + tech-debt-temporary issue + structurally-distinct
  signal from fire
- Dispatch authors: never include "accept workaround" as ranked outcome
- Executors: STOP and re-read § 0 if ranking "live with it" as primary

Cross-references added to:
- AGENTS.md § Conventions (between risk-tiers and size-classes)
- state/pan-herbatka-day1-checklist.md § don't-do list (rule #6) + ADR map

ADR map in checklist also refreshed to reflect actual state of 0010, 0011,
0017 (no longer drafts).

Tier: Full per ADR-0007 (new ADR). Operator merge only; no auto-merge.

Refs #260 #142 #142
Sign in to join this conversation.
No reviewers
No labels
W6d-automerge-calibration
agent/claude-code
agent/codex
agent/hermes
agent/iskra
agent/ollama
agent/patchwarden
automerge-candidate
class/security-sensitive
cutover-gate
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
iterating
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
large-impact
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
meta
mode:operator-only
mode:patchwarden-iskra-approved
mode:safe-auto
needs-operator-decision
needs-triage
not-ready
observed/erroring
observed/needs-followup
observed/pending
observed/retire-candidate
observed/unused
observed/used
operator-emotional
owner-attention
phase/02
phase/03
priority:p0
priority:p1
priority:p2
priority:p3
proposed
ready-for-agent
ready-for-operator
recovery
review:claude-reviewed
review:codex-reviewed
review:dziadek-reviewed
review:needs-human
risk/exposure
risk/process
risk/product
risk/runtime
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:codex-ready
status:merged:pending-evidence
status:needs-evidence
status:operator-needed
status:parked
tier/full
tier/lite
tier/stacked
tier:0-platform-substrate
tier:1-iskra-value-layer
tier:2-tools-products-modules
type:bug
type:chore
type:docs
type:feat
type:policy
type:research
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/platform!283
No description provided.