Service decomposition: archie-core modularization #1140

Closed
opened 2026-10-27 13:39:11 +00:00 by sam · 0 comments
Owner

archie-core moves from one Go binary (archied) hosting every domain
in-process to a set of independently deployable services, each exposing
exactly one typed contract. Consumers depend on the contract; they never
reach into another service's internal types, session state, or config.
gRPC is the synchronous transport; NATS remains for asynchronous fan-out
(status, telemetry) rather than being replaced.

This is a distribution decision, not a rewrite of Archie's domain model.
The six-domain split already approved in docs/architecture/index.md and
docs/architecture/organisation.md (Identity, Agent, Messaging, Workflow,
Work Intake, Plugin) is unchanged; this epic is about how the processes
running that domain logic get packaged, contracted, and discovered.

Target services (see the PRD's table): UI Service, Gateway Service,
Messaging Service, Curator Service (optional), Scheduler Service,
Execution Environment, Runner, State Store.

All five blocking open questions in the PRD are resolved as of
2026-09-05: extraction order (Gateway first, then State Store, UI,
Messaging, Execution/Runner/Scheduler, Curator -- preceded by a Phase 0
contract-seams step), contract-definition mechanism (buf v2 +
protoc-gen-go/grpc-go), in-process-vs-out-of-process migration mechanism
(multiplexed in-process is the default, per-service wire-safe contract
interfaces with local + gRPC adapters), State Store's contract shape (one
State Store service, single SQLite, narrow typed contracts, no physical
per-service database), and Helm chart / Operator ownership (a library
chart + a core-services chart + a Curator chart/Operator).

Full decision record: docs/prds/service-decomposition.md
Full resolution detail and reasoning for each question:
docs/inspiration/service-decomposition-open-questions-research-2026-09-05.md

Filing this epic satisfies the PRD's "file a beads epic" completion
criterion only. It does NOT authorize implementation -- the PRD's
completion criteria separately require the captain's explicit go-ahead
given the scale of this change. No implementation work should start
against the child issues below until that go-ahead is given.

Close reason

Reconciled: State Store, Gateway, UI and Messaging are separate services; remaining phases closed as superseded or not planned; component self-report moved under archie-core-6vfu.


Imported from beads archie-core-8cda · GitHub #724 · type epic · priority P1 · created 2026-09-05 · closed 2026-10-03

archie-core moves from one Go binary (archied) hosting every domain in-process to a set of independently deployable services, each exposing exactly one typed contract. Consumers depend on the contract; they never reach into another service's internal types, session state, or config. gRPC is the synchronous transport; NATS remains for asynchronous fan-out (status, telemetry) rather than being replaced. This is a distribution decision, not a rewrite of Archie's domain model. The six-domain split already approved in docs/architecture/index.md and docs/architecture/organisation.md (Identity, Agent, Messaging, Workflow, Work Intake, Plugin) is unchanged; this epic is about how the processes running that domain logic get packaged, contracted, and discovered. Target services (see the PRD's table): UI Service, Gateway Service, Messaging Service, Curator Service (optional), Scheduler Service, Execution Environment, Runner, State Store. All five blocking open questions in the PRD are resolved as of 2026-09-05: extraction order (Gateway first, then State Store, UI, Messaging, Execution/Runner/Scheduler, Curator -- preceded by a Phase 0 contract-seams step), contract-definition mechanism (buf v2 + protoc-gen-go/grpc-go), in-process-vs-out-of-process migration mechanism (multiplexed in-process is the default, per-service wire-safe contract interfaces with local + gRPC adapters), State Store's contract shape (one State Store service, single SQLite, narrow typed contracts, no physical per-service database), and Helm chart / Operator ownership (a library chart + a core-services chart + a Curator chart/Operator). Full decision record: docs/prds/service-decomposition.md Full resolution detail and reasoning for each question: docs/inspiration/service-decomposition-open-questions-research-2026-09-05.md Filing this epic satisfies the PRD's "file a beads epic" completion criterion only. It does NOT authorize implementation -- the PRD's completion criteria separately require the captain's explicit go-ahead given the scale of this change. No implementation work should start against the child issues below until that go-ahead is given. ### Close reason Reconciled: State Store, Gateway, UI and Messaging are separate services; remaining phases closed as superseded or not planned; component self-report moved under archie-core-6vfu. --- _Imported from beads `archie-core-8cda` · GitHub #724 · type epic · priority P1 · created 2026-09-05 · closed 2026-10-03_
sam added the highepic labels 2026-10-27 13:39:11 +00:00
sam self-assigned this 2026-10-27 13:39:11 +00:00
sam closed this issue 2026-10-27 13:39:11 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#1140