⚠️ Status: Legacy — migrating to clarvia-graph. New contributions should target the graph repo unless explicitly for migration. See the transition note for details.
Open workflow data, schemas, and validation for source-backed administrative guidance. This repository is the core data layer for Clarvia's open bereavement workflow infrastructure - designed for cross-jurisdiction reuse across European administrative systems. Every contribution - a source check, a schema improvement, a validation fix - strengthens a reusable commons for bereavement administration.
🌐 clarvia.org · 📋 Good first issues · 📖 How to contribute
Source-backed workflow data, schemas, provenance, exports, and validation for Clarvia.
This repository is the core data layer for Clarvia's open bereavement workflow infrastructure. It is intended to become a reusable open dataset and workflow specification for source-backed bereavement administration. It contains structured administrative workflow data that can be used to generate:
- human-readable checklists,
- machine-readable exports,
- review pipelines,
- and lightweight public API views.
Note: The graph infrastructure is moving to
clarvia-graph, which introduces formal schemas, a source-backed consequence model, and a validation pipeline. This repository remains the legacy checklist corpus and migration source. Existing contributions here remain valuable — source-backed items will be migrated to the new graph model.
This repository contains the legacy checklist corpus and migration source for Clarvia's source-backed bereavement workflow data.
It is being maintained as part of a phased transition. Early workflow data, source records, and checklist structures are developed with internal resources so that the project can validate source collection methods, review states, jurisdiction modelling, and limited early checklist usefulness before larger funding cycles conclude.
This early data work is not a substitute for funded validation. It provides a practical base for migration, review, and improvement.
Future funded phases will support deeper source checking, expert review, localization, data quality improvement, validation rules, documentation, migration into clarvia-graph, and long-term stewardship of the workflow data.
The goal is to preserve the value of early structured work while making clear that published guidance should only mature through proper source review, validation, and approval.
You don't need to be a developer. Many of our most valuable tasks require attention to detail, language skills, or domain knowledge — not code.
| Task | Time | Skills needed |
|---|---|---|
| Verify a source URL is still current | ~15 min | Browser + attention to detail |
| Translate source descriptions to French or German | ~20 min | French or German proficiency |
| Review and mark a source as verified | ~15 min | Attention to detail |
| Write methodology documentation | ~30 min | Clear writing in English |
| Add a new official source record | ~20 min | Basic YAML editing |
👉 Browse all good first issues to find something that fits your skills.
Clarvia focuses on bereavement administration and related family support workflows.
The first service is being built and validated in Luxembourg. The data model is designed to recognise cross-border realities from the beginning, because many Luxembourg family situations involve neighbouring countries, foreign institutions, multilingual documents, or responsibilities outside one jurisdiction.
This repository models administrative workflows using official and authoritative sources.
Clarvia provides administrative guidance based on official sources.
It does not provide individualized legal advice.
The public data should not contain personal bereavement cases, private family information, or sensitive personal documents.
schemas/
v0.1/
data/
sources/
institutions/
document_requirements/
deadlines/
conditions/
tasks/
workflows/
scenarios/
exports/
scripts/
tests/
The initial data model includes:
- Source
- Institution
- DocumentRequirement
- Deadline
- Condition
- Task
- Workflow
- Scenario
- ReviewEvent
Every publishable workflow item should be traceable to at least one source.
Workflow data may use the following verification states:
discoveredstructured-from-sourcesource-checkedexpert-reviewedpublishedstale-reviewsuperseded
Only maintainers should mark workflow content as published.
- Luxembourg — first checklist and source-backed workflow foundation to build and validate
- France, Belgium, Germany — future or Luxembourg-relevant source mapping where cross-border situations require it
- Portugal and other European jurisdictions — possible future expansion after the model and review process mature
No jurisdiction should be treated as published guidance until its workflow data has appropriate sources, review status, and publication approval.
Workflow-data contributions must include:
- source references,
- jurisdiction,
- language,
- access date,
- verification status,
- and enough context for review.
Do not add unsourced legal, tax, inheritance, or administrative claims.
Do not submit personal bereavement cases or sensitive personal information.
See CONTRIBUTING.md for details.
Install dependencies:
pip install -r requirements.txtValidate data:
python scripts/validate.pyExport JSON:
python scripts/export_json.pyUnless otherwise specified:
- workflow data, documentation, and source metadata are licensed under Creative Commons Attribution 4.0 International;
- code and tooling are licensed under Apache License 2.0.
| Repository | Role |
|---|---|
| clarvia-graph | Open consequence graph — schemas, validation, sources, exports |
| workflow-web | Consumer web layer for publishing checklists |
| .github | Organization-wide community health files |