Operating record · Corrections
A no-fit case can correct the framework or its translation.
Corrections should preserve what changed, why it changed, and which canonical or public records depend on the decision.
What belongs in the correction path
- Factual or source error
- Canonical version mismatch
- Interpretive overreach
- Safeguarding or consent concern
- Accessibility barrier
- Privacy or data-behavior concern
- Attribution or visual-provenance problem
- Broken route, metadata, or technical defect
Public correction pattern
- 01
Receive the exact route, issue, and requested review without requiring intimate context.
- 02
Classify the issue and identify affected public and canonical records.
- 03
Review evidence, no-fit examples, conceptual dependencies, and safeguarding impact.
- 04
Decide and record the change, non-change, uncertainty, version, and rationale.
Correction channel · Ordinary email
Report a correction or access problem.
Email hello@neurosexuality.org with the affected Neurosexuality page or record and the issue where possible. Attribution is optional, a personal history is not required, and sensitive records should not be sent through ordinary email.
This founder-led forwarding address routes Neurosexuality correspondence to the project inbox. Messages may be kept while relevant to the conversation, correction history, project administration, safety, or legal obligations, then removed when no longer needed. No fixed retention period, guaranteed response time, anonymous delivery, or crisis monitoring is promised.
Open a correction emailPage record
Status, sources, and boundary
- Record
- NSX-GOV-CORRECTIONS-001
- Version
- 0.3
- Last revised
- 2026-08-12
- Boundary
- The Neurosexuality correction address is ordinary founder-led forwarding email, not research intake, a secure reporting service, or crisis monitoring.