Skip to main content

Process Packs

A process pack is the unit of process-specific control.

It contains:

process.manifest.yaml
profile.yaml
hooks.yaml
schemas/
scenarios/
templates/
skill/SKILL.md

Process packs are contract-based components. They define process knowledge for FST, but they do not change FST authority rules.

Manifest​

The manifest declares process id, version, profile API, logic API, entrypoints, required capabilities, generated command metadata, and approval requirements.

Profile​

The profile defines actions, artifacts, gates, routes, approvals, and materialization rules.

Hooks​

Hooks provide process-specific logic. They compute facts, validate artifacts, or render templates. Hooks do not return route or approval authority.

Scenarios​

Scenarios prove the pack behaves:

  • happy path
  • missing input
  • blocked case
  • ask-user case
  • instruct-agent case
  • approval-required case
  • hook failure
  • idempotency replay

Lifecycle​

fst process install process-packs/local_patch_review-0.1.0.fstpack --command fst-patch-review
fst process command list
fst scenario run local_patch_review.happy_path

Installation records the process in .fst/processes/registry.json and creates resolver metadata in .fst/commands/. Existing runs remain bound to their original process id, version, and profile hash.