communication: decide plugin details (check, reply drafts, voice, send denial) #7557

Activity

1. kyle-sexton

   added

   needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.Human-in-the-loop required; autonomous sessions must not resolve items carrying this.

   on Oct 16, 2026
2. kyle-sexton

   added the

   Feature

   issue type on Oct 16, 2026
3. kyle-sexton

   added a parent issue on Oct 16, 2026

   • Epic: absorb Lauren Tan's and Matt Pocock's agent workflows (poteto-review) #7555
4. kyle-sexton

   set

   Work status

   to

   needs-spec

   on Oct 16, 2026
5. github-actions commented on Oct 16, 2026

   

   github-actionsBot

   on Oct 16, 2026 – with GitHub Actions

   Last edited by github-actions

   Contributor

   More actions

   Proposed work class: none

   Size: Large
   Complexity: Medium
   Uncertainty: Knowable
   Flags: intent

   Understood: this is a parked design item to decide the communication plugin's details (Q191-Q198). That covers the check command, two-block reply drafts, a voice skill, send-tool denial, polling and later kinds. The body says it reopens only when the plugin design starts. The earlier comment releases it for re-triage, but nothing records that the trigger fired. No duplicates found among open issues.

   Open questions:

   1. Has the reopen trigger (communication plugin design starts) fired? RECOMMENDED: no, keep it parked. The body names communication as lowest priority (Q154, Q156) and puts build work out of scope before the trigger.
   2. Receive path: /loop 5m /communication:check or a one-way channel plugin? RECOMMENDED: /loop polling. It needs no new plugin surface and fits the trigger-dispatch contract the body names.
   3. Where does send denial live: user settings, Cursor config, or both? RECOMMENDED: both, since the body lists both as options and a draft-only rule is only as strong as its weakest client.

   _{Automated triage. A maintainer reviews it.}
6. github-actions

   changed the issue type from

   Feature

   to

   Task

   on Oct 16, 2026
7. kyle-sexton

   changed the issue type from

   Task

   to

   Feature

   on Oct 16, 2026
8. kyle-sexton

   added

   needs-specNeeds a Brief or plan before anyone can build it.Needs a Brief or plan before anyone can build it.

   on Oct 16, 2026
9. kyle-sexton

   removed

   needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.Human-in-the-loop required; autonomous sessions must not resolve items carrying this.

   on Oct 24, 2026
10. kyle-sexton commented on Oct 24, 2026

    

    kyle-sexton

    on Oct 24, 2026

    MemberAuthor

    More actions

    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 (or status: needs-decision) and say why in a comment.
11. github-actions

    added

    priority: lowNice-to-have, cosmetic, or speculative; opportunistic.Nice-to-have, cosmetic, or speculative; opportunistic.

    status: needs-decisionAwaiting a human or maintainer judgment call.Awaiting a human or maintainer judgment call.

    needs-triageNot yet classified. Floor until a type and one priority tier are set.Not yet classified. Floor until a type and one priority tier are set.

    on Oct 24, 2026
12. github-actions

    changed the issue type from

    Feature

    to

    Task

    on Oct 24, 2026
