release-track
latest stable tag current version public report source alignment
Project / Civic League
Governance systems should be readable before they become powerful.
Civic League is a public-system simulation and governance reporting experiment focused on release discipline, version clarity, decision traces, and civic-style operating loops.
Problem
Complex systems drift when nobody can explain the current state.
Governance work fails when rules, versions, source alignment, and public reporting become scattered. The goal is to make the system explain what changed, why it changed, and whether it is ready to publish.
System shape
Release reports, source alignment, and readiness gates.
governance gate
release check public report smoke version validation ready signal
operating rule
make state visible make changes traceable make readiness testable
Real artifact
Public season report is generated and smoke-tested.
npm run season:public-report
Civic League Public Season Report Status: ready Total Seasons: 2 Release Reference - Release Track: v0.4.19 - Latest Stable Tag: v0.4.19 Public Readiness - [x] Portfolio readable - [x] Schedules visible - [x] Scope mix visible - [x] Runnable status visible - [x] Both seasons validate - [x] Public report export passes smoke validation
Current signal
Release-ready public report
Civic League now has a real public report artifact with release references, season status, readiness checks, and smoke validation.
View raw public report →release-governance-check
PASS main branch protected PASS required check includes release-verify PASS release process runbook exists PASS versions agree at v0.4.19
Governance checks are part of the release surface, not a separate afterthought.
season-public-report-smoke
== Season Public Report Smoke == PASS | season public report CLI/export parity
The public report has CLI/export parity smoke coverage.
Why it matters
A system with public consequences needs public legibility.
Version clarity
Clear tags, reports, and release tracks reduce confusion around what is stable, current, or experimental.
Governance traceability
Decision systems need a record of what changed and why, not just a final output.
Reusable release discipline
The same readiness model can support other software, civic, operational, and product systems.
Product direction
Governance infrastructure as a reusable pattern.
Civic League is useful as both a specific experiment and a reusable pattern for release reporting, public readiness checks, and decision-system accountability.