Public
Approved public material
An aggregate record or artifact appears publicly only after the applicable release decision.
Governance
CO-LUMINATE separates authority by decision domain.
The approved model separates scientific, lived-experience, data, technical, implementation, policy, access, and release authority. Named assignments and operating procedures remain pending. Publication of this model does not assign authority, grant access, record approvals, or operate a release workflow.
- Content class
- Governance record
- Foundation
- Approved v1.0
- Named domain assignments
- -
- Domain gate procedures
- Pending
- Public artifact inventory
- Empty
Role-based decision gates
The approved model defines the authority required for each gate.
- Platform scope and canonical promotion
- Project owner. Decision domain: Platform definition, architecture, priorities, and canonical promotion.
- Causal relevance and interpretation
- Relevant lived-experience representatives with the applicable scientific and implementation roles. Decision domain: Pathway relevance, priorities, language, interpretation, and translation risks.
- Data readiness and access
- Data steward. Decision domain: Access, lineage, linkage, missingness, quality, and privacy.
- Scientific specification and validation
- Scientific lead with the relevant outcome or method reviewer. Decision domain: Question, endpoint, estimand, assumptions, methods, validation, and sensitivity.
- Technical readiness
- Authorized engineering or reproducibility reviewer. Decision domain: Contracts, implementation, testing, environment, lineage, and reproducibility.
- Intended use and translation
- Implementation or policy role with lived-experience and scientific review where applicable. Decision domain: Actionability, feasible use, limitations, and responsible translation.
- Public release
- All applicable domain approvals followed by final project-owner approval. Decision domain: Exact artifact version, license, access, safety, and public classification.
Lived-experience authority is co-decision, not consultation alone. A Workspace role or permission does not satisfy a domain gate, and one gate cannot complete another.
Minimum decision record
An approval must identify the exact decision and evidence.
The symbol - marks an unestablished field. Its value cannot be inferred from an account, Workspace role, or another decision.
- Exact object and version
- Implementation scope and intended use
- Decision and decision date
- Approving role and authorized capacity
- Evidence reviewed
- Limitations, conditions, and dissent
- Access classification
- Re-review, withdrawal, or supersession conditions
Access classes
Identity, membership, and authority are separate.
Project Workspace
Approved project-team access
Access is limited to active project-team roles with the required capability.
Controlled
Separately governed access
Data, consent, ethics, partner, or governance requirements control research access outside ordinary site identity and Project Workspace membership.
ORCID and GitHub confirm provider identity. Neither grants project membership, repository access, controlled research access, or release authority.
Public release
Public release requires every applicable gate.
Public listing requires an exact version, approved provenance, applicable validation and safety records, a license, public or controlled classification, an accessible action, all relevant domain approvals, and final project-owner approval. This page does not approve or release an artifact.
Pending operating decisions
Operating procedures remain incomplete.
- Scoped domain-authority assignment, effective periods, recusal, and named assignments
- Lived-experience representation, selection, compensation, consent, safeguarding, quorum, and dispute resolution
- Authenticated-learning access classification
- Protected governance-audit projection, read scope, retention, and disclosure
- Member role or scope changes and contributor task-write scope
- Collaboration eligibility, conduct, review, appeal, retention, deletion, and responsible contact
- Code, documentation, image, and content licenses with artifact-level release records