Skill Governance

Govern the Skill surface the user actually experiences: the intended hot or router entries are fully visible in a fresh host, cold capabilities remain reachable, editable behavior has one canonical owner, and every retirement is recoverable. A smaller directory count is not the outcome.

Required outcome contract

Before acting, state in one sentence:

• which entries or routers must be model-visible;
• which capabilities must remain available cold;
• which layer the user authorized changing;
• what fresh-host evidence will prove success.

If the request is only “how many / what is loaded / why”, stay read-only.

System model