Service Agent Execution Queue

Status: first-slice-accepted-queue-not-completion-proof.

This page explains service-agent-execution-queue.json, the orchestrator-owned queue of the first bounded worker slice for each canonical service owner. The current first slices have accepted handoffs, so this queue is now a historical handoff pointer and next-slice planning baseline, not a prompt to respawn the same workers. It is the dispatch bridge between the manifest/proof ledgers and actual service-agent handoffs.

For the next worker after an accepted first slice, use Service Agent Next Slice Queue. That page translates the current proof-ledger open gates into bounded next-slice focus areas.

Use this queue with:

• docs/agents/service-agent-manifest.json
• docs/agents/service-agent-proof-ledger.json
• docs/agents/service-agent-closeout-ledger.json
• docs/agents/service-agent-next-slice-queue.md
• docs/agents/service-agent-spawn-packets.md
• docs/agents/service-workflow-test-matrix.md
• docs/agents/agent-handoff-format.md

Rules

• Queue rows can be ready-to-spawn before a handoff is accepted, or first-slice-accepted after closeout accepts that handoff. Both states remain not complete until the row's proof gate closes.
• The taskId must keep the Dispatch ID prefix, for example SVC-003-session-jwks-access-scope.
• Every handoff must prove the loop: audit, investigate, code, test, fix.
• Spawn at most one active worker per implementationOwner.
• Legacy source under /Users/velikho/Desktop/WORKING/HOCTAPAZ/ is read-only evidence.
• Default gateway route promotion remains blocked unless a row has explicit live/browser proof, rollback notes, and orchestrator approval.
• auth-service is not a queue row; identity/access work routes to iam-service.
• formula-docx-service is a runtime-adapter row and must not create services/formula-docx-service.

Guard

Run:

make test-service-agent-execution-queue

The guard validates that queue rows:

• stay aligned with service-agent-manifest.json, service-agent-proof-ledger.json, and service-agent-closeout-ledger.json;
• keep exactly SVC-001 through SVC-023;
• use unique taskId values with the matching dispatch prefix;
• include the manifest first verification command in workflowVerification;
• keep workflowVerification commands unique so duplicate checks do not hide missing workflow coverage;
• point required handoffs under docs/agents/handoffs/<Dispatch ID>-...;
• keep every status explicitly not-complete;
• use first-slice-accepted when the closeout ledger already records the matching accepted handoff, so the first slice is not respawned by mistake;
• keep dependencies inside the canonical dispatch set.

Current Queue

Dispatch ID	Service	Task ID	Status
SVC-001	api-gateway	SVC-001-protected-route-jwks-rehearsal	first-slice-accepted-not-complete
SVC-002	bff-service	SVC-002-next-owner-read-adapter	first-slice-accepted-not-complete
SVC-003	iam-service	SVC-003-iam-backfill-cutover-hardening	first-slice-accepted-cutover-gated-not-complete
SVC-004	profile-service	SVC-004-profile-backfill-cutover-hardening	first-slice-accepted-cutover-gated-not-complete
SVC-005	organization-service	SVC-005-student-roster-import-boundary	first-slice-accepted-not-complete
SVC-006	classroom-service	SVC-006-legacy-lessons-materials-tuition-audit	first-slice-accepted-not-complete
SVC-007	course-service	SVC-007-quiz-question-integration-contract	first-slice-accepted-not-complete
SVC-008	question-service	SVC-008-question-permanent-delete-worker-parity	first-slice-accepted-not-complete
SVC-009	exam-service	SVC-009-share-link-workflow-tests	first-slice-accepted-not-complete
SVC-010	attempt-service	SVC-010-timeout-retake-result-visibility	first-slice-accepted-not-complete
SVC-011	file-service	SVC-011-object-delete-archive-lifecycle	first-slice-accepted-not-complete
SVC-012	import-service	SVC-012-import-list-repository-pagination	first-slice-accepted-not-complete
SVC-013	formula-docx-service	SVC-013-formula-runtime-boundary-audit	first-slice-accepted-runtime-adapter-not-complete
SVC-014	search-service	SVC-014-projection-worker-runtime-fixtures	first-slice-accepted-not-complete
SVC-015	ai-service	SVC-015-queue-worker-batching-semantics	first-slice-accepted-not-complete
SVC-016	billing-service	SVC-016-renewal-mutation-no-proration	first-slice-accepted-not-complete
SVC-017	wallet-service	SVC-017-wallet-admin-review-response-parity	first-slice-accepted-not-complete
SVC-018	usage-service	SVC-018-quota-caller-contract-fixtures	first-slice-accepted-not-complete
SVC-019	payment-service	SVC-019-sepay-legacy-response-parity	first-slice-accepted-not-complete
SVC-020	notification-service	SVC-020-attempt-grade-notification-producer-contract	first-slice-accepted-not-complete
SVC-021	audit-service	SVC-021-legacy-admin-audit-backfill-report	first-slice-accepted-not-complete
SVC-022	analytics-service	SVC-022-mastery-projection-fixtures	first-slice-accepted-not-complete
SVC-023	admin-service	SVC-023-support-moderation-source-contract	first-slice-accepted-not-complete