Official SORF repository
View framework files, templates, examples, governance documents, changelog entries, issues, and public development history.
Open repositoryFramework areas
SORF framework guidance lives in the official repository.
The website introduces the framework areas and helps visitors find the right materials. Official SORF framework guidance is maintained in the GitHub repository so version history, review records, and source files stay traceable.
SORF framework guidance is provided for educational and organizational planning purposes. It is not legal, tax, financial, accounting, insurance, cybersecurity, regulatory, compliance, governance, or professional advice.
Official source
Use GitHub for the current framework files.
The official framework documents are stored in the SORF repository. This helps users verify the current version, review changes, and see how the framework develops over time.
Download latest release
Download the latest official SORF release package from GitHub Releases when available.
View releasesSubmit framework feedback
Use GitHub Issues to submit clarity suggestions, safety concerns, professional review notes, or proposed improvements.
Go to IssuesCurrent framework areas
Read the official guidance files.
These six areas form the first SORF framework set for small organizations.
Vendor Inventory
Understand how to document vendors, services, subscriptions, tools, providers, and outside relationships your organization depends on.
Read on GitHubAccess References
Learn how to document where access is managed without recording passwords, API keys, recovery codes, private keys, seed phrases, or other secret values.
Read on GitHubResponsibility Records
Clarify who owns, maintains, reviews, and supports important records, systems, vendors, services, and recurring processes.
Read on GitHubContinuity Notes
Preserve practical handoff context if a founder, owner, maintainer, director, board member, staff member, or key person becomes unavailable.
Read on GitHubIncident Timeline
Record neutral timeline notes during outages, disruptions, vendor issues, access problems, public communication errors, or operational incidents.
Read on GitHubReview Routines
Keep documentation useful through simple, realistic review habits that match the organization’s size, capacity, and risk level.
Read on GitHub