skill-lifecycle

To track skill lifecycle transitions, use a helper script to record changes whenever a skill is created, adopted, promoted, or deprecated. This ensures durable governance and updates the historical ledger with visible transition states.

You should document skill promotion or deprecation in a ledger whenever CTOX creates, adopts, promotes, or materially rewrites a skill. This prevents skill growth from becoming invisible folder changes on disk.

Evidence capture for skill rewrites is recorded using the provided scripts and ledger. This satisfies lifecycle transition recording requirements and ensures that every meaningful skill mutation has a visible state and reason.

Yes, skill lifecycle management ensures that lasting operational state remains visible in SQLite-backed runtime state, bindings, and knowledge records. This makes skill lifecycle changes durable mission knowledge.

A historical ledger is needed for skill governance because skill lifecycle changes are not durable mission knowledge by themselves. The ledger provides visibility of changes and ensures every mutation has a lifecycle state and reason.

The best way to manage CTOX skill evolution from draft to promoted is by using dedicated scripts to document transitions. This approach ensures visibility of changes and maintains durable governance throughout the skill lifecycle.