13. melodic-automation-lanes commented on Oct 24, 2026

    

    melodic-automation-lanesBot

    on Oct 24, 2026

    Contributor

    More actions

    Refinement. A read-only run explored this repository, searched its issues and pull requests, and read the allowed docs to draft what follows. It is model text, to check, not instructions.

    Intended outcome: The communication plugin's details (Q191-Q198) are decided and recorded by the owner once the design starts; until then the issue stays parked.

    Related work

    • lanes: record trigger facts as pointers #7592 (related): Frames outer-loop text as data and records trigger facts; bears on the trigger-dispatch contract and untrusted wrapping the communication plugin would use.
    • corrections: new plugin with /corrections:codify #7573 (related): Another new-plugin issue from the same plan; shows the plugin shape but does not decide communication details.

    Open questions

    1. Has the reopen trigger (the communication plugin design starts) fired, and where is it recorded?
       RECOMMENDED: No. Keep the issue parked until the owner cites the trigger in a comment. Basis: The body sets communication as lowest priority (Q154, Q156) and puts build work out of scope before the trigger. No plugins/communication directory exists in the checkout, and no comment records the trigger.
    2. Receive path: poll with /loop 5m /communication:check, or build a one-way channel plugin?
       RECOMMENDED: Poll with /loop. It adds no new plugin surface and fits the trigger-dispatch contract. Basis: judgment
    3. Where does send-tool denial live: user settings, Cursor config, or both?
       RECOMMENDED: Both, since a drafts-only rule is only as strong as the weakest client. This is a security call, so the owner decides. Basis: judgment
    4. Which of Q191-Q198 does the owner decide now, and which stay deferred? Only the team-communication convention rename of Q191 is listed as remaining.
       RECOMMENDED: Leave all deferred except the rename. The done-when item needs a recorded decision per question, which an unattended run cannot make. Basis: judgment

    Sources read

    • /home/runner/work/_temp/refine-data/context.json: the body defers Q191-Q198 to a reopen trigger, and the only comment is a generic re-triage release that does not record the trigger.
    • plugins glob in the checkout: no communication plugin exists; the only match is plugins/playbooks/skills/fable-5/context/communication.md, a context file for another plugin.

    _{Automated refinement by the lanes App. Answer with a comment whose first line is **Decision recorded.**.}
14. kyle-sexton

    changed the issue type from

    Task

    to

    Feature

    on Oct 25, 2026
15. kyle-sexton commented on Oct 27, 2026

    

    kyle-sexton

    on Oct 27, 2026

    MemberAuthor

    More actions

    Decision recorded. The owner answered in the Refinement and Issue Triage sessions (2026-10-25), deciding the open items below on the facts:

    go with whatever the facts/data/metrics + /discovery:research says and ensure we're aligned with SOLID, DRY/SSOT principles

    I should only ever be in the loop ONLY when necessary (intent/vision changed, something came up during implementation that impacts trajectory/alignment, OR a high security risk) - I've covered this all before

    This answers the questions in the lane's pushback (#7557 (comment)).

    1. Has the reopen trigger (the communication plugin design starts) fired?
       Decided: No, so the owner's deferral stands. The owner made communication lowest priority: Q154 is "accepted with broader scope: communication covers all personal written communication (chat and messengers, SMS, email and Outlook, other written forms); lowest priority" (.work/poteto-review/interview-checklist.md:199), Q156 is "accepted, lowest priority" (.work/poteto-review/interview-checklist.md:201), and decision 89 is "APPROVED, lowest priority" (.work/poteto-review/GUIDE.md:199, owner 2026-10-15). Each of Q191-Q198 is recorded as deferred (.work/poteto-review/interview-checklist.md:236-243), for example Q196:

       deferred to the communication plugin design (owner: lowest priority, Q154, Q156)

       The deferral table names the reopen trigger "the communication plugin design starts (lowest priority)" (.work/poteto-review/shared-understanding.md:347).
       The trigger has not fired. On origin/main (ecdba7a3a6), git ls-tree -d origin/main plugins/communication returns nothing, and git grep -nE 'communication:check|/communication:|plugins/communication' origin/main returns nothing. No comment on the issue cites a design start.

    2. Receive path (/loop polling or a channel plugin), send-tool denial placement, and which of Q191-Q198 to decide now.
       Decided: None of them now. They are Q196, Q195 and Q191-Q198, all recorded as deferred to the communication plugin design (.work/poteto-review/interview-checklist.md:236-243). The lane's recommendations on them are inputs for that design, not decisions. Nothing here touches a send permission, so no security boundary moves.

    Closed as a recorded deferral. Reopen trigger: the communication plugin design starts. When it does, reopen this issue, cite the start in a comment, record a decision for each of Q191-Q198, and file the slices under it, as the body's "Done when" says. Until then there is no lane work, so this record sets no - [ ] criteria. Close as not planned.
16. kyle-sexton

    closed this as not plannedon Oct 27, 2026