Skip to content

Relationship Operating Framework v1.1.0

Latest
Latest

Choose a tag to compare

View all tags
@BradGroux BradGroux released this 23 Aug 00:41
v1.1.0
afa195b
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Relationship Operating Framework v1.1.0

  • Release date: 2026-08-22
  • Type: Minor, documentation-only
  • Previous release: v1.0.0
  • Release PR: #9

Summary

Version 1.1.0 adopts Open Framework Commons v1.1.0 and adds the minimum repository-stewardship surfaces needed to keep future changes inspectable. Relationship remains an independent, people-first documentation framework. Its method, human ownership of relationship judgment and external action, agent limits, and separation from Influence are unchanged.

Commons adoption

Relationship independently adopts Open Framework Commons v1.1.0 with no deviations.

  • Annotated Commons tag object: 79e5f06dab46f262cad1d1daf7840e683ffc3880
  • Peeled Commons release commit: f25a2b89b4aed95984fd235e2e229efe52c125d8

Commons v1.1.0 recognizes Focus Operating Framework as the fifth independent product and adds repository-stewardship surfaces. Shared principles and evidence boundaries are unchanged from Commons v1.0.0. This adoption does not import Focus guidance or Influence doctrine.

Repository audit

  • Added minimal owner routing, one issue form, a pull-request template, and hosted validation. CODEOWNERS routes review but does not itself enforce branch protection.
  • Added prospective decision records and Decision 0001 for this Commons adoption. No retrospective v1.0.0 decisions were fabricated.
  • Added canonical framework and release indexes, a machine-readable version, restrained ignore rules, and repository topics.
  • Added repository, Mermaid, and release-integrity validation.
  • Declined the alleged dead script reference in issue #7 because the v1.0.0 contributor guide contained no such reference. Validation is a prospective v1.1.0 addition.
  • Preserved historical v1.0.0 records, tag, and release unchanged.

Verification

  • Merged commit: afa195b576cfd35b219e9d905cd013af6fc265b7
  • Merged and reviewed tree: ab1b21a48960ba7b0da44cc3a3d6f221c54315b2
  • The merged tree exactly matches the final reviewed pull-request tree.
  • Hosted validation passed on the pull request and merged main tree.
  • Repository validation covered 43 Markdown files, every local link and heading target, synchronized release metadata, exact Commons provenance, file modes, and publication hygiene.
  • All 13 external destinations returned successful responses.
  • Citation metadata passed the CFF 1.2 schema.
  • Nine diagrams across seven documents compiled and received visual inspection.
  • The complete release change passed patch-integrity and redacted secret checks.
  • Independent repository-standards and issue-specification reviews passed.
  • Practical, adversarial-misuse, canonical-coherence, and public-hygiene reviews returned GO with zero findings.

Compatibility and limits

This backward-compatible release changes Commons adoption and repository stewardship, not Relationship practice. It does not establish real-world effectiveness, consent, legal compliance, professional fitness, or certification. Existing v1.0.0 adopters can continue using that immutable release.

Assets 2
Loading