Skip to content

OPERATIONS.md

Latest commit

 

History

History
100 lines (66 loc) · 1.5 KB

OPERATIONS.md

File metadata and controls

100 lines (66 loc) · 1.5 KB

Operations

v0.2 Primary Flow

Initialize a repository:

salacia init

Compile program.md into a blueprint:

salacia design --json

Run the harness:

salacia run --adapter codex --json

Inspect the decision:

salacia judge --json
salacia trace --json

Eval Surface

Run benchmark probes:

salacia eval run --suite full --json

Compare against competitors:

salacia eval compare --run <run-id> --json

Verify benchmark attestation:

salacia eval verify --run <run-id> --json

Run superiority profile:

salacia eval superiority --profile docs/benchmarks/trellis-baseline.v1.json --json

Judge and Promotion

Judge output is always written to:

.salacia/runs/<run-id>/judge.json

Possible outcomes:

  • accept
  • reject
  • blocked

Promotion policy:

  • accepted patches may be promoted to the root workspace
  • rejected patches are discarded
  • blocked runs preserve trace/evidence but do not promote changes

Release Gate

Release policy should consume:

  • runtime judge reports
  • eval/superiority reports
  • standard verification commands

This replaces the old v0.1 mental model of “convergence-only release gating.”

Legacy v0.1 Surface

The following commands are legacy/transitional:

  • plan
  • forge
  • prompt
  • execute
  • validate

They remain useful for compatibility and historical tests, but the primary runtime flow is now:

init -> design -> run -> judge -> trace -> eval