public-release-reconcile
Skill4 starsChanged 3 months agoApache-2.0View on GitHub
Determine and record a product's genuine Public Release Surface state (HORO-512's 7-state contract) by checking what's actually true across every public surface — never by asserting a state to make a checklist green. Auto-used. Invoke when adopting a product into governance (HORO-511/513/ 517), when a product's public presence changes, and as part of the final campaign QA gate (HORO-533). Any Horonom product being represented (or considered for representation) on a public surface: metadata/company.yaml, the GitHub org profile, horonom.com, a product's…
In this repository21 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- adr-governanceSkill
- credential-operationsSkill
- documentation-experienceSkill
- engineering-loopSkill
- governance-doctorSkill
- homebrew-tap-mergeSkill
- jira-deliverySkill
- product-validationSkill
- release-assuranceSkill
- release-docs-syncSkill
- release-evidence-finalizeSkill
- release-qa-gateSkill
- release-security-gateSkill
- release-tag-cutSkill
- release-validate-channelsSkill
- repo-bootstrapSkill
- repo-scaffoldSkill
- rust-developmentSkill
- shell-developmentSkill
- terraform-developmentSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 36
Add or update the product's evidence config at metadata/release-evidence/<product>.yaml (github org/repo, claimed lifecycle, and any public …
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
<!-- horonom:generated --><!-- Source: horonomy/.github agents/skills/public-release-reconcile/SKILL.md. Do not hand-edit — rerun `python3 agents/common/project_skills.py`. -->SKILL.md — public-release-reconcile
Purpose
Determine and record a product's genuine Public Release Surface state (HORO-512's 7-state contract) by checking what's actually true across every public surface — never by asserting a state to make a checklist green.
Type
Auto-used. Invoke when adopting a product into governance (HORO-511/513/ 517), when a product's public presence changes, and as part of the final campaign QA gate (HORO-533).
When to use
Any Horonom product being represented (or considered for representation)
on a public surface: metadata/company.yaml, the GitHub org profile,
horonom.com, a product's own repo/docs/domain.
When NOT to use
- To justify publishing an unreleased or internal product "because the gate needs to be green." The gate reports what's true; it never becomes the reason to make something true prematurely.
- On a product whose own repo already has a more specific, stricter release process — run this reconciliation in addition to that process, not instead of it.
Procedure
- Add or update the product's evidence config at
metadata/release-evidence/<product>.yaml(github org/repo, claimed lifecycle, and any public website/docs/hosted-service URL), then runpython3 scripts/public_release_reconcile.py metadata/release-evidence/<product>.yaml. It checks each surface independently and live: product repo's own truth/maturity claim, GitHub repo metadata, tags/Releases (catching a lifecycle claim wider than the release evidence supports), website/docs/ hosted-service reachability and TLS,metadata/company.yaml's catalog entry, the GitHub org profile, andhoronom.comitself. - Classify the product's overall state using the 7-state contract in
governance/releases/public-release-contract.md(VERIFIED / REQUIRED / DEFERRED / NOT_APPLICABLE / NOT_YET_PUBLIC / BLOCKED_EXTERNAL / FAILED) — pick the state the evidence supports, not the state that would look best. - Where two surfaces disagree (e.g.
company.yamlsays one lifecycle, the product's own repo says another), the product's own repo is authoritative for capability/maturity truth;company.yamlmay only restate catalog-level facts already true there (governance/releases/public-surfaces.md). - Record the reconciliation result and any gap found; fix a gap only where it's genuinely this ticket's scope — don't repair an unrelated product defect a reconciliation pass happens to surface, unless it blocks governance correctness itself.
- A visible change to
horonom.comor the org profile as a result of this reconciliation needs real screenshot evidence in its PR (seerelease-assurance).
References
governance/releases/public-release-contract.md— the full 7-state contract (HORO-512).governance/releases/public-surfaces.md— the never-publish-to-turn- the-gate-green rule and the catalog-ownership boundary.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

