ARC 5Own Runtime OperationsChapters 19โ€“22

Arc 5 Recap โ€” Turn Operating Responsibilities into Contracts (Chapters 19โ€“22)

Observability, security, lifecycle, and capacity together form DSM's operating responsibility and directly affect fault detection, isolation, and recovery.

Four operating contracts

Contract Useful question Dangerous substitute
Observability Which identity/locator/origin/reason differs? "Sync looks wrong; restart it."
Security Which admission/authentication/encryption/replay/abuse gate rejected? "Security is enabled."
Lifecycle Which state accepts traffic; when does registry freeze and close? "Spring Context is up."
Capacity Which fixture, environment, and parameters support this trend? "The laptop produced a large number."

How this arc realizes DSM's value

Shared diagnostics, metrics, traces, security gates, and lifecycle reduce repeated platform work across services. Comparable benchmarks identify hot-path regressions. Each target environment still owns alert thresholds, key custody, traffic drain, and production capacity.

A pre-release path

  1. Check RUNNING state, collection registration, and readiness.
  2. Verify that diagnostics, metrics, and traces can locate membership/delta/repair/consumer differences.
  3. Validate token, signature, encryption policy, nonce, abuse limit, and audit outcomes.
  4. Rehearse readiness removal, drain, Runtime close, and incomplete-action records.
  5. Run the target microbenchmark under a pinned revision/environment, retain JSON, and keep smoke separate from SLA.

Still unproven

These gaps become inputs to the Arc 6 E4 lab and final release decision.

Next

Arc 6 adds independent-process/real-port evidence with a Redis-shaped black box, then addresses Federation, alternatives, and the capstone.