docs: rewrite IncrementalSync + AddressSpace for v3, fix driver-specs/driver-stability tier claims, update Secrets runbook for pair replication + KEK rotation (#623)

Claude-Session: https://claude.ai/code/session_01Ef2ozxS7QPanGT8uoATbTe
This commit is contained in:
Joseph Doherty
2026-10-08 08:13:14 -04:00
parent a702875d41
commit 90bfcbe47a
7 changed files with 239 additions and 210 deletions
+4
View File
@@ -49,6 +49,10 @@ Driver stability needs to be a first-class architectural concern, not a per-driv
Every driver is assigned to one of three tiers based on the trust level of its dependency stack:
> **Design intent, not the shipped assignment.** The per-driver tier tables below record the proposed
> assignment (Galaxy/FOCAS in Tier C, the Ab/S7/TwinCAT drivers in Tier B). As shipped every driver is Tier A —
> see the banner above and `docs/drivers/README.md`, which is the accurate reference.
### Tier A — Pure Managed
Drivers whose entire dependency chain is verifiable .NET. Standard exception handling and Polly are sufficient. Run in-process in the main server.