Relationship Operating Framework v1.1.0

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.

Relationship Operating Framework v1.0.0

Relationship Operating Framework v1.0.0

This owner-authorized same-version documentation republication adds the missing framework visualization layer and preserves the coordinated Open Framework Commons v1.0.0 adoption refresh. It does not change the Relationship method, authority, or product boundary.

What changed

• Added eight inline Mermaid diagrams across six documents: repository orientation, stewardship concerns, practical decision checks, human and assisting-agent authority, learning without relationship scoring, and the three fictional examples.
• Added visualization guidance to contribution, governance, and repository instructions so future diagrams must clarify meaning without creating a lifecycle, score, system, or product architecture.
• Preserved people-first stewardship, contribution without debt, non-transactional re-engagement, continuity, commitments, consent, context, repair, and accountable human judgment.
• Preserved the prohibition on autonomous agent contact, scoring, manipulation, promises, or transactions.
• Published sanitized practical, adversarial, coherence, public-hygiene, Commons-adoption, correction, integration, and disposition records.

Commons adoption

• Commons tag: v1.0.0
• Commons annotated-tag object: d1303411ea67768ee2fee5dfb21e82c2e8599a3a
• Original Commons pin: 27870fb1d57d951b9ef5a3a86f33ef068ee557da
• Current exact Commons pin: a0f0d384e9010a65d1a21a324b4c912433d5e031

Relationship remains independent and owns its local method, terminology, examples, research, governance, and releases. It remains distinct from the Influence Operating Framework.

Review and release integrity

• Framework candidate: fec214099ea6479a675529b85657f429a6e3b3b5
• Framework candidate tree: 5d7b9ada117c0b6f685fec4cadf234acdd08d9ae
• Corrected integration candidate: 810bcbf46ecb3542a837dee5022be14d38c43476
• Corrected integration tree: bf9ac56af20b39d13aeeb205c2d7d8232e98a7f9
• Pull-request branch head: 35d220d733492400dfc950751cffd1ec53a8e673
• Pull-request branch tree: 6d6e3ad4622a5b445bc13735400fc4af32b73dd0
• Exact merged and released commit: 0c90cb23ccb5fd4616ae3c6dac86216cbfd69d36
• Merged tree: 6d6e3ad4622a5b445bc13735400fc4af32b73dd0, exact branch-tree match
• Replacement annotated-tag object: 4ad69305234c0da7cf6ab903e1f1fe0157cc4976
• Pull request: #6
• Release issue: #4

Practical, adversarial, canonical-coherence, and public-hygiene reviews against the exact merged commit returned GO with no open findings. Earlier review passes found one Material same-version provenance gap and one Minor tool-specific wording issue; both findings remain visible, were corrected, and passed affected-review reruns.

Validation confirmed eight rendered diagrams, 48 local links and heading targets across 31 Markdown documents, 10 external destinations, 110 review evidence references, valid citation metadata, documentation-only file modes, and no detected credentials in repository history.

Same-version provenance

• Original Relationship tag object 24290489bd59fb80d27a16c8360b1f41263310f9 peeled to original release commit ce7957143aa5eb3860b2fe81b63ec62a8857dbfb.
• The coordinated Commons-refresh replacement tag object b8d135dc6ab267a2a07fead0f55668ccd007ca72 peeled to intermediate release commit 6a255a8ded7d4cb86a9584b46e7694213019264f.
• This visualization republication replaces that tag object and peels to merged release commit 0c90cb23ccb5fd4616ae3c6dac86216cbfd69d36.

This is a bounded owner-authorized correction to the first documentation release. Immutable tags remain the normal release rule.

Known limits

No longitudinal real-world validation or certification. Examples are fictional and not domain-validated. No legal, privacy, safeguarding, organizational, professional, implementation, or accessibility certification. First-user, first-job, lifecycle, domain-model, Mission Control, and extension ideas remain proposals. The release contains no scripts, automation, CI, schemas, generated visual exports, or machine-readable conformance layer.