Organization-wide governance, community health, reusable workflows, and repository policy source for the WowAPI ecosystem.
The public ecosystem is WowDev; WowAPI is its assembled framework chassis. Organization defaults include professional issue and Discussion forms, contribution and DCO guidance, Contributor Covenant 3.0 enforcement, accountable-maintainer governance, security and support routing, a synchronized label taxonomy, and fail-closed validation with negative fixtures.
Run the complete local contract with:
make validate KERNEL=../wowapi-kernelApply the label taxonomy to a hosted repository with scripts/sync-labels.sh OWNER/REPOSITORY after authenticating gh. Use --dry-run to inspect the exact manifest without changing GitHub.
go-library-ci.ymlruns the repository-owned metadata, formatting, lint, documentation, external-consumer, dependency, license, test, race, fuzz-smoke, and build contracts.release-library.ymlchecks an exact source commit and unused semantic version, runs the full release contract, and emits attested commit-bound candidate evidence. It does not create a tag or publish a module.validate-shared-workflows.ymlvalidates the workflow source and proves that an unpinned third-party action is rejected.
Component repositories own the meaning of their make targets; this repository owns orchestration, tool versions, least-privilege permissions, timeouts, and final required-job aggregation. This keeps domain policy close to each component while preventing every repository from inventing a different CI control plane.
Consumers must reference a released immutable workflow tag, beginning with wowdev-org/.github/.github/workflows/[email protected]. A moving branch reference is not accepted. Until this repository is published and v0.1.0 exists, local validation is authoritative and hosted consumer workflows are intentionally not operational.