managed-agents: map the docs corpus and pick a first credit-funded workload #7675

Activity

1. github-actions

   added

   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 16, 2026
2. github-actions commented on Oct 16, 2026

   

   github-actionsBot

   on Oct 16, 2026 – with GitHub Actions

   Last edited by melodic-automation-lanes

   Contributor

   More actions

   Proposed work class: work-class: scoped
   Basis: automated intake triage; the lanes App applied this class.

   Size: Medium
   Complexity: Medium
   Uncertainty: Knowable
   Flags: none
   Blocked by: none

   Understood: run a corpus map of the Managed Agents docs, queue the pages for digest, and pick one first workload. The workload must need no local machine, be read-only or write only in a narrow scope, and use data suited to a beta surface without ZDR or HIPAA BAA eligibility. The choice must also say how a failed run is detected, since a succeeded run only means a session was created. The issue states its decisions (Q11, Q12, Q38, entry 19), so nothing is missing. I found no duplicates. Credit spend is prepaid, so there is no billing flag.

   _{Automated triage, applied by the lanes App.}
3. github-actions

   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.

   and removed

   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 16, 2026
4. github-actions

   added the

   Task

   issue type on Oct 16, 2026
5. 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 25, 2026
6. kyle-sexton commented on Oct 25, 2026

   

   kyle-sexton

   on Oct 25, 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.
7. github-actions

   added

   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.

   priority: mediumReal value, no hard deadline; normal backlog flow.Real value, no hard deadline; normal backlog flow.

   and removed

   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 25, 2026
8. melodic-automation-lanes

   added

   status: readyTriaged, unblocked, and fully specified; eligible to pick up.Triaged, unblocked, and fully specified; eligible to pick up.

   work-class: scopedA briefed fix or small feature; blast radius bounded by the brief, tests exist.A briefed fix or small feature; blast radius bounded by the brief, tests exist.

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

   and removed

   status: readyTriaged, unblocked, and fully specified; eligible to pick up.Triaged, unblocked, and fully specified; eligible to pick up.

   on Oct 25, 2026
9. melodic-automation-lanes commented on Oct 25, 2026

   

   melodic-automation-lanesBot

   on Oct 25, 2026

   Contributor

   More actions

   Not admitted to the issue lane: no trusted-human acceptance criteria: a listed human must put the confirmed - [ ] criteria in the body or post them as their own comment, or, on an issue a listed human filed, intake's newest refinement comment must hold them unedited. Admission takes the issue once each of those is met, when intake triages it again (.github/actions/resolve-config/admission-rules.json).
10. melodic-automation-lanes commented on Oct 25, 2026

    

    melodic-automation-lanesBot

    on Oct 25, 2026

    Contributor

    More actions

    The latest triage verdict holds nothing: admission moved the issue to status: needs-decision; its comment says why.
11. melodic-automation-lanes commented on Oct 25, 2026

    

    melodic-automation-lanesBot

    on Oct 25, 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. On an issue a listed human filed, it counts as the issue's spec once posted, while unedited; it is still model text, so check it.

    Intended outcome: A verified map of the platform.claude.com Managed Agents docs with a digest queue, plus one chosen read-only first workload with a failure-detection rule, recorded in a docs file.

    Dependencies

    • #​6970 takes the chosen workload as its first Managed Agents entry, so it waits on this issue.

    Related work

    • Map: run the agent lanes at full Claude capacity #6958 (related): Parent map issue this one refs.
    • knowledge: add the deferred repository-tree enumeration rung to map-corpus #7368 (related): Open change to map-corpus discovery that this run would use.

    Open questions

    1. Who approves the digest queue the acceptance criteria call approved, and how is approval recorded?
       RECOMMENDED: Treat it as approved when the map-corpus verification gate passes and the queue file is merged; the owner can strike pages in review. Basis: judgment
    2. Which data counts as fit for a beta surface without ZDR or HIPAA BAA eligibility? This is a security call for the owner.
       RECOMMENDED: Public repository data only: no secrets, no customer data, no private-repo contents beyond what lanes already read. Basis: judgment
    3. Is a written choice of workload enough, or must the issue also launch it on Managed Agents?
       RECOMMENDED: Write-up only: the issue says choose, and launching needs the operator's onboarding step (entry 19). Basis: judgment
    4. Where should the map, queue and workload choice be recorded, and what are the checkable done-when items?
       RECOMMENDED: Put them under docs/upstream/ next to claude-dev-building-effective-agent-automations.md, with a task list of map verified, queue listed, workload and failure detection stated, and no prices. Basis: docs/upstream/claude-dev-building-effective-agent-automations.md

    Sources read

    • context.json: issue 7675 body states decisions Q11, Q12, Q38 and entry 19 and four acceptance criteria but has no task list
    • AGENTS.md:149: cost-claims rule bars prices and per-task figures outside docs/upstream vendor-reported records
    • plugins/knowledge/skills/map-corpus/SKILL.md: the skill the issue says to run

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