feat: verify death certificate issuing authority and accepted forms

[HirenGajjar]

Closes #29

Researched two official Guichet.lu source pages to verify the two unknown fields.

---

Issuing authority

Source: Declaration of death page — https://guichet.public.lu/en/citoyens/life-event/famille-education/deces-proche.html

"The civil registrar's office will draw up the death certificate and provide the declarant with extracts from the certificate."

Source: Death certificate page — https://guichet.public.lu/en/citoyens/justice/certificats-copies-actes-casier-judicaire/certificats-copies-actes/acte-deces.html

"When a person dies, the death must be declared to the communal administration in the commune where the death occurred. For this reason, only the commune in question is able to issue a copy of the death certificate."
"The office of the civil registrar establishes the death certificate on the basis of the report issued by the doctor."

Conclusion: The issuing authority is the civil registrar's office (Bureau de l'état civil) of the communal administration in the commune where the death occurred.

issuing_authority_id remains null — no matching institution record exists in data/institutions/lu/. A new institution record for Luxembourg communal administrations will need to be created.

---

Accepted forms

Source: Death certificate page — https://guichet.public.lu/en/citoyens/justice/certificats-copies-actes-casier-judicaire/certificats-copies-actes/acte-deces.html

"The copy or extract of a death certificate is a reproduction in full or in part of the details indicated on the death certificate. A copy or an extract of this certificate is often necessary for carrying out certain administrative procedures."

Conclusion: Families receive extracts (partial reproductions) and full copies, both issued officially by the civil registrar. Mapped to schema enum values:

• certified_copy — extracts issued as standard at declaration, issued by an official government body
• copy — additional full copies available on request

---

Schema compliance

Before making any changes, I read schemas/v0.1/document_requirement.schema.json carefully.

The accepted_forms field has a strict enum:
["original", "copy", "certified_copy", "digital", "unknown"]

extract and full_copy are not valid values in this schema. The Guichet source uses the word "extract" to describe what families receive, but the correct schema mapping is certified_copy (extracts issued by an official government body) and copy (additional full copies on request). All values in this PR are valid enum entries confirmed against the schema before committing.

---

Other changes

• verification_status: discovered → structured-from-source
• provenance.updated_at and updated_by set

---

Verified

• python3 scripts/validate.py — passes (8 data files)
• Trailing newline present
• 1 file changed, 6 insertions, 5 deletions

[TommiLindfors]

Merged! This is your best PR yet @HirenGajjar. The level of source verification here is exactly what Clarvia needs:

• Quoting the actual Guichet.lu text that supports each data change
• Carefully mapping 'extracts' to the schema's certified_copy enum value with reasoning
• Correctly leaving issuing_authority_id as null and documenting why in the notes
• Updating provenance metadata

This is the kind of rigorous, source-backed work that makes Clarvia's data trustworthy. Five merged PRs across both repos now - you're a core contributor.

Also good catch on issue #30 (CI workflow already exists). I'll close that one.

Next challenges if you're interested:

• #28 - Verify death declaration deadline from Guichet source (similar research pattern to this PR)
• #22 - Add test cases for the validation script (Python)

[TommiLindfors]

Hey @HirenGajjar - we've just sent you collaborator invitations to both workflow-data and workflow-web with write access. Check your GitHub notifications or email to accept.

What this means for you:

• You can push branches directly to the repos (no more forking needed)
• You can assign yourself to issues, add labels, and manage project boards
• Clarvia is on the GitHub Teams plan through GitHub for Nonprofits - as an outside collaborator, you get Teams-level features when working on our repos, for free
• PRs still require one maintainer approval before merging (branch protection is on)

Five merged PRs across both repos, source verification research, schema-aware contributions - you've earned this. Welcome aboard properly.

If you have any questions about the workflow or want to discuss anything, feel free to open a discussion or comment on any issue.