docs(config): correct OtOpcUa draft-validation description
The C# DraftValidator/DraftSnapshot has NO live caller in OtOpcUa src/ (verified repo-wide) — it is dormant complement code. The enforced pre-publish draft validation runs DB-side in the sp_ValidateDraft stored procedure (Status='Draft' -> sp_PublishGeneration lifecycle). Reframe across current-state/SPEC/GAPS/README/ CLAUDE.md from 'runtime draft validation' + a false publish-pipeline caller to 'dormant managed validator; enforcement is DB-side'. Out-of-scope conclusion for ZB.MOM.WW.Configuration is unchanged.
This commit is contained in:
@@ -91,8 +91,9 @@ drift — adoption here is *additive*, optional, and the lowest-stakes of the th
|
||||
|
||||
### §6 Draft validation is out of scope (no gap)
|
||||
|
||||
OtOpcUa's `DraftValidator` / `DraftSnapshot` (runtime draft/snapshot validation of operator config
|
||||
*content*) is **not** options/config validation and is explicitly out of the shared library's scope
|
||||
OtOpcUa's draft/generation-content validation (the dormant C# `DraftValidator` / `DraftSnapshot`,
|
||||
plus the live DB `sp_ValidateDraft` it complements — validating operator config *content*) is
|
||||
**not** options/config validation and is explicitly out of the shared library's scope
|
||||
(SPEC §0). It is **not a gap** and requires **no change** on adoption — listed here only to record
|
||||
that it was considered and deliberately excluded.
|
||||
|
||||
@@ -117,8 +118,9 @@ externally-observed contract (metric label, dashboard, wire format) changes.
|
||||
|
||||
## Decisions settled (no longer open)
|
||||
|
||||
- **Draft validation excluded (SETTLED):** OtOpcUa's `DraftValidator`/`DraftSnapshot` is runtime
|
||||
config-content validation, not startup options validation, and stays per-project. See SPEC §0 and
|
||||
- **Draft validation excluded (SETTLED):** OtOpcUa's draft/generation-content validation
|
||||
(DB-side `sp_ValidateDraft`; the C# `DraftValidator`/`DraftSnapshot` is dormant, no `src/` caller)
|
||||
is config-content validation, not startup options validation, and stays per-project. See SPEC §0 and
|
||||
[`current-state/otopcua/CURRENT-STATE.md`](current-state/otopcua/CURRENT-STATE.md).
|
||||
- **`ConfigPreflight` message envelope pinned (SETTLED):** the library reproduces ScadaBridge's
|
||||
`StartupValidator` envelope byte-for-byte (`InvalidOperationException`,
|
||||
|
||||
Reference in New Issue
Block a user