Influence Operating Framework v1.0.2

Summary

Version 1.0.2 removes the two remaining release-integrity caveats from v1.0.1 without changing canonical framework meaning or rewriting prior release history.

Changed

• Added a dedicated GitHub-registered Ed25519 release-signing identity and tracked only its public allowed-signers entry.
• Added scripts/validate-release.sh, which requires a clean worktree and complete Git history.
• Required signed annotated version tags that verify against the tracked public key and resolve exactly to the released commit.
• Kept ordinary shallow-clone contributor validation useful with explicit partial-history reporting.
• Updated CI to exercise the full-history release gate and fail closed for shallow release validation.
• Synchronized VERSION, CITATION.cff, the changelog, governance baseline, charter status, release record, and review records at 1.0.2.

Release identity

• Signed annotated tag: v1.0.2
• Tag object: 9aaf9341b88b6e6c5475ba3eb0d9356255d42ed9
• Released merge commit: cc5a25d3523a33347c75644d4f41920822cb12f5
• Signing-key fingerprint: SHA256:EKmFG8TU58Rz+2TGF/Wu4N3PmLu2+zcNFhhKhvI9k3Q
• GitHub signature result: verified and valid

Only the public key is committed. The private key remains outside the repository with restrictive local permissions.

Verification

• Complete-history release gate passed on the candidate and merged main.
• Repository checks passed: 37 required files, 59 Markdown documents, 119 local links and anchors, 28 review records, 210 historical citations, and 40 public-history commits after merge.
• Mermaid rendering passed 8/8.
• Depth-1 contributor validation passed with explicit partial-history reporting.
• Depth-1 release validation failed with actionable unshallow guidance.
• Independent repository-standards review: GO, zero findings.
• Independent issue-requirements review: GO, zero findings.
• Pull-request, merged-main, and signed-tag workflows passed.
• The merged tree exactly matches the PR head tree, and the exact reviewed commit remains reachable.

Compatibility and limits

Open Framework Commons v1.1.0 adoption remains unchanged. This patch affects release stewardship only; it does not change the six concerns, seven practice moves, responsible-practice standard, measurement guidance, glossary, or examples.

Signature verification establishes control of the registered signing key. It does not establish real-world, organizational, legal, ethical, accessibility, professional, or domain validation.

Closes #13.

Influence Operating Framework v1.0.1

Influence Operating Framework v1.0.1

• Release date: 2026-08-22
• Type: Patch, documentation and repository maintenance
• Previous release: v1.0.0

Summary

Version 1.0.1 adopts Open Framework Commons v1.1.0 and corrects validation in shallow Git clones. It changes no canonical Influence framework meaning.

Open Framework Commons v1.1.0

• Annotated tag object: 79e5f06dab46f262cad1d1daf7840e683ffc3880
• Peeled release commit: f25a2b89b4aed95984fd235e2e229efe52c125d8
• Adopted: all nine unchanged shared principles and all shared boundaries, including recognition of Focus Operating Framework as the fifth equal, independent product
• Deferred: Mission Control, community-extension topics, and product-local guidance
• Deviations: none

Influence retains independent authority over its concerns, method, terminology, examples, research, governance, roadmap, implementation choices, and releases.

Validation correction

A depth-1 clone previously emitted 194 false errors when historical reviewed commits were unavailable. Validation now keeps current-tree and reachable-history checks active, reports unavailable coverage once, and directs release work to git fetch --unshallow for complete historical assurance. Full clones remain strict for missing reviewed commits and invalid citations.

Historical review citations to underscored script filenames were audited and preserved because those paths are correct at their exact reviewed commits. Issue #9 was closed with that evidence; issue #10 was resolved by PR #12.

Review and verification

• Reviewed candidate: c58ab80437e0cf91b191fb48285bb1883ceba76d
• Standards review: GO, zero open findings
• Specification review: GO, zero open findings
• PR #12 merged with commit preservation at f24f3b4c5b50b8fbf2dd89850969fe8017813c8c
• Merge tree exactly matches the PR head tree
• Full-history gate: 56 Markdown documents, 115 local links and anchors, 26 review records, 192 historical citations, 36 public-history commits, 70 publication-scanned text files, and 8 rendered Mermaid diagrams
• Depth-1 gate: current-tree and reachable-history PASS with 21 unavailable review commits and 192 unavailable citations reported explicitly
• Pull-request, merged-main, and annotated-tag workflows: PASS
• Annotated v1.0.1 tag object: 1f3521e1fc4e1f4643f2e687afd7d50dfa94bf33, peeling exactly to the merged commit

Compatibility and limits

This patch does not change the six concerns, seven practice moves, responsible-practice standard, measurement guidance, glossary, or examples. Shallow-clone success does not establish complete historical assurance. Repository review does not establish real-world, organizational, legal, ethical, accessibility, professional, or domain validation.

Influence Operating Framework v1.0.0

Influence Operating Framework v1.0.0

Version 1.0.0 is the complete public release of an open, human-first business operating framework for building meaningful influence through useful contribution, trusted relationships, accountable judgment, and continuous learning.

This owner-authorized coordinated republication updates the adopted Open Framework Commons v1.0.0 exact commit while preserving Influence as an independent framework.

Open Framework Commons adoption

• Commons tag: v1.0.0
• Original Commons pin: 27870fb1d57d951b9ef5a3a86f33ef068ee557da
• Current exact Commons pin: a0f0d384e9010a65d1a21a324b4c912433d5e031
• Adopted: all nine shared principles and shared boundaries
• Deferred/product-local: topics owned by Influence or another ecosystem product
• Deviations: none

The refreshed Commons visual guides and active-product status do not change the Influence concerns, method, terminology, examples, research, governance, roadmap, implementation choices, release authority, or stronger human-judgment safeguards.

What ships

• Charter, six canonical concerns, seven-move practice method, responsible-practice standard, measurement guidance, glossary, and three fictional application examples
• Eight focused inline Mermaid views across the framework and examples
• Governance, contribution, conduct, security, citation, decision, and sanitized review records
• Explicit Commons discovery and product-independence boundaries

Review and verification

• Corrected adoption candidate: f3ed7635f9c3231fe1a0b112fd24c0eac3fa03e7
• Standards: GO with no open findings after one Minor release-history correction
• Specification: PASS with no findings
• Full reviewed publication tree: 99d7adf0ade6cd052897ff8f2a76846e55eb8c53
• First merge: 1db36dcf943bae00af25eaa532fbbce87bb767ff, exact tree match
• Review-anchor follow-up merge: adefdfe5d68c802f5c0b904c1ec36d96db409a32, exact tree match
• Final local gate: 51 Markdown documents, 106 local links and anchors, 24 standardized review records, 175 historical citations, 65 publication-scanned text files, and 8 rendered Mermaid diagrams
• Pull-request and final main-branch workflows: PASS

Release history

Prior annotated v1.0.0 targets remain public history:

• original: 7d4727a8cf889d621e45854c874a5e0a15a94a56
• Commons adoption: f91851a1b42b28b01928e5db7aaac4c20b946417
• visualization refresh: cbe41ccd84f2027f58ae7938df09131b5fbde3ca
• final coordinated Commons-pin release: adefdfe5d68c802f5c0b904c1ec36d96db409a32

Known limitations

Examples are fictional and not domain-validated. Review records are source-bounded review evidence, not organizational, legal, ethical, professional, domain, accessibility, or real-world validation. Adoption still requires local authority and practical feedback.