Last updated: June 22, 2026
This website address is: https://osloadarchitecture.com.
Purpose of this site
OS Load Architecture is a public information and publication-access site for the work OS Load Architecture: Constraint, Contradiction, and Collapse in Finite Human Systems.
This site is not a therapy, coaching, diagnostic, assessment, or personal-classification service.
Information submitted through the RFC form
The RFC / Correction Intake form may collect:
- name
- email address
- canonical version referenced
- primary scope
- additional scope fields, if provided
- RFC type
- submission text
- boundary confirmation
- public log consent selection
RFC submissions are used for correction review, citation review, terminology review, boundary clarification, version review, misuse-risk review, and periodic release-cycle assessment.
Individual responses are not guaranteed. Submissions may be reviewed in aggregate during periodic release cycles.
RFC submissions do not modify the canon. Canonical changes occur only through formal version release or documented errata.
Email contact
If you contact the site by email, your email address and the content of your message may be retained as part of normal correspondence records.
General contact should use:
RFCs, corrections, citation issues, terminology concerns, structural critiques, misuse-risk flags, and boundary-review items should use:
RFC recordkeeping
This site currently uses WPForms Lite. Form entries are not stored inside the WordPress dashboard.
RFC submissions are delivered by email to [email protected].
Selected RFCs may be manually entered into an internal RFC review ledger for tracking, triage, release-cycle review, and correction-history control.
The internal ledger may include submitter name, submitter email, canonical version, scope, RFC type, summary, consent selection, status, disposition, notes, and version affected.
Public RFC summaries
RFC submissions may be summarized publicly only according to the public log consent selected by the submitter and only after review.
Raw submissions, submitter email addresses, and private review notes are not intended for public posting.
If a submission is marked for private review only, it will not be knowingly published as a public RFC summary.
No comments or user accounts
This site does not currently use public comments, public user registration, discussion forums, membership accounts, or public profile pages.
If those functions are enabled later, this policy will be updated before or when they become active.
Cookies and login data
Public visitors do not need an account to use this site.
WordPress may use cookies for administrative login, site security, spam prevention, or basic site functionality. Cookies are small text files used by websites for functions such as remembering login state or supporting site operation.
Administrative users may receive additional WordPress login cookies when accessing the site dashboard.
Server logs and technical data
The site host, WordPress installation, security tools, plugins, and related infrastructure may collect routine technical data such as IP address, browser type, device information, access time, referring page, requested URLs, and error logs.
This information is used for site operation, security, troubleshooting, spam prevention, and abuse prevention.
Third-party services and plugins
This site may use hosting, WordPress, WPForms, email, caching, security, analytics, or administrative plugins to operate the site.
These services may process technical data or form-related data as needed to provide site functionality.
No sale of personal data
This site does not sell personal data.
No therapy or emergency channel
This site is not monitored as a clinical, therapeutic, emergency, crisis, or support channel.
Do not use the RFC form or contact addresses for emergency communication, therapy requests, diagnosis, coaching, personal OS-level classification, or requests to apply the framework to a person.
Data retention
RFC submissions, email messages, and internal ledger entries may be retained as long as needed for publication administration, correction history, version control, misuse-risk review, legal recordkeeping, security, or archive integrity.
Requests
For privacy-related questions, use:
Requests may be limited by administrative, legal, security, archival, or publication-record requirements.
Changes to this policy
This policy may be updated as the site changes, including if download links, print ordering links, analytics tools, user accounts, public comments, public RFC logs, or additional publication infrastructure are added.