Skip to content

v0.2.1

Choose a tag to compare

@github-actions github-actions released this 15 Sep 20:05
Immutable release. Only release title and notes can be modified.

0.2.1 (2026-09-15)

Governance impact

Phase: ▣ P1 — unchanged
Items: 4 advanced · 15 introduced · 2 superseded

Advanced · 4

GV Proposition
GV59 ◇ ↑ Minimize the ungoverned surface to irreducible observation and effect execution; adapters may perform effects but must not introduce semantic content, policy, structure, ordering, or authorization decisions.
GV63 ◇ ↑ Close the GitHub Actions portion of the governance inventory: triggers, permissions, concurrency, runners, timeouts, pinned actions, Nix runtime/cache, materialization, tests, Pages, releases, and admin boundaries.
GV77 ◇ ↑ Make CHANGELOG.md the canonical versioned portable materialization of each typed release entry, while the Release Please pull request and published GitHub Release project the same typed release content through a shared enriched GitHub renderer; external GitHub Release application must be verified by read-back equality.
GV42 ◇ ↑ Make repository bootstrap, integrations, secrets/environments setup, and privileged materialization declarative and reproducible through Govenv rather than repository-specific manual steps.

Introduced · 15

GV Proposition
+ GV84 ◇ Make observed invariant regressions counterexample-closing: once a contradiction to a governed or relied-upon invariant is recorded as an observed regression, its repair is incomplete until the counterexample is preserved as governed evidence, the missing or incorrectly scoped assurance boundary is corrected or overstated governance superseded, and candidate validation rejects recurrence before the affected workflow may succeed.
+ GV86 ◇ Treat governance items as cumulative constitutional decisions: from introduction onward, every item is interpreted against the complete constitution at that revision, including todo, done, superseded, and cancelled history; lifecycle state determines operative effect rather than constitutional membership, completion records establishment rather than applicability, and explicit dependency relationships between governance items are neither required nor modeled.
+ GV87 ◇ Project the typed candidate governance delta of every governed pull request through a GitHub-native check derived from revision-aware governance state; workflow artifacts may provide transient inspection material, but finite external retention means they must never be the sole or authoritative governance evidence, and any evidence required for completion, regression closure, auditability, or future validation must persist in governed revision-addressable form from which transient projections can be reproduced.
+ GV90 ◇ Model human authorization as AuthorizedRevision: new semantic authority may originate only from the exact repository state accepted by an explicit human pull-request merge. Candidate revisions may perform unprivileged validation and transient non-authoritative projections, but automated candidate-authoring principals must be distinct from human authorizers and post-authorization materializers and must not receive capabilities that can alter executable automation, authorize or merge the candidate, mutate authoritative repository state, or mutate persistent governed external state; only after authorization may governed automation exercise the capabilities necessary to derive deterministic materialization revisions or external effects. Derived outcomes create no independent semantic authority, must not be treated as fresh human authorization, and must retain revision-addressable causal provenance to the authorizing revision.
+ GV91 ◇ Require authority-boundary migrations to be monotonic and non-self-locking: an enforcement or capability restriction may become active only after every authorized execution path required to operate, verify, and repair under that restriction is already present in an AuthorizedRevision and its prerequisite external capabilities have been applied and read-back verified; bootstrap stages must preserve a human-authorized recovery path, and no stage may depend on a capability whose establishment occurs only after the enforcement that requires it.
+ GV92 ◇ Require administrative bootstrap and continued administration to have exactly one human-supplied root authority, represented by GOVENV_ADMIN_TOKEN. Provisioning, replacing, or rotating the credential representing that root preserves the identity of the same administrative authority and must never constitute a new independent authority. From this root and an AuthorizedRevision, Admin Materialize must deterministically derive the required subordinate authority graph and must materialize, generate where cryptographic material is required, provision, rotate, order, and read-back verify every subordinate credential, capability boundary, identity, environment, variable, secret, policy, and persistent administrative effect required by Govenv. Generated credential material carries no independent semantic authority and must remain bound to governed identity and capability state. No additional manually supplied credential, token, key, secret, application identity, environment mutation, or per-target administrative intervention may become a prerequisite for normal operation. Any required authority that cannot be derived or materialized from this root must be treated as an architectural incompleteness unless a hosting-platform impossibility is explicitly governed.
+ GV93 ◇ When an authorized materializer relies on a GitHub ruleset bypass granted to the DeployKey actor class, govern the repository deploy-key set as a closed set containing only the materializer credential. No unmanaged or independently provisioned deploy key may coexist with that bypass. Admin Materialize must provision or rotate the materializer deploy key, remove stale or unauthorized deploy keys, and read-back verify the complete deploy-key set before the DeployKey bypass may become active.
+ GV83 ◇ Render governance deltas sparsely: project only semantic dimensions whose values change, keep unchanged dimensions implicit, and retain only the identity and context required to unambiguously interpret the change.
+ GV78 ◇ Define revision-aware documentation references for governed identities, lifecycle states, operators, transitions, and Agda modules and symbols, so every reference can be resolved against the repository revision or delta it semantically represents.
+ GV79 ◇ Require every versioned Markdown artifact, including literate Agda, whether handwritten or materialized, to use valid navigable documentation references for governed concepts and Agda entities whenever such references are semantically exposed.
+ GV80 ◇ Make Agda documentation addressable by immutable repository revision so revision-aware documentation references never depend on mutable current documentation.
+ GV81 ◇ Require the Release Please pull request body to project governed and Agda documentation references using the revision-aware documentation reference model for the release delta it represents.
+ GV82 ◇ Require the published GitHub Release body to project the same revision-aware governed and Agda documentation references as its release document.
+ GV89 ◇ Treat the case-insensitive standalone word fix in governed commit messages as a conservative regression signal: candidate commit validation must reject it unless the commit references governed regression evidence or carries an explicit justified non-regression exemption; no exemption may discharge an unresolved observed regression.
+ GV88 ◇ Require every governable obligation to be enforced at its earliest sound information boundary while retaining govenv check as the authoritative repository evaluation and deriving every anticipatory enforcement from the same governed rule. Maintain an explicit enforcement inventory that anticipates, at minimum: construction-time Agda constraints for typed identities, roadmap/lifecycle validity, constitutional structure, evidence relationships, pure kernel boundaries, and projection/materialization structure; static candidate or incremental/LSP checks for governance evolution, immutable identity, architecture imports, handwritten-source restrictions, materialization ownership and drift, artifact colocation, documentation references, regression obligations, governance/release deltas, and release-progress classification; commit-boundary checks for staged candidate validity, commit policy, governance references, semantic commit classification, and regression signals; PR/CI checks only for information first available from GitHub or the remote candidate; and post-effect checks only for irreducible external observations such as read-back equality, publication state, admin effects, and runtime facts. Later stages may confirm earlier results but must not re-own, duplicate, or independently specify semantics that were soundly enforceable earlier.

