Phase 6: Curator Service (optional, last) #118

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

Sixth and final phase in the resolved extraction order -- deliberately
last, since it is the proof-of-optionality exercise (open question #5),
not a load-bearing step for the base fleet.

Scope: internal/domain/curator installs as a Gateway plugin (its current
shape is already a contract/registrar/registry family per the PRD's
target-services table). This phase proves the optional-service
NotInstalled discovery semantic end to end: an optional service that is
not installed must resolve to a distinct NotInstalled outcome, never a
Down/Unhealthy one (per the ServiceRegistry design in
docs/inspiration/service-discovery-research-2026-09-05.md and
internal/servicediscovery/servicediscovery.go's ErrNotInstalled).

The K8s Operator to deploy Curator (CRD, controller, RBAC, the
archie-curator Helm chart) is open question #5's scoping concern and can
be built against this phase's contract once it lands -- see the
resolved-question research's own suggested first issue breakdown
(Kubebuilder scaffold, reconciler, archie-library chart, archie chart,
ServiceRegistry K8s resolver NotInstalled semantics, end-to-end M1
assertion) for how that follow-on work should be filed once this phase's
contract is settled.

Depends on Phase 5 (Execution/Runner/Scheduler) per the resolved
extraction order.

Full reasoning: docs/inspiration/service-decomposition-open-questions-research-2026-09-05.md#1
(Phase 6 section) and #5 (Helm chart / Operator scoping, M1 milestone).

Acceptance criteria

  • Curator Service exposes a curator contract (proto + generated Go) and
    installs as an optional Gateway plugin, following the same
    local-adapter + gRPC-adapter + conformance-suite shape as prior phases.
  • ServiceRegistry.Resolve/Watch for "curator" returns a distinct
    NotInstalled outcome (not Down/Unhealthy) when Curator is not
    installed, verified by a test.
  • Installing/uninstalling the Curator Service flips its discovery state
    without requiring a Gateway restart or redeploy (mirrors question #5's
    M1 milestone assertion, even if the K8s Operator itself is filed as
    separate follow-on work).
  • task check passes; existing Curator functionality (whatever
    internal/domain/curator provides today) is preserved through the
    contract boundary.

Close reason

Superseded: the Gateway owns all model work, curators included (2026-10-04).


Imported from beads archie-core-8cda.8 · GitHub #749 · type task · priority P4 · created 2026-09-05 · closed 2026-10-03

Sixth and final phase in the resolved extraction order -- deliberately last, since it is the proof-of-optionality exercise (open question #5), not a load-bearing step for the base fleet. Scope: internal/domain/curator installs as a Gateway plugin (its current shape is already a contract/registrar/registry family per the PRD's target-services table). This phase proves the optional-service NotInstalled discovery semantic end to end: an optional service that is not installed must resolve to a distinct NotInstalled outcome, never a Down/Unhealthy one (per the ServiceRegistry design in docs/inspiration/service-discovery-research-2026-09-05.md and internal/servicediscovery/servicediscovery.go's ErrNotInstalled). The K8s Operator to *deploy* Curator (CRD, controller, RBAC, the archie-curator Helm chart) is open question #5's scoping concern and can be built against this phase's contract once it lands -- see the resolved-question research's own suggested first issue breakdown (Kubebuilder scaffold, reconciler, archie-library chart, archie chart, ServiceRegistry K8s resolver NotInstalled semantics, end-to-end M1 assertion) for how that follow-on work should be filed once this phase's contract is settled. Depends on Phase 5 (Execution/Runner/Scheduler) per the resolved extraction order. Full reasoning: docs/inspiration/service-decomposition-open-questions-research-2026-09-05.md#1 (Phase 6 section) and #5 (Helm chart / Operator scoping, M1 milestone). ### Acceptance criteria - Curator Service exposes a curator contract (proto + generated Go) and installs as an optional Gateway plugin, following the same local-adapter + gRPC-adapter + conformance-suite shape as prior phases. - ServiceRegistry.Resolve/Watch for "curator" returns a distinct NotInstalled outcome (not Down/Unhealthy) when Curator is not installed, verified by a test. - Installing/uninstalling the Curator Service flips its discovery state without requiring a Gateway restart or redeploy (mirrors question #5's M1 milestone assertion, even if the K8s Operator itself is filed as separate follow-on work). - task check passes; existing Curator functionality (whatever internal/domain/curator provides today) is preserved through the contract boundary. ### Close reason Superseded: the Gateway owns all model work, curators included (2026-10-04). --- _Imported from beads `archie-core-8cda.8` · GitHub #749 · type task · priority P4 · created 2026-09-05 · closed 2026-10-03_
sam added the task label 2026-10-27 13:35:01 +00:00
sam self-assigned this 2026-10-27 13:35:01 +00:00
sam closed this issue 2026-10-27 13:35:01 +00:00
sam added a new dependency 2026-10-27 13:41:44 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Reference: sam/archie#118