be-civic

Drafts new Be Civic path entries (single-outcome routes like portal flows, commune deeplinks, or single forms), or amendments to existing paths, from session research-notes. Spawned by bc-session-close, or by bc-process-drafter when content is path-shaped rather than process-shaped.

Drafts new Be Civic procedure processes, or amendments to existing ones, from session research-notes. Spawned by bc-session-close when a user's experience reveals a procedure the catalogue lacks or should change.

Use when Be Civic has no verified process for the customer's procedure (process mode) or no verified path for a needed source (path mode). Walks the customer through with research-as-we-go discipline. Produces a durable research-notes file the drafter consumes at session close.

Use when the customer presents a document — paste, upload, attachment, photo, or described field value. Extracts the routing fields the active procedure needs, archives the original to the customer's machine, discards everything else. Tells the customer plainly what was kept and what wasn't.

Use at the end of a Be Civic application procedure, after eligibility has passed and the document checklist has been gathered. Produces a Be Civic-styled application dossier — index page, bring-originals callout, checklist table, filled official forms, disclaimer — that the user prints and submits to the filing authority. Agent-tooling sub-skill; produces an artefact rather than running a Belgian admin process.

Onboarding for Be Civic. First-contact mode runs the verified flow — an email→code access widget (start-verification emails a 6-digit code → verify with the code), then state-shape activation inside the user-picked project folder (one folder, one git repo, with agent-managed state in a hidden .be-civic/state subdir) — and ends with a clean handoff into a fresh chat opened inside the project folder, where the working session begins. First-working-session mode (the next chat, after the harness loads and greets) fetches the carried-over canonical, renders the about-you form, and commits the profile sentinel. Falls back to anonymous read-only mode if the user declines verification. Returning and multi-active framings are owned by the harness.

Walk the user step-by-step through a Belgian-administration procedure once onboarding has captured the profile and the procedure has been routed. Owns the Path Directory traversal contract — batched-phase loop, browser-driven site discovery, browser_driving_preference honouring, eligibility-first / commune-last / consent-before-audited-delivery invariants, inline-commit path-source validations on each attempt. Hands off to bc-onboarding (returning mode) when the user signals a new procedure mid-session. Hands back to the harness at procedure completion.

Auto-commits Be Civic substrate state in the project folder as it changes