Microservices

This section collects the current Go-platform service split, IAM/Profile cutover design, and service-agent dispatch material. It is the starting point before assigning a service owner agent or promoting any route from legacy proxy to a native service.

Start Here

Need	Read
Canonical service ownership	Service Responsibility Matrix
Service guide by domain, implementation path, and authority line	Service Catalog
Runtime topology and service communication rules	Target Go Microservices
Database-per-service rules	Database Per Service
Machine-readable service-agent rows	Service Agent Manifest
Service-agent proof state	Service Agent Proof Ledger
Service-agent handoff closeout state	Service Agent Closeout Ledger
Next-slice handoff closeout state	Service Agent Next Slice Closeout Ledger
Accepted bounded handoff index	Service Agent Accepted Handoffs
First bounded service-owner slices	Service Agent Execution Queue
Next proof-gate slices after accepted handoffs	Service Agent Next Slice Queue
Prompt packets for next proof-gate slices	Service Agent Next Slice Spawn Packets
Service owner dispatch units	Service Agent Dispatch Roster
Parallel service-agent spawning	Service Agent Spawn Runbook
Ready-to-spawn service packets	Service Agent Spawn Packets
Current wave status and cross-service backlog	Service Agent Wave Board
Per-service workflow and verification commands	Workflow Test Matrix
Service task packs	Service Task Pack README

IAM/Profile Cutover

Topic	Read
Legacy auth/profile inventory	Legacy User And Auth Inventory
IAM/Profile boundary and current status	IAM/Profile Design
UUID storage cutover guardrail	IAM/Profile UUID Cutover Design
Current implementation report	IAM/Profile Implementation Report

Dispatch Rules

• Legacy source under /Users/velikho/Desktop/WORKING/HOCTAPAZ/ is evidence only; implementation work stays under go-platform/.
• Frontend apps call only api-gateway or an approved BFF.
• Each service owns its database and must not read another service database.
• iam-service owns identity/access; profile-service owns education profile data; user-service is a deprecated compatibility scaffold.
• AZ Credits and subscriptions are split across billing-service, wallet-service, usage-service, and payment-service; do not put plan, ledger, quota, or provider webhook ownership in IAM/Profile.
• Alias services use the current implementation directory from the matrix until a separate rename task is approved.
• Default gateway route promotion requires route proof, browser/runtime proof, and rollback notes.