Skip to content

Add Governed Form Filling doctrine (CERFA + any form, modular skills)#44

Draft
ifanjuang wants to merge 1 commit into
mainfrom
claude/governed-form-filling
Draft

Add Governed Form Filling doctrine (CERFA + any form, modular skills)#44
ifanjuang wants to merge 1 commit into
mainfrom
claude/governed-form-filling

Conversation

@ifanjuang
Copy link
Copy Markdown
Owner

Why

User's first concrete example: from a project database, prepare a required document (a CERFA — permis de construire, déclaration préalable, autorisation de travaux ERP, permis d'aménager — or any administrative form). Find which one, where to look, retrieve, verify, fill what is certain, ask when in doubt, document every value's source, save, and produce a downloadable annotated draft. Then: make it modular / several skills.

What

docs/governance/GOVERNED_FORM_FILLING.md — generic governed filling of any structured document:

  • Field as claim: every field carries value + status (known / retrieved / inferred / unverified / entity_to_confirm / conflicting) + source + date. Rendered as inline "to verify / to fill" comments.
  • Per-field resolution loop with fallback: known → authorized source A → source B → ask. A fallback is another authorized source, never a guess; after sources are exhausted the answer is "ask", not "assume"; every attempt is recorded.
  • Guardrails: entity verification before keeping a contact/company (right registration number); dated source for any regulatory value; no submission/signature ever; scope isolation; save & resume.
  • Modular decomposition (the user's ask): classify-document, resolve-known, retrieve-source, verify-entity, fill-fields, raise-doubt, render-annotated, save-provenance — each a manifest + envelope, never calling each other, returning candidates, degrading gracefully. Fan-out-then-synthesis topology; the composition is a Workflow Manifest, not a runtime.

CERFA is the first cited instance; the rule is generic for any administrative form.

Placement

Method + field discipline in Pantheon. The whitelist of concrete sources lives in EXTERNAL_TOOLS_POLICY.md; retrieval, entity check, PDF fill and contact sync are adapters outside Pantheon. Doubts surface via USER_DECISION_GATE / REVIEW_QUEUE; provenance saved via CORE_RECORDS_MODEL (#43).

Indexing

MODULES.md and AUTHORITY_INDEX.md updated here. STATUS.md / README.md to index when #42 lands.

Boundary

Documentation only. No form filler, PDF writer, OCR, scraper, API connector, contact sync or runtime. Submission and signature remain human. CI lint verified locally (0 failures).

Find where to look. Verify. Fill what is sure. Ask what is not.
The draft is the system's. The signature is the human's.

https://claude.ai/code/session_01UDCR8Dmp16xpFnwqJwsrPH


Generated by Claude Code

@ifanjuang ifanjuang force-pushed the claude/governed-form-filling branch 3 times, most recently from 67a3c8c to 0c393f1 Compare June 1, 2026 18:30
Generic governed filling of any structured document from dossier records
and authorized sources. Obtain the template itself: provided library, a
curated whitelist of template sites, or discovery; handle any format
(docx/pdf, fielded or flat) where a flat template needs a verified,
reusable field map; confirm current official version (e.g.
public-procurement DC/ATTRI/EXE families). Each field is a claim (value
+ status + source + date); per-field resolution loop with fallback
(known -> source A -> source B -> ask). Guardrails: entity verification,
dated regulatory sources, no submission/signature, scope isolation,
pre-transmission minimization, resumable save. Cross-field consistency;
governed reuse of confirmed facts across documents (to_reconfirm /
superseded); completeness/readiness summary (described, never asserted);
failure/unavailability handling. Modular decomposition into reusable
skills (classify-document, fetch-form-template, resolve-known,
retrieve-source, verify-entity, fill-fields, raise-doubt,
render-annotated, save-provenance) as a fan-out-then-synthesis
composition; skills never call each other. Method only; readers, fillers
and connectors are adapters outside Pantheon. Concrete catalogues and
template-site lists live dated in domain packs.

https://claude.ai/code/session_01UDCR8Dmp16xpFnwqJwsrPH
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants