Repository navigation
architecture: Dune-like agent framework for the day job #7560
Description
Parent
Refs #7555. Source: PLAN Phase 0, topic poteto-review. Thread: Dune-like framework for the day job
(deferred).
Depends on
- none (parked: opens on the reopen trigger below, not on an edge)
Reopen trigger
Earned by recurrence from the cheaper ladder rungs: the cheaper levels run first and a framework is
built only when they recur (D65, Q52).
Outcome
When reopened: an agent-friendly framework for the day job, built from what the cheaper rungs
showed.
Decisions
- Deferred: start with the cheapest levels and earn the rest by recurrence (D65, Q52). Origin:
Lauren's ("prose last" order) with the ladder's strongest-rung rule. - Options on record: build now versus earn by recurrence; earn chosen.
Key interfaces
None (deferred, no module change yet).
Done when
- A recurrence count from codify or the buffer shows the trigger, cited in a comment.
- Slices are filed under this item.
Out of scope
- Framework code before the trigger fires.
Activity
github-actions commentedon Oct 16, 2026
Proposed work class: none
Size: Large
Complexity: High
Uncertainty: Unknown
Flags: none
Blocked by: none
Understood: this is a parked item for an agent-friendly framework for the day job. Per the recorded decisions (D65, Q52), it reopens only when the cheaper ladder rungs show recurrence. No framework code is in scope before that trigger fires.
Nothing is missing for triage. The done-when items are a recurrence count cited in a comment, then slices filed under this item. The approach can't be known until the trigger fires. No duplicates found among the open issues.
Automated triage. A maintainer reviews it.
kyle-sexton commentedon Oct 24, 2026
Released for re-triage under the owner's 2026-10-24 rule: an issue stops for a person only for an intent or vision question, a security call, a host or attended run, or spend outside prepaid credit. The hold label came off and intake triage runs again now; it re-applies a hold, with a numbered question, when one of those applies.
To hold this issue again, add
needs-human(orstatus: needs-decision) and say why in a comment.melodic-automation-lanes commentedon Oct 24, 2026
Not admitted to the issue lane: Uncertainty unknown is not one of known, knowable; Size large: the split into sub-issues at intake is pending (owner Q93). Admission takes the issue once each of those is met, when intake triages it again (
.github/actions/resolve-config/admission-rules.json).kyle-sexton commentedon Oct 27, 2026
Released for re-triage under the owner's 2026-10-26 rule: a person is involved only for "1. A change in original intent/vision 2. Something comes up during implementation ... that alters intent/vision or the primary design 3. If there is a HIGH/CRITICAL security issue". None applies here, so the hold label came off and intake triage runs again now.
To hold this issue again, add
needs-human(orstatus: needs-decision) and name which of the three applies.melodic-automation-lanes commentedon Oct 27, 2026
The latest triage verdict holds nothing: admission moved the issue to
status: confirmed; its comment says why.