Record intentional editorial acceptance across modules
This commit is contained in:
@@ -2,7 +2,7 @@
|
||||
|
||||
**Base Policy Version:** 1.3
|
||||
|
||||
**Last Updated**: 2026-09-28
|
||||
**Last Updated**: 2026-11-11
|
||||
**Upstream Source:** [Standard Repository Policies architecture](https://gitea.maximumdirect.net/eric/policy/src/commit/d84a38ebab26f048cafbe59a2246700c35d29843/docs/policy/architecture.md)
|
||||
|
||||
## Purpose And Ownership
|
||||
@@ -72,6 +72,12 @@ hidden global state.
|
||||
|
||||
## Correction and Concurrency Invariants
|
||||
|
||||
- Module focus guides proposal generation; it is not an exclusive acceptance
|
||||
boundary. Validators permit otherwise acceptable minor editorial cleanup even
|
||||
when the originating module did not request it. Existing applicability,
|
||||
protection, and meaning checks still apply. See
|
||||
[ADR 0003](../adr/0003-module-focus-and-editorial-acceptance.md) for the empirical
|
||||
rationale and rejected strict-scope alternative.
|
||||
- Treat LLM responses as nondeterministic inputs. Preserve deterministic proposal
|
||||
indexing, validator ordering, transcript mutation, reports, and serialization.
|
||||
- Validate corrections before final mutation, including local proposal checks,
|
||||
|
||||
Reference in New Issue
Block a user