docs: align release metadata governance wording - #7
Merged
Merged
Conversation
Post-release documentation correction discovered after v1.9.6 publication. Replace stale enforcement wording in process-engine.toml comments with the canonical advisory governance contract: - 'Turnstone governance enforces gates' -> 'Turnstone provides native governance surfaces' - 'relies on Turnstone's native governance for enforcement' -> 'relies on Turnstone's native governance mechanisms; operator approval remains authoritative' Comment-only; no version/engine/lineage/counts change; no runtime artifacts changed; no Turnstone deployment required; v1.9.6 tag/release unchanged.
RedEyeNinja-BKK
commented
Aug 8, 2026
RedEyeNinja-BKK
left a comment
RedEyeNinja-BKK
left a comment
Owner
Author
There was a problem hiding this comment.
Independent final review: PASS. Verified exact head a4045b8, one changed file (process-engine.toml), +3/-2 comment-only governance wording correction, no runtime/product artifact changes, v1.9.6 tag remains immutable at 65eaba8, and exact-head structural-validation run 31270479799 completed successfully. READY FOR POST-RELEASE DOCS MERGE GATE.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
docs: align release metadata governance wording (post-release residue)
Base SHA:
65eaba888322609afa9986ff1d19e959317f5e28(main; released v1.9.6 SHA)Head SHA:
a4045b882923998405a6d6603104ba528008cffcWhat this is
A post-release documentation/metadata residue correction discovered after v1.9.6 publication. Two comment-only statements in
process-engine.tomlretained stale enforcement wording inconsistent with the canonical v1.9.6 governance contract (Turnstone supplies native governance surfaces; prompt policy = durable contextual guidance; judge = advisory evidence; operator approval remains authoritative; Process Engine does not own deterministic enforcement).Changes (comment-only, 1 file)
# Turnstone-native. All logic in prompts; Turnstone governance enforces gates.→# Turnstone-native. All logic in prompts; Turnstone provides native governance surfaces.# The prompt-only engine relies on Turnstone's native governance for enforcement.→# The prompt-only engine relies on Turnstone's native governance mechanisms; operator approval remains authoritative.Scope / non-changes
v1.9.6→65eaba8…is not moved, recreated, or rewritten; this commit is not part of the published v1.9.6 artifact (post-releasemainwill differ after merge).Validation
python3 tools/validate.py --repo .→ STRUCTURAL VALIDATION PASS (canonical 1.9.6, counts 6/7/6, frontmatter, embedded refs == root, links, lineage v8.0).Do not merge.