Governance Policy
Explains how SORF is stewarded, how decisions are documented, and how the framework protects independence and transparency.
Read policyGovernance
How SORF is stewarded.
SORF is an independently stewarded public documentation framework. Its governance exists to protect transparency, review quality, official releases, contributor trust, and the long-term usefulness of the framework.
Current status
Early public draft, not a formal standards body.
SORF is not currently a government standard, accredited standards body, certification program, membership association, charity, UK CIC, or formal professional advisory service.
It is an independently stewarded public framework that is being developed through documented governance, version history, public review records, and official releases.
Governance documents
The official policies live in the SORF repository.
The website provides a readable overview. The GitHub repository preserves the official governance record, including policies, changelog entries, release process, issue history, and public review activity.
Change Review Method
Explains how suggestions are reviewed before becoming part of the official framework.
Read methodReview Record Policy
Explains how feedback, review IDs, decisions, contributor permissions, and public review history are recorded.
Read policyRelease Process
Explains how official SORF versions are prepared, labeled, published, and referenced.
Read processBrand Policy
Explains how the SORF name, official status, modified versions, translations, and endorsement boundaries should be handled.
Read policyDisclaimer
Explains SORF’s educational boundaries and why it should not be treated as professional advice.
Read disclaimerStewardship
SORF is stewarded, not treated as a static document library.
SORF is maintained through a documented process. Significant changes should be traceable through issues, review records, commits, changelog entries, release notes, or other official repository records.
The goal is for users and future reviewers to understand not only what changed, but why it changed.
Transparency
Significant changes should be documented so users can understand the development history of the framework.
Independence
Contributors, reviewers, supporters, donors, sponsors, or outside organizations do not automatically receive authority over SORF.
Public benefit
SORF should remain focused on helping small organizations improve practical records, continuity, and responsible documentation habits.
Review process
Suggestions are reviewed before becoming official.
SORF welcomes practical feedback, but not every suggestion can or should become part of the official framework.
Suggestions are reviewed for usefulness, safety, clarity, evidence, scope fit, consistency with the framework, and benefit to small organizations.
Public feedback and review activity are handled through the official SORF GitHub repository so decisions can be documented and traced over time. Contribution does not imply endorsement, certification, approval, partnership, or formal representation of SORF.
Official releases
Official versions are published through GitHub.
Official SORF releases should be published through the official SORF repository and GitHub Releases when practical. The website may explain and link to official releases, but the repository preserves the versioned development record.
Official repository
View the source files, policies, changelog, issues, and public development history.
Open repositoryLatest release
Download the latest official SORF release package when available.
View releaseAll releases
Review previous SORF releases, release notes, and downloadable files.
View releasesProject boundaries
SORF does not certify, audit, approve, or verify organizations.
SORF does not determine whether an organization is compliant, secure, legally prepared, financially prepared, operationally resilient, properly insured, or correctly governed.
Organizations remain responsible for deciding whether SORF materials are appropriate for their situation and for seeking qualified professional guidance where needed.
Future governance
The governance model may mature over time.
As SORF grows, future governance may include advisory reviewers, editorial reviewers, working groups, educational advisors, institutional partners, fiscal support structures, or a more formal stewardship organization.
Any future governance changes should be documented through the official repository and should strengthen transparency rather than add unnecessary complexity.