Superseded · 2

GV85 ↪ GV89
Phase: P1 → P3
GV76 ↪ GV78
${\color{red}\texttt{-}}$ ${\color{red}\texttt{Make}}$ ${\color{red}\texttt{governance}}$ ${\color{red}\texttt{references}}$ ${\color{red}\texttt{in}}$ ${\color{red}\texttt{Git-derived}}$ ${\color{red}\texttt{projections}}$ revision-aware ${\color{red}\texttt{and}}$
  ${\color{red}\texttt{navigable:}}$ ${\color{red}\texttt{linked}}$ identities, lifecycle ${\color{red}\texttt{states}}$ ${\color{red}\texttt{and}}$ operators, transitions, and
  ${\color{red}\texttt{elisions}}$ ${\color{red}\texttt{must}}$ ${\color{red}\texttt{resolve}}$ ${\color{red}\texttt{to}}$ ${\color{red}\texttt{documentation}}$ ${\color{red}\texttt{derived}}$ ${\color{red}\texttt{from}}$ ${\color{red}\texttt{the}}$ ${\color{red}\texttt{immutable}}$ ${\color{red}\texttt{Git}}$ ${\color{red}\texttt{revision}}$
  ${\color{red}\texttt{or}}$ ${\color{red}\texttt{delta}}$ ${\color{red}\texttt{they}}$ ${\color{red}\texttt{represent;}}$ ${\color{red}\texttt{before-state}}$ ${\color{red}\texttt{references}}$ ${\color{red}\texttt{use}}$ ${\color{red}\texttt{the}}$ ${\color{red}\texttt{base}}$ ${\color{red}\texttt{revision}}$ and
  ${\color{red}\texttt{after-state}}$ ${\color{red}\texttt{references}}$ ${\color{red}\texttt{use}}$ the ${\color{red}\texttt{candidate}}$ or ${\color{red}\texttt{head}}$ ${\color{red}\texttt{revision.}}$
${\color{green}\texttt{+}}$ ${\color{green}\texttt{Define}}$ revision-aware ${\color{green}\texttt{documentation}}$ ${\color{green}\texttt{references}}$ ${\color{green}\texttt{for}}$ ${\color{green}\texttt{governed}}$ identities,
  lifecycle ${\color{green}\texttt{states,}}$ operators, transitions, and ${\color{green}\texttt{Agda}}$ ${\color{green}\texttt{modules}}$ and ${\color{green}\texttt{symbols,}}$ ${\color{green}\texttt{so}}$
  ${\color{green}\texttt{every}}$ ${\color{green}\texttt{reference}}$ ${\color{green}\texttt{can}}$ ${\color{green}\texttt{be}}$ ${\color{green}\texttt{resolved}}$ ${\color{green}\texttt{against}}$ the ${\color{green}\texttt{repository}}$ ${\color{green}\texttt{revision}}$ or ${\color{green}\texttt{delta}}$ ${\color{green}\texttt{it}}$
  ${\color{green}\texttt{semantically}}$ ${\color{green}\texttt{represents.}}$

Derived from immutable typed roadmap snapshots and governed Refs: GV… commit metadata. SemVer remains independent. 0e03a8c..733c812.

Bug Fixes

  • authorization: support private materializer app (346aee0)
  • release: parse quoted roadmap snapshot strings (ac963c3)
  • release: simplify phase delta classification (9c8e438)

Governance

  • administration: materialize single setup (47707f8)
  • administration: model single-root authority (9742d9a)
  • administration: normalize deploy key readback (328cc1c)
  • assurance: define regression closure policy (ca6c2ed)
  • authorization: bind post-merge effects to exact revision (b3ffd02)
  • authorization: stage monotonic authority bootstrap (6e35290)
  • release: bind governance impact to release version (95c4ceb)
  • release: close release push authorization regression (30fc755)
  • release: model sparse supersession dimensions (6928076)
  • release: render only changed supersession dimensions (bcf858f)
  • roadmap: govern documentation references (748d65d)
  • roadmap: govern sparse delta projection (b01ad45)

Documentation

  • release: describe sparse governance deltas (206dfb9)

Code Refactoring

  • materialization: project deploy key set (6cebdee)
  • release: close projection over typed delta (e0b59aa)

Miscellaneous

  • materialize: update governed materializations (cfa0ad3)
  • materialize: update governed materializations (9fd6483)