Service Agent Next Slice Queue

Status: next-slice-dispatch-baseline-not-completion-proof.

Source path: docs/agents/service-agent-next-slice-queue.md. Machine-readable queue: docs/agents/service-agent-next-slice-queue.json.

This page is the orchestrator queue for work after the accepted first-slice handoffs. It does not replace service-agent-execution-queue.json; that JSON keeps the accepted first-slice handoff pointer for each canonical service. Use this page when the execution queue row is already first-slice-accepted and the proof ledger still has an open gate.

Use this queue with:

• docs/agents/service-agent-proof-ledger.json
• docs/agents/service-agent-closeout-ledger.json
• docs/agents/service-agent-execution-queue.json
• docs/agents/service-agent-next-slice-queue.json
• docs/agents/service-agent-accepted-handoffs.md
• docs/agents/service-agent-spawn-runbook.md
• docs/agents/service-agent-spawn-packets.md
• docs/agents/service-agent-next-slice-spawn-packets.md
• docs/agents/service-agent-next-slice-closeout-ledger.json
• docs/agents/agent-handoff-format.md

Rules

• Do not respawn the first-slice taskId once its handoff is accepted.
• Pick the next bounded slice from the row's current open proof gate.
• Keep the Dispatch ID prefix in every new task ID.
• Keep frontend callers behind api-gateway or an approved BFF.
• Default gateway route promotion remains blocked until the next-slice handoff includes route proof, browser/runtime proof, and rollback evidence.
• iam-service owns auth, JWT, sessions, roles, permissions, and access control. profile-service owns display/profile projection data.
• auth-service is not a dispatch row; identity/access work routes to iam-service.
• RET-USER is retirement-only. Do not add new product work to services/user-service.

Next Slice Queue

Dispatch ID	Service	Next slice focus	Open proof gate
SVC-001	api-gateway	Route-specific live/browser proof and rollback notes before default promotion.	Route-specific gateway live/browser proof and rollback notes are required before any default route promotion.
SVC-002	bff-service	Owner-service source evidence plus gateway route proof for any BFF route change.	BFF route changes need owner-service source evidence and gateway route proof.
SVC-003	iam-service	Production-like IAM/Profile auth cutover proof bundle with migrator run report, candidate review, browser proof, and rollback-after-candidate proof.	Default IAM/Profile auth promotion still needs a passed default cutover proof bundle over production-like populated targets with run-report evidence, candidate review, browser proof, and rollback-after-candidate proof.
SVC-004	profile-service	Production-like profile default promotion proof bundle with candidate diff, browser proof, and rollback-after-candidate proof.	Default profile route promotion still needs a passed default cutover proof bundle over production-like populated targets with candidate diff evidence, browser proof, and rollback-after-candidate proof.
SVC-005	organization-service	IAM membership write authority and school-service read-model sync evidence before member-write route promotion.	IAM membership write authority and school-service read-model sync proof must stay explicit before member-write route promotion.
SVC-006	classroom-service	Public classroom route guard proof with owner-local profile/org references only.	Classroom public route work needs route guard proof and owner-local profile/org references only.
SVC-007	course-service	Student course route guard, live/browser proof, and rollback notes.	Student course route changes need route guards, live/browser proof, and default rollback notes.
SVC-008	question-service	Question read/write/type save-reload proof plus live/browser/rollback evidence.	Question read/write/type route changes need save/reload, live/browser, and rollback evidence before default promotion.
SVC-009	exam-service	Exam authoring/start contract proof with attempt-service plus live/browser proof.	Exam authoring/start slices need exam-attempt contract proof plus live/browser proof before public route promotion.
SVC-010	attempt-service	Public/start route proof covering live, browser, idempotency, and rollback.	Attempt public/start slices need route, live, browser, idempotency, and rollback proof.
SVC-011	file-service	Storage/media parity proof and browser evidence for touched upload/read flows.	Storage/media promotion requires parity proof and browser evidence for touched upload/read flows.
SVC-012	import-service	Import create/status/approval/review route proof with live/browser/rollback evidence.	Import create/status/approval/review changes need matching route, live, browser, and rollback proof.
SVC-013	formula-docx-service	Parser/runtime adapter determinism behind the external Go Formula adapter only.	Parser/runtime work must stay behind the external Go Formula adapter and must not create services/formula-docx-service.
SVC-014	search-service	Exact legacy route ownership mapping plus rebuild/projection proof.	Search route promotion needs exact legacy route ownership mapping plus rebuild/projection proof.
SVC-015	ai-service	AI job/public route proof while keeping quota and credit movement in usage/wallet.	AI job/public route changes need usage/wallet boundary proof and route live proof; AI must not own quota or credit movement.
SVC-016	billing-service	Subscription entitlement replay/idempotency proof before public subscription promotion.	Subscription entitlement events need replay/idempotency proof before public subscription route promotion.
SVC-017	wallet-service	Wallet route proof with immutable ledger, replay, route guard, live proof, and rollback evidence.	Wallet route changes need immutable ledger, replay, route guard, live proof, and rollback evidence.
SVC-018	usage-service	Billing sync replay proof while keeping money movement and workload execution out of usage.	Billing sync replay is accepted; AI generation and OCR/import caller contracts remain owner-service bounded, while route-specific live/browser and rollback proof is required before default public caller route promotion.
SVC-019	payment-service	Webhook/reconcile idempotency, paid-event replay, and downstream billing/wallet proof.	Payment webhook/reconcile changes need idempotency, paid-event replay, and downstream billing/wallet proof.
SVC-020	notification-service	Already-resolved-recipient proof and route rollback notes for notification surfaces.	Notification route changes need already-resolved-recipient proof and route rollback notes.
SVC-021	audit-service	Append-only producer/backfill proof with replay/idempotency, retention, and compatibility evidence.	Audit producer/backfill changes need append-only, replay/idempotency, retention, and compatibility proof.
SVC-022	analytics-service	Rebuildable projection/event-source proof and route guard evidence.	Analytics changes need rebuildable projection/event-source proof and route guard evidence.
SVC-023	admin-service	Owner-service source proof, route/browser proof, and rollback notes before default promotion.	Admin route/dashboard changes need owner-service source proof, route/browser proof, and rollback notes before default promotion.
RET-USER	user-service retirement	Remove or narrow the deprecated compatibility scaffold only after IAM/Profile parity, default-route proof, rollback proof, and user-service retirement criteria are satisfied.	user-service remains a deprecated compatibility scaffold; no new product work belongs there.

Dispatch Pattern

1. Read the accepted handoff in docs/agents/service-agent-accepted-handoffs.md.
2. Read the current row in service-agent-proof-ledger.json.
3. Use the row's nextTaskId from docs/agents/service-agent-next-slice-queue.json.
4. Spawn from docs/agents/service-agent-next-slice-spawn-packets.md, the service task pack, and the row's open proof gate.
5. Require a new handoff under docs/agents/handoffs/ before changing the next-slice closeout/proof state.
6. Accept that future handoff through docs/agents/service-agent-next-slice-closeout-ledger.json; keep the first-slice closeout ledger unchanged.

Completion Boundary

This queue is still not-complete. It only prevents accidental respawn of the accepted first slices and names the next proof gates. Goal completion still requires closing the IAM/Profile production-like cutover proof, route/browser rollback evidence, broader default public route promotions, and RET-USER retirement.