Post

idiolect
@idiolect.dev

We have a new release (v0.13.0) that introduces a bunch of new community management tooling. There is now one portable path from a governed definition change through consequence analysis, review, verification, signed release, resumable migration, federation, and exit.

github.comRelease v0.13.0 · idiolect-dev/idiolectAdded Community control plane for 0.13.0. The new idiolect-community crate and CLI lifecycle provide versioned idiolect.toml workspaces, role-aware maintainer/consent/vote/steward/hybrid governanc...

2 reposts1 like

idiolect
@idiolect.dev

idiolect-community starts with an idiolect.toml workspace: community identity, governed packages, authorities, decision rules, resource limits, and exit policy. A change packet keeps the schema diff, participant-facing consequences, reviews, and verification evidence together.

idiolect
@idiolect.dev

Governance supports maintainer approval, consent, threshold vote, steward approval, and maintainer + steward rules. Verification remains three-valued: verified, refuted, or incomplete. A release gate accepts only verified evidence for every check required by policy.

idiolect
@idiolect.dev

Approved packets become P-256/ES256-signed release indexes over artifacts, dependencies, and digests. Migration runs retain cursors, progress, and sampled failures so work can resume after interruption. Exports reject symlinks and carry a SHA-256 inventory.

idiolect
@idiolect.dev

Four new records publish the interoperable part of that lifecycle: dev.idiolect.changeProposal, communityRelease, migrationRun, and federation. Private keys, local paths, and draft evidence remain in the workspace rather than becoming network records.