v1.9.6 release identity + documentation alignment - #4
Merged
Conversation
Release-identity/documentation changes only - no behavioral, tooling, or turnstone changes. Base 16e4cbe (PR #3 merged). - process-engine.toml: version 1.9.5 -> 1.9.6, engine process-engine 1.9.6, header comment v1.9.6. Lineage/counts/compatibility/author unchanged. - 6 skills: frontmatter metadata.version + metadata.engine -> 1.9.6 (bodies unchanged). - README: current version identity v1.9.6 (Origin Story historical 1.9.5 statement kept). - docs/architecture.md: current 'Pipeline gates (v1.9.6)' label. - CHANGELOG: add 1.9.6 entry (Changed / Validated / Evidence qualification); v1.9.5 entry untouched. Structural validation: STRUCTURAL VALIDATION PASS. Remaining 1.9.5 refs are historical (README Origin Story, toml historical comment, CHANGELOG v1.9.5 entry). Reference: #1.
…ate model, generator persona Non-behavioral documentation alignment for v1.9.6 (PR #4): - Governance wording: replace 'enforce gates mechanically' / 'owns the guardrails' / 'enforcement layer' with the advisory contract: Turnstone provides native governance surfaces (prompt policy = durable contextual guidance; advisory judge = review/trial evidence); operator approval is the final authority at the defined gates. README, architecture, standards, governance-usage. - Gate model: architecture now lists the meaningful operator gates (Summary, Review, Trial, Ship) and states not every conversational stage is an approval gate. - Generator vs development persona: README deploying section + architecture components distinguish persona.md as the canonical generator persona (deploy under a distinct generator identity, e.g. process-engine-generator) without encoding private/local object IDs. - governance-usage: durable product contract (Turnstone-native, contextual prompt policy, advisory judge, operator final authority) separated from a dated 'Deployment snapshot - 2026-08-01' (policy/rule IDs, judge counts, model) as mutable operational facts. - spec-compliance.md left unchanged (version-neutral, accurate). - Historical statements (v1.9.5 clean-slate, evidence qualification, case study) preserved as historical. Structural validation PASS. Reference: #1.
RedEyeNinja-BKK
changed the title
RedEyeNinja-BKK
added a commit
that referenced
this pull request
Aug 8, 2026
- Agent Skills eval-methodology: corrected - upstream DOES contain trigger sets, near-misses, with/without baselines, token/timing capture (optimizing-descriptions.mdx, evaluating-skills.mdx @ 217be548); PE adapts it to Turnstone, not PE-only. - Osmani 24-skill: RESOLVED - README @ f4933771 says 'install all 24 skills' + 'All 24 Skills' (23 lifecycle + 1 meta). - Imperative-description: kept as PE authoring standard; formal spec requires non-empty <=1024 what+when only (spec-vs-guidance framing preserved). - Progressive disclosure reclassified as spec guidance/design convention + PE standard (not hard validator requirement). - metadata wording: spec = map from string keys to string values; PE docs 'arbitrary key-value map' -> align (B-class). - Added internal behavioral-contract issue: stale mechanical-enforcement wording in persona.md + core + pattern-author + ship (C-class, small prompt correction before release, opposite of adding enforcement). - Added Triage package-manifest remnant finding (verify; rewrite if none). - Added validator/spec-integrity finding (top-level version; compat<=500; metadata string->string) - small structural fidelity. - OWASP: proportional named security basis confirmed (not universal). - Verdict revised: ALIGNED WITH SMALL DOCUMENTATION/ATTRIBUTION + INTERNAL GOVERNANCE-CONTRACT WORDING CORRECTIONS; PR #4 ready for merge review.
RedEyeNinja-BKK
added a commit
that referenced
this pull request
Aug 8, 2026
- Record PR #4 merge (2511f1a) + PR #6 merge (4808268) + final main 4808268. - Record exact-head structural-validation run 31268609588 (success) on PR #6 head bcab220 (tree identical to reviewed 6705e5f). - Record G1-G6 evidence (comment 5226619712) + final alignment verdict: ALIGNED, merged product matches reviewed v1.9.6 candidate.
RedEyeNinja-BKK
added a commit
that referenced
this pull request
Aug 8, 2026
- Triage manifest remnant: mark historical finding; resolved by PR #6 (explicit historical v1.9.5 state) - satisfies validator historical exemption. - §12: remove stale 'both await operator merge gates in sequence'; actual chain (findings -> PR #6 correction -> senior PASS -> PR #4/#6 merged; PR #5 evidence-only awaits its gate). - '4808268a' framed as reviewed product-candidate main before this evidence-only PR (merging PR #5 advances main without product change). - No product/validator/CI changes.
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.
v1.9.6 release identity + documentation alignment
Branch:
v1.9.6-release-metadataBase SHA (verified before branching):
16e4cbe7151297ac8c659f7fca8bad1ffd05f9dc(main after PR #3)Head SHA:
3d114e58e5e87303868fd3ed6ad073698e8988dcReferences: Issue #1 — v1.9.6 release preparation (identity-correction PR #2 + tooling-hygiene PR #3 + live trials + current-documentation alignment)
Scope
Release identity/documentation changes only. Process Engine behavior is unchanged by this PR. No skill-body changes, no persona prompt changes, no reference/template content changes, no tooling changes, no Turnstone mutation.
Files changed (12)
process-engine.tomlversion = "1.9.6",engine = "process-engine 1.9.6", header comment v1.9.6. Lineage/counts/compatibility/author unchangedskills/*/SKILL.mdmetadata.version+metadata.engine→ 1.9.6 (bodies unchanged)README.mdpersona.md→ deploy asprocess-engine-generator); Origin Story historical v1.9.5 statement keptdocs/architecture.mdprocess-engine-generatordocs/standards.mddocs/governance-usage.mdCHANGELOG.md## 1.9.6 — 2026-08-08entry (v1.9.5 entry untouched)Diff:
12 files changed(metadata + docs only).docs/spec-compliance.mdleft unchanged (version-neutral, accurate).Governance/enforcement wording correction
Replaced "enforce gates mechanically" / "owns the guardrails" / "enforcement layer" across README, architecture, standards, governance-usage with the actual contract: Turnstone provides the native governance surfaces (prompt policy = durable contextual guidance; advisory judge = review/trial evidence); operator approval remains the final authority at the defined gates. No new governance doctrine.
Gate model correction
docs/architecture.mdno longer says "every stage has an operator gate." It now names the meaningful operator gates (Summary Gate, Review, Trial, Ship) and states the pipeline stays conversational between them — consistent with Process Engine's avoid-excessive-ceremony principle.Generator vs development persona
persona.mdis documented as the canonical Process Engine generator persona; the deploying section and components tree say to deploy it under a distinct generator identity (e.g.process-engine-generator) so it does not collide with any development/maintenance persona. No private/local object IDs encoded in public docs.governance-usage.md restructure
Durable product contract (Turnstone-native, contextual prompt policy, advisory judge, operator final authority, generated packages may include governance artifacts) is separated from a clearly labeled "Deployment snapshot — 2026-08-01" holding policy/rule IDs, judge settings counts, output-guard counts, and the observed judge model as mutable operational facts (not timeless architecture; no silent update of mutable values without live evidence).
Version-neutral documents
docs/spec-compliance.md, standards rules, references left version-neutral — "aligned to v1.9.6" means accurate at v1.9.6, not stamped with the version everywhere.Historical statements preserved
v1.9.5 clean-slate story (README Origin Story, CHANGELOG v1.9.5 entry), old CI evidence qualification (CHANGELOG), case-study facts — all preserved as historical; not rewritten to imply v1.9.6 always existed.
Deployment instructions check
README deploying section verified against the actual synchronized generator deployment: generator persona, six skills, seven references/resources, six templates, Turnstone-native governance artifacts, read-back verification — all present and now generator-identity-correct.
Validation
python3 tools/validate.py --repo .→ STRUCTURAL VALIDATION PASS (canonical 1.9.6, counts 6/7/6, frontmatter valid, embedded refs == root, links resolve, lineage v8.0).git diff --stat persona.md references/ templates/empty).1.9.5occurrences all historical/intentional (README Origin Story, toml historical comment, CHANGELOG v1.9.5 entry) — verified by sweep + validator.structural-validationon exact head: PASS (see check-run).Confirmations