Co-created causal knowledge
An editorial framework for turning knowledge from people and communities into documented questions, triage decisions, and interpretation boundaries.
Public learning library
CO-LUMINATE connects co-created causal stories, longitudinal reconstruction, outcome harmonisation, causal specification, and governed evidence release. These project-owner-directed editorial summaries contain no participant-level data and are not released artifacts.
Platform horizons
CO-LUMINATE is intended to support multiple populations, outcomes, and implementation settings over time. Maturity badges distinguish what can be learned from now from work still being designed.
An editorial framework for turning knowledge from people and communities into documented questions, triage decisions, and interpretation boundaries.
Project-owner-directed editorial summaries of synthetic-data rules, reproducibility guidance, and public/private handover safeguards.
A governed adaptation workflow is being defined. No population or outcome beyond a human-approved implementation should be considered solved.
Internal specifications and synthetic reference files exist. No licensed, runnable, or reusable pipeline is published on this site.
The roadmap connects bounded evidence to learning, implementation partnerships, and action while keeping uncertainty visible.
Future integrations may add narrowly permissioned tools and services. No plugin marketplace or runnable extension is available today.
Start-to-finish learning path
Each stage should leave an auditable basis for the next. Later modelling cannot repair undocumented upstream choices.
Begin with lived experience, purpose, and an explicit causal question.
Make linkage, time, households, exposures, and observation gaps visible.
Document endpoint provenance, measurement limits, and adaptation needs.
Translate an approved DAG into requirements, assumptions, and an estimand.
Test contracts, provenance, failure modes, and interpretation boundaries.
Share only reviewed, licensed, public-safe learning artifacts.
Current public summaries
Each card is a current public editorial summary. It is not a download, runnable tool, pipeline, or substitute for the internal source material.
Understand why CO-LUMINATE is a reusable evidence architecture, with depression as a reference case rather than the platform boundary.
The five layers, module boundaries, and separation between public and controlled work.
Learn how lived-experience inputs can inform causal questions without being treated as automatically model-ready variables.
How causal stories can be captured, triaged, and interpreted without turning them directly into model-ready variables.
Work through person-time, visits, households, exposure windows, linkage quality, and observation gaps before analysis.
The sequence of timing, linkage, history, and gap questions that should be resolved before causal modelling.
See which provenance, timing, measurement, missingness, and validation decisions must be revisited for every new outcome.
The decisions that must be revisited before adapting the architecture beyond the reference outcome.
Move from a documented question and DAG to analysis windows, estimands, interpretation limits, and sensitivity needs.
The assumptions, timing decisions, estimand questions, and interpretation limits that precede analysis.
Learn how provenance, environments, tests, validation reports, synthetic-data rules, and release review fit together.
The provenance, testing, privacy, and human-review controls required before a public handover.
Review the evidence-to-decision basis, architectural recommendations, risks, and staged implementation plan.
The cited research synthesis, recorded risks, and staged implementation roadmap.
See how bounded tasks, source-of-truth rules, privacy checks, and explicit open questions reduce unsafe automation.
The source-of-truth, privacy, review, and open-question controls applied to AI-assisted development.
Reuse readiness
Public editorial learning summaries are available on this site. No tool, pipeline, source package, download, or redistribution permission is currently published. Publication requires an approved license, completed validation and safety review, a real release manifest, and human approval.