You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
managed-agents: map the docs corpus and pick a first credit-funded workload #7675
The claude.dev post "Building effective agent automations" (2026-10-08, https://claude.dev/blog/building-effective-agent-automations/) runs a scheduled agent on Managed Agents and points readers at an onboarding path. Anthropic's credit pages say the monthly API credits cover Managed Agents. Managed Agents is in beta and is not eligible for ZDR or a HIPAA BAA. Digest entries 18 and 19.
Decision
Q11: entry 18 moves forward as its own track instead of deferring.
Q12: digest the Managed Agents docs with a /knowledge:map-corpus run scoped to the platform.claude.com managed-agents pages, then queue its pages for /knowledge:docpage-digest.
Q38: credit-funded work is backlog work with value of its own; this track is the first Managed Agents candidate. Work is never created only to spend credit.
Entry 19: the operator decides whether to run the onboarding path; fetch the post's reference agent.md only as part of this track.
Acceptance criteria
A verified corpus map of the Managed Agents docs exists, with an approved digest queue.
One first workload is chosen, with its basis: it needs no local machine, it is read-only or its writes are scoped, and its data is fit for a beta surface that is not ZDR or HIPAA BAA eligible.
The choice states how a run's failure is detected, given that a succeeded deployment run only means a session was created.
No price, rate or per-task cost appears in tracked docs outside the cost-claims exceptions.
Understood: map the platform.claude.com Managed Agents docs with /knowledge:map-corpus, then record one first credit-funded workload in row A18 of the upstream digest doc. The workload needs no local machine, is read-only or scoped-write, and uses public repository data only. The record must also say how a run's failure is detected, and it must carry no prices.
The corpus-map approval needs an attended session, so a person has to run that check. The docs edit can be checked without one. The earlier questions look answered by the owner's comment, so nothing is open. I found no likely duplicates. #6970 depends on this issue.
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.
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).
melodic-automation-lanes commented on Oct 25, 2026
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.
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
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
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
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.**.
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
No owner ledger (.work/*/interview-checklist.md, .work/gh-monitor-owner-decisions/) names this issue. The body's "Decision" section (Q11, Q12, Q38, entry 19) stands.
This answers the four questions in intake's refinement (#7675 (comment)).
Who approves the digest queue, and how is it recorded?
Decided: The /knowledge:map-corpus run's own gates: check_linkmap.py must PASS, then the map is approved in the session running the skill, which freezes it (plugins/knowledge/skills/map-corpus/SKILL.md:137-151); queue.json is "the approved queue" (:184-186). That approval needs an attended session, and the skill commits nothing ("nothing this skill writes is ever committed", :66), so the map criterion is a check a person runs, not a repository criterion.
Which data is fit for a beta surface without ZDR or HIPAA BAA eligibility?
Decided: Public repository data only: no secrets, no private-repository content. This narrows the body's own criterion and widens nothing; this repository is public (AGENTS.md:51), so its content already meets it.
Choose only, or also launch?
Decided: Choose only. The body's criterion is "One first workload is chosen", moving a lane is out of scope, and running the onboarding path stays with the operator (body, entry 19; docs/upstream/claude-dev-building-effective-agent-automations.md:72). Basis: the body.
Where is the choice recorded?
Decided: In row A18 of docs/upstream/claude-dev-building-effective-agent-automations.md (:71), which already names this track and managed-agents: map the docs corpus and pick a first credit-funded workload #7675. No new file. Basis: docs/upstream/claude-dev-building-effective-agent-automations.md:71.
Acceptance criteria (converted from the body's criteria list, wording unchanged except the location, the public-data rule from item 2, and the map criterion moved to the person check below):
Row A18 of docs/upstream/claude-dev-building-effective-agent-automations.md names one first workload, with its basis: it needs no local machine, it is read-only or its writes are scoped, and its data is fit for a beta surface that is not ZDR or HIPAA BAA eligible (public repository data only).
The choice states how a run's failure is detected, given that a succeeded deployment run only means a session was created.
No price, rate or per-task cost appears in tracked docs outside the cost-claims exceptions (.claude/rules/cost-claims.md).
Checks a person runs:
A verified corpus map of the Managed Agents docs exists, with an approved digest queue: a /knowledge:map-corpus run scoped to the platform.claude.com managed-agents pages (body Q12), whose map is approved in that session before the workload is chosen.
Activity
github-actions commentedon Oct 16, 2026
Proposed work class: work-class: scoped
Basis: automated intake triage; the lanes App applied this class.
Size: Small
Complexity: Low
Uncertainty: Knowable
Flags: none
Blocked by: none
Understood: map the platform.claude.com Managed Agents docs with
/knowledge:map-corpus, then record one first credit-funded workload in row A18 of the upstream digest doc. The workload needs no local machine, is read-only or scoped-write, and uses public repository data only. The record must also say how a run's failure is detected, and it must carry no prices.The corpus-map approval needs an attended session, so a person has to run that check. The docs edit can be checked without one. The earlier questions look answered by the owner's comment, so nothing is open. I found no likely duplicates. #6970 depends on this issue.
Automated triage, applied by the lanes App.
kyle-sexton commentedon Oct 25, 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 25, 2026
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).melodic-automation-lanes commentedon Oct 25, 2026
The latest triage verdict holds nothing: the issue is at
status: ready.melodic-automation-lanes commentedon Oct 25, 2026
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
Related work
Open questions
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
RECOMMENDED: Public repository data only: no secrets, no customer data, no private-repo contents beyond what lanes already read. Basis: judgment
RECOMMENDED: Write-up only: the issue says choose, and launching needs the operator's onboarding step (entry 19). Basis: judgment
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
Automated refinement by the lanes App. Answer with a comment whose first line is
**Decision recorded.**.kyle-sexton commentedon Oct 26, 2026
Decision recorded. The owner answered in the Refinement and Issue Triage sessions (2026-10-25), deciding the open items below on the facts:
No owner ledger (
.work/*/interview-checklist.md,.work/gh-monitor-owner-decisions/) names this issue. The body's "Decision" section (Q11, Q12, Q38, entry 19) stands.This answers the four questions in intake's refinement (#7675 (comment)).
Decided: The
/knowledge:map-corpusrun's own gates:check_linkmap.pymust PASS, then the map is approved in the session running the skill, which freezes it (plugins/knowledge/skills/map-corpus/SKILL.md:137-151);queue.jsonis "the approved queue" (:184-186). That approval needs an attended session, and the skill commits nothing ("nothing this skill writes is ever committed",:66), so the map criterion is a check a person runs, not a repository criterion.Decided: Public repository data only: no secrets, no private-repository content. This narrows the body's own criterion and widens nothing; this repository is public (
AGENTS.md:51), so its content already meets it.Decided: Choose only. The body's criterion is "One first workload is chosen", moving a lane is out of scope, and running the onboarding path stays with the operator (body, entry 19;
docs/upstream/claude-dev-building-effective-agent-automations.md:72). Basis: the body.Decided: In row A18 of
docs/upstream/claude-dev-building-effective-agent-automations.md(:71), which already names this track and managed-agents: map the docs corpus and pick a first credit-funded workload #7675. No new file. Basis:docs/upstream/claude-dev-building-effective-agent-automations.md:71.Acceptance criteria (converted from the body's criteria list, wording unchanged except the location, the public-data rule from item 2, and the map criterion moved to the person check below):
docs/upstream/claude-dev-building-effective-agent-automations.mdnames one first workload, with its basis: it needs no local machine, it is read-only or its writes are scoped, and its data is fit for a beta surface that is not ZDR or HIPAA BAA eligible (public repository data only)..claude/rules/cost-claims.md).Checks a person runs:
/knowledge:map-corpusrun scoped to the platform.claude.com managed-agents pages (body Q12), whose map is approved in that session before the workload is chosen.