Development record
2026-09-30 — Pending the person's ruling CL1, a promoted inbox report files the machine value: outside text never becomes a drain-eligible remedy without a person naming it (fix round of lane remedyRequired, autonomous run A, closing the review's trust finding on the entry of 2026-09-29 above). As built: `inbox promote` always writes `remedy: none (filed automatically)` (`issueschema.MachineRemedy`), whatever the report proposes, so `abcd drain --dry-run` lists the issue as ineligible; the sender's proposal stays in the issue's text under "Remedy the reporter proposes:", scrubbed like every other value the report carries, for a person to adopt with `capture remedy`. This narrows the entry above, which filed a report's own remedy as the issue's; the ruling CL1 may widen it again.
2026-09-30 — Pending the person's ruling CL1, a promoted inbox report files the machine value: outside text never becomes a drain-eligible remedy without a person naming it (fix round of lane remedyRequired, autonomous run A, closing the review's trust finding on the entry of 2026-09-29 above). As built: inbox promote always writes remedy: none (filed automatically) (issueschema.MachineRemedy), whatever the report proposes, so abcd drain --dry-run lists the issue as ineligible; the sender's proposal stays in the issue's text under "Remedy the reporter proposes:", scrubbed like every other value the report carries, for a person to adopt with capture remedy. This narrows the entry above, which filed a report's own remedy as the issue's; the ruling CL1 may widen it again.
Frontmatter
| id | dcn-2609300000000016 |
|---|---|
| type | decision |
| date | 2026-09-30 |
.abcd/work/decisions/dcn-2609300000000016-pending-the-person-s-ruling-cl1-a.md
open on GitHub ↗ · commit history ↗