alknet/tasks/architecture/adr-034-head-worker-terminology.md at 835724d08748d50390553c69df04a664043a8397

Files

glm-5.1 19b3d3a078 docs: write Phase 0 architecture foundation — ADRs 026-034, spec docs, and task updates

Phase 0a — ADRs (9 new):
- ADR-026: Transport/interface separation (three-layer model)
- ADR-027: Crate decomposition (core, secret, storage, flowgraph, napi, CLI)
- ADR-028: Auth as irpc service (AuthProtocol behind feature flag)
- ADR-029: Identity as core type (Identity + IdentityProvider in alknet-core)
- ADR-030: Static/dynamic config split (ArcSwap, ConfigReloadHandle)
- ADR-031: Forwarding policy (rule-based allow/deny, TransportKind-aware)
- ADR-032: Event boundary discipline (domain, irpc, call protocol boundaries)
- ADR-033: OperationEnv universal composition (three dispatch paths)
- ADR-034: Head/worker terminology (replace hub/spoke)

Phase 0b — New spec documents (7):
- identity.md, services.md, interface.md, configuration.md,
  storage.md, flowgraph.md, secret-service.md

Updated existing docs:
- auth.md: reference identity.md for canonical definitions, add AuthProtocol
- open-questions.md: resolve OQ-12, OQ-16, OQ-18, OQ-22, OQ-23-25
- README.md: add all new docs, ADRs 026-034

Marked 19 architecture tasks as completed.

2026-06-07 09:32:58 +00:00

1.7 KiB

Raw Blame History

id, name, status, depends_on, scope, risk, impact, level

name

status

depends_on

scope

risk

impact

level

architecture/adr-034-head-worker-terminology

Write ADR-034 — Head/worker terminology

completed

single

trivial

project

implementation

Description

Write ADR-034 formalizing the decision to use head/worker terminology instead of hub/spoke throughout the project.

This decision has already been applied in practice — call-protocol.md, auth.md, open-questions.md, and napi-and-pubsub.md were all updated to head/worker. The existing ADRs (024, 025) retain their original hub/spoke language because ADRs are historical records. ADR-018 is noted as superseded/extended by ADR-024 and the three-layer model.

The ADR exists to formally record the decision so future contributors understand why and can reference it.

Acceptance Criteria

docs/architecture/decisions/034-head-worker-terminology.md exists
ADR follows the established format (Status, Context, Decision, Consequences, References)
Context explains why hub/spoke is being replaced (mesh topologies, a head is also a worker)
Decision states: head/worker everywhere in new specs and code; ADRs retain original language as historical records
Consequences note: natural mesh formation, consistency with integration plan terminology
References: integration-plan.md, ADR-024, ADR-025

References

docs/research/integration-plan.md — Phase 0 ADR 034 entry, inconsistencies section item 1
docs/architecture/decisions/024-bidirectional-call-protocol.md — uses hub/spoke historically
docs/architecture/decisions/025-handler-spec-separation.md — uses hub/spoke historically

Notes

To be filled by implementation agent

Summary

To be filled on completion

1.7 KiB Raw Blame History