Protective Computing — Curation Policy
Version: 1.1
Effective: February 26, 2026
Community URL: https://protective-computing.github.io
1. Scope and Authority
The Protective Computing community curates scholarly and technical work related to systems design under conditions of human vulnerability.
This community functions as the archival and standards repository for the Protective Computing Canon, including:
• The Overton Framework (Foundational Theory)
• The Field Guide to Trauma-Informed Software Architecture (Operational Translation)
• The Protective Legitimacy Score (Measurement & Audit)
All accepted records must demonstrate substantive engagement with one or more Protective Computing principles:
PC-1: Reversibility
PC-2: Exposure Minimization
PC-3: Local Authority
PC-4: Coercion Resistance
PC-5: Degraded Functionality
The purpose of curation is not volume, but integrity. This community prioritizes rigor, reproducibility, and safety relevance.
2. Submission Eligibility
Records must meet at least one in-scope criterion.
2.1 In-Scope Content
Framework Specifications
Canonical framework releases, revisions, or formal extensions.
Implementation Artifacts
Source code, control matrices, architectural documentation, configuration templates, or verification harnesses demonstrating application of PC principles.
Case Studies
Structured analyses of real systems, including explicit mapping to PC controls and, where applicable, Protective Legitimacy Score assessment.
Research Outputs
Peer-reviewed articles, technical reports, dissertations, or applied research advancing or stress-testing the discipline.
Audit & Verification Tools
Measurement methodologies, scoring instruments, scripts, or evaluation frameworks.
Educational Resources
Teaching materials, practitioner guides, or structured workshops directly implementing Protective Computing concepts.
2.2 Out-of-Scope Content
Submissions will be declined if they:
• Lack explicit engagement with Protective Computing principles
• Present generic security or privacy practices without Canon reference
• Function primarily as marketing or product promotion
• Contain unverifiable claims of compliance
• Include identifiable data about vulnerable individuals without documented ethical clearance
• Duplicate existing records without substantive advancement
3. Quality Standards
All submissions must meet the following baseline requirements.
3.1 Metadata Requirements
• Authors: ORCID identifiers strongly encouraged
• Title: Precise and descriptive, indicating artifact type and Canon relationship
• Abstract: Minimum 150 words describing contribution, methodology, and relevance
• Keywords: Must include “protective computing” plus 3–5 relevant domain terms
• Versioning: Explicit semantic versioning where applicable
• Related Works: Citation of the Overton Framework DOI and specific Canon layer engaged
3.2 Documentation Standards
Submissions must enable independent verification.
README Required
Plain-language overview, purpose, dependencies, and usage instructions.
Control Mapping Required (Technical Artifacts)
Explicit mapping to PC-1 through PC-5 principles, including verification evidence.
Reproducibility Requirements
Environment specifications, build instructions, and test procedures where applicable.
Data Provenance Disclosure
Clear statement of data sources, collection methodology, and ethical oversight.
Claims without reproducible evidence may be declined.
4. Licensing Requirements
All records must use open licenses.
Preferred:
• CC BY 4.0 (documents)
• MIT or Apache 2.0 (code)
Acceptable:
• OSI-approved licenses with attribution
Not accepted:
• Proprietary or restrictive non-commercial licenses
• Ambiguous or unspecified licensing
Open licensing is required to support auditability and academic reuse.
5. Review Process
All submissions undergo curator review.
5.1 Initial Screening (Within 7 Days)
Curators assess:
• Relevance to Protective Computing scope
• Completeness of metadata
• File accessibility and format integrity
• Compliance with FAIR principles
5.2 Technical & Standards Review
Where applicable, curators will:
• Verify metadata consistency
• Assess documentation clarity
• Evaluate control mappings and verification claims
• Confirm correct Canon citation
• Request revisions where necessary
Substantive revisions may be required prior to acceptance.
5.3 Publication Outcomes
Curators may:
• Accept
• Accept with required revisions
• Decline with documented rationale
Decisions prioritize discipline integrity over publication volume.
6. Curator Authority
Community curators may:
• Edit metadata for clarity and discoverability
• Add standardized tags
• Cross-link related Canon records
• Request clarifications or updates
• Remove records that violate policy
Curatorial actions will be documented where material.
7. Versioning and Record Updates
Updated submissions:
• Receive new DOIs
• Maintain links to prior versions
• Require changelogs documenting substantive modifications
Major Canon revisions (e.g., v1.x → v2.0) are treated as new records.
Prior versions remain accessible for citation stability.
8. Ethical Standards
All submissions must adhere to accepted research ethics:
• No plagiarism, fabrication, or falsification
• Human subjects protections where applicable
• Disclosure of funding sources or conflicts of interest
• Protection of vulnerable populations’ privacy
Protective Computing work directly intersects with human safety. Ethical violations will result in removal.
9. Content Integrity & Retraction
The community reserves the right to retract or remove records that:
• Violate intellectual property rights
• Contain demonstrably false technical claims
• Misrepresent compliance with PC principles
• Introduce harm or risk to vulnerable populations
Retractions will include documented rationale.
10. Policy Amendments
This policy may be revised as the discipline evolves.
All changes will include version updates and effective dates. Contributors are responsible for compliance with the current version.
11. Contact
For submission questions or clarification:
https://protective-computing.github.io
or through the Zenodo community interface.