Open Access Compliance¶

An Open Access Compliance record documents the access classification, license, repository, persistent identifier, embargo posture, and policy-alignment status of every artifact that leaves the immediate project team. It serves as the single surface that Plan S funders, Nelson-memo-covered partners, and internal legal can consult before dissemination. Produce this artifact during the Critique phase whenever an artifact is about to be published, shared, mirrored, or archived outside the owning team.

Template¶

Section 1: Compliance Metadata¶

Instructions: Assign a stable Compliance ID and link it to the artifact under assessment. Status must reflect the latest policy alignment, not the state at creation.

Field	Value
Compliance ID	`[FILL — e.g. OAC-2026-001]`
Artifact name	`[FILL]`
Artifact type	`[Paper / Dataset / Model / Software / Report / Other]`
Innovation / Ecosystem ID	`[FILL]`
Assessor	`[FILL]`
Date	`[FILL]`

Section 2: Access Classification¶

Instructions: Tick exactly one access level. Hybrid and Internal Open both require explicit justification in the Notes field below.

Gold OA — fully open-access venue, immediate public access
Green OA — self-archived preprint/postprint in an open repository
Hybrid — subscription venue with OA option exercised
Internal Open — freely available within the sibling-project ecosystem
Restricted — access limited by license, NDA, or IP protection

Notes: [FILL — justification for Hybrid / Internal Open]

Section 3: Licensing¶

Instructions: Name the license, its URL, and its four canonical permission bits (commercial, derivatives, attribution, share-alike). Custom or non-SPDX licenses require a legal review sign-off.

Field	Value
License type	`[FILL — e.g. CC-BY-4.0, MIT, Apache-2.0, proprietary]`
License URL	`[FILL]`
Commercial use	`[Yes / No]`
Derivative works	`[Yes / No]`
Attribution required	`[Yes / No]`
Share-alike required	`[Yes / No]`

Section 4: Repository, Identifier, and Archival¶

Instructions: A persistent identifier is mandatory for every publicly shared artifact. Prefer DOIs (Zenodo, DataCite) for datasets and models; Innovation IDs suffice for internal-only artifacts.

Primary repository: [FILL — GitHub, internal registry, Zenodo, arXiv]
Persistent identifier: [FILL — DOI / Innovation ID / URL]
Backup / mirror: [FILL]
Retention period: [FILL]

Section 5: Funder & Policy Alignment¶

Instructions: For each row, mark Applicable and Compliant. Plan S applies whenever a cOAlition S funder is acknowledged anywhere in the underlying work; OSTP applies to US federally funded research post-2025.

Policy	Applicable?	Compliant?	Notes
Organisational OA policy	`[Yes / No]`	`[Yes / No / N/A]`	`[FILL]`
Funder OA mandate	`[Yes / No]`	`[Yes / No / N/A]`	`[FILL]`
Plan S / cOAlition S	`[Yes / No]`	`[Yes / No / N/A]`	`[FILL]`
OSTP public access (US federal)	`[Yes / No]`	`[Yes / No / N/A]`	`[FILL]`
Partner ecosystem sharing agreement	`[Yes / No]`	`[Yes / No / N/A]`	`[FILL]`

Section 6: Embargo, Decision, and Approval¶

Instructions: Embargoes must cite a concrete reason and a scheduled open-access date. The final decision label is one of the three below; Partially compliant requires an action-item table with owner and deadline.

Embargo period / start / open date / reason: [FILL]
Decision: [Compliant / Partially compliant / Non-compliant]
Action items: [FILL]
Assessor + IP lead sign-off: [FILL]

Adoption Checklist¶

All required sections completed
Artifact peer-reviewed by at least one R.I.S.C.E.A.R. peer
Stored in the project's designated docs location
Linked from README or equivalent index
Versioned + date-stamped with embargo end-date scheduled

References¶

PHOENIX v4.0.0 — docs/resources/templates/open-science/open-access-compliance.md
Plan S — Principles and Implementation, cOAlition S (2021)
OSTP — Ensuring Free, Immediate, and Equitable Access to Federally Funded Research (Nelson Memo 2022)
Creative Commons — License Chooser (https://creativecommons.org/choose/)
UNESCO Recommendation on Open Science (2021)

FCC integration¶

This template is referenced from the Forensic Auditor persona (src/fcc/data/personas/forensic_auditor.yaml) as part of the Critique-phase evidence set. The auditor pairs every publicly released artifact with an Open Access Compliance record and flags any public release without one as a P0 finding (hard-stop). See also src/fcc/data/governance/open_science_gates.yaml and src/fcc/data/governance/quality_gates.yaml.