SOPs as agent skills

Processes & skills

A Process is one team's procedure inside a Service. It is not a flowchart. It is an SOP written so an agent can exercise judgment — typically as a skill document (for example .rfctr.md / SKILL.md) plus supporting scripts and a review surface.

Versioning

Publishing creates an immutable process version. Every run pins the version that judged it. Mid-run re-pin is a deliberate, audited exception — the default is immutability so audits stay honest.

Authoring motion

Edit the skill and supporting files in the process workspace.
Try the work (ad-hoc or on a test engagement).
Publish when the definition should apply to future runs.
When review produces a lasting correction, promote it back into the skill.

The console treats authoring as document work, not canvas wiring. On screens where someone is reading or editing the process, the writing should be the loudest thing on the page.