AIWG 2026.9.0 - Cited civic workflows, safer publication

AIWG 2026.9.0 - Cited civic workflows, safer publication

Release date: 2026-09-01

Channel: stable

AIWG 2026.9.0 introduces an opt-in Civic Action review kit for public-interest research and editorial preparation. It connects source provenance, public-records planning, meeting and vote reconciliation, public-technology research, local-resource profiles, correction planning, and publication QA without delegating consequential civic decisions to automation.

What this changes for you

Civic work starts from evidence, not a blank prompt

Install the addon and describe the civic artifact you need to prepare:

aiwg use civic-action
aiwg discover "plan a public records request"
aiwg discover "reconcile a public meeting transcript with minutes"
aiwg discover "publish cited local public information"

The addon supplies four bounded personas, eight focused skills, three FlowPlaybooks with resolvable AIWG capabilities, and structured contracts for source registries, request plans, vote ledgers, meeting reconciliation, public-technology reviews, local-resource indexes, publication packets, corrections, and gate results. The design and legal/ethics briefs shipped with the addon cite the primary standards and public-sector guidance that informed those contracts. A control-to-source matrix records which boundaries are executable and which remain declarative.

Selected local packet checks are executable

Three commands make the most important boundaries testable in local workflows and CI:

aiwg civic source-gate source-registry.json
aiwg civic meeting-gate vote-ledger.json reconciliation.json
aiwg civic publish-gate publication-packet.json

Each command validates its input against the shipped JSON Schema, then inspects selected declared fields and writes a structured JSON report. Exit `0` means the evaluator found no blocking condition among those fields, exit `1` means a declared condition blocked, and exit `2` means the input or invocation was invalid. Schema failures include bounded JSON-pointer diagnostics. A pass does not independently validate facts, determine legality, or authorize an action; warnings remain visible for a named human to disposition.

Meeting contracts preserve disagreement instead of smoothing it away

The meeting FlowPlaybook and contracts keep media/transcripts, agendas, vote ledgers, and minutes as distinct sources. The local meeting gate checks declared vote cues, conflicts, results, reconciliation decisions, minutes state, and named review. Speaker identity is never inferred from voice alone. Recording posture, jurisdiction, and source completeness remain mandatory human workflow decisions rather than conclusions made by the command.

Public records and procurement remain decision-support workflows

Public-records plans capture jurisdiction, authority, scope, exemptions, fee/format preferences, deadlines, and manual submission approval. Public- technology review contracts inventory record classes, evidence, risks, release states, and human questions, and prohibit an automated award recommendation.

These artifacts help a person research and prepare. They do not submit a request, contact an agency or vendor, give legal advice, select a supplier, or make a procurement decision.

Local public data stays portable

The local-resource contract supports vendor-neutral AIWG profiles for CAP, GTFS, and HSDS with provenance, freshness, selected vertical fields, citations, and declared validation state. These profiles are not standards-conformance or public-safety validators. Jurisdiction- and vendor-specific connectors remain separate adapters.

Consequential actions stay with named people

Civic Action performs no autonomous acquisition, recording, speaker identification, outreach, records submission, legal or procurement decision, correction approval, or publication. Its local commands enforce a bounded set of declared source, meeting, and publication packet checks. Records, procurement, local-resource, correction, and external-adapter actions remain decision-support workflows controlled by named people. A machine pass is review evidence—not legal advice, factual verification, standards certification, compliance, or authorization to act.

The release also isolates required CI workflow concurrency, makes Gitea release recovery and asset retries safer, binds GitHub signing identity to the release tag, and removes timestamp drift from prebuilt release indices.

Package matrix

[email protected]
@aiwg/[email protected]
@aiwg/[email protected]

Learn more

When you try the addon, useful feedback includes the jurisdiction and artifact type, which gate decision surprised you, and whether the report gave the human reviewer enough evidence to act without hiding uncertainty.