Open Framework Commons v1.1.0

Open Framework Commons v1.1.0

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

Summary

Version 1.1.0 recognizes Focus Operating Framework as the fifth independent
product in Commons scope, corrects the public review index, and adds the minimum
community and release surfaces needed to keep future changes inspectable.

The shared principles and boundaries are unchanged. Commons remains
documentation, every product remains independent, and no Commons release
automatically changes a product.

Scope decision

Decision 0001
records the Charter amendment. Focus v1.0.0 already adopted Commons v1.0.0 while
explicitly deferring membership to a separate Commons decision. This release
makes that decision and synchronizes all complete product lists,
shared-applicability tests, the ecosystem diagram, and stable adoption links.

Focus remains pinned to Commons v1.0.0 until its own governance adopts a later
release.

Review-record corrections

• The review index now distinguishes the visualization content candidate from
  the PR #2 squash merge that published the candidate and review record.
• The obsolete v1.0.0 pin is replaced with the commit currently peeled from the
  annotated tag.
• The 2026-08-02 reports are explicitly framed as point-in-time draft reviews;
  their historical contents remain unchanged.

Repository stewardship

• Added contributor guidance, conduct expectations, a security policy,
  citation metadata, release history, ownership routing, one issue form, and a
  pull-request template.
• Added a machine-readable version and validation that keeps versioned surfaces,
  local links, scope references, citation metadata, Mermaid fences, and public
  hygiene synchronized.
• Added restrained repository topics and enabled private vulnerability
  reporting.
• Retained the LICENSE filename because GitHub recognizes both common license
  names and the ecosystem has no consistent alternative.

Compatibility

This is a backward-compatible scope addition, so the minor version increases
from 1.0.0 to 1.1.0. The v1.0.0 tag, release, and downstream adoption records
remain unchanged. Existing adopters do not need to update unless they
independently choose to adopt v1.1.0.

Verification

Release verification uses these gates:

• ./scripts/validate-repository.sh checks shell, Ruby, YAML/CFF loading, local
  links and anchors, synchronized five-product scope references, Mermaid fences,
  and publication hygiene.
• uvx --from cffconvert cffconvert --validate validates CITATION.cff against
  the CFF 1.2 schema.
• Mermaid CLI 11.16.0 compiles every tracked Mermaid diagram for visual review.
• Gitleaks scans the complete staged release diff with redacted output.
• ./scripts/validate-release.sh v1.1.0 verifies the clean merged commit and
  matching local and remote annotated tag plus the published release state.
• Authenticated GitHub API readback verifies public identity, metadata, issue
  dispositions, and exact release content.

This verification establishes documentation and publication integrity. It does
not claim real-world effectiveness for Commons or any ecosystem product.