alknet/tasks/architecture/adr-030-static-dynamic-config-split.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

2.3 KiB

Raw Blame History

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

name

status

depends_on

scope

risk

impact

level

architecture/adr-030-static-dynamic-config-split

Write ADR-030 — Static/dynamic config split

completed

narrow

low

phase

implementation

Description

Write ADR-030 establishing the split between StaticConfig (immutable after startup) and DynamicConfig (hot-reloadable at runtime) in alknet-core.

This is largely a promotion from the well-analyzed research in docs/research/configuration.md. The ADR records why this split matters, what goes in each config, and how reload works.

Key points:

StaticConfig: transport mode, listen addr, TLS config, iroh config, host key, stealth mode, max auth attempts, max connections per IP — everything that requires socket/TLS renegotation to change
DynamicConfig: auth policy (authorized keys, cert authorities), forwarding policy, rate limits — everything checked per-connection or per-channel
ArcSwap for lock-free hot reload of DynamicConfig
ServeOptions builder pattern is preserved; StaticConfig is constructed from ServeOptions
TOML config file is an optional convenience input format (amends ADR-011, doesn't replace programmatic API)
ConfigReloadHandle with reload(DynamicConfig) method
NAPI exposes reloadAuth(), reloadForwarding(), reloadAll() on AlknetServer

Acceptance Criteria

docs/architecture/decisions/030-static-dynamic-config-split.md exists
ADR follows established format
Context explains the three failures: no hot reload of auth, no forwarding policy, no structured config beyond CLI flags
Decision states: StaticConfig vs DynamicConfig split; ArcSwap for DynamicConfig; ServeOptions preserved as builder; TOML as optional convenience; ConfigService wraps reloads; amends ADR-011
Lists what's in StaticConfig and what's in DynamicConfig
Consequences: auth and forwarding can be reloaded without restart; config file users get TOML format; programmatic-first API preserved
References: research/configuration.md, ADR-011

References

docs/research/configuration.md — full analysis, nearly spec-ready
docs/architecture/decisions/011-no-ssh-config-programmatic-api.md — programmatic-first decision (amended, not superseded)
docs/research/integration-plan.md — ADR 030 entry, Phase 1.1

Notes

To be filled by implementation agent

Summary

To be filled on completion

2.3 KiB Raw Blame History