OutcomeCI

Share a workflow

Public workflows let other teams inspect and clone the way an outcome is delivered. Publishing never exposes the live private revision directly.

Prepare a public version

Open the workflow settings and choose Publish workflow. OutcomeCI runs the configured coding agent against an isolated copy of outcome.yml and its support files. The agent replaces organization-specific and consumer-provided values, including:

  • people, email addresses, channels, and provider identifiers;
  • Vault paths and connection references;
  • repositories, workspaces, and endpoints; and
  • organization-specific values in supporting prompts.

The prepared package must pass deterministic privacy checks and compile with the pinned OutcomeCI compiler. A failed check publishes nothing. If the Codex pass reaches a usage limit, OutcomeCI retries it once with Claude.

Prepare a package locally

The same preparation runs from the CLI, so you can inspect a package before publishing:

oci workflow prepare-publication outcome.yml --output ./public-package \
  --sensitive-term "Acme" --sensitive-term "Project Falcon"

--sensitive-term adds a term the privacy checks must not find in the package; repeat it for each term. --agent selects codex (the default), claude, or opencode, and --model overrides its model.

Review before publishing

OutcomeCI shows the exact sanitized definition and a typed setup list for new consumers. Review both, then approve or discard the candidate. Approval creates an immutable public version; later private syncs do not change it.

Generic, valid values stay in the public definition so it remains compilable. The setup list explains what a person cloning it must replace. Original values are not included in the replacement report.

Clone and evolve

A clone starts from the approved public version and retains lineage to that version. It does not inherit credentials, Vault access, logs, artifacts, or runtime state. A publisher can prepare and approve a newer public version while existing clones remain pinned to the version they selected.

Making the workflow private removes its public page without deleting its public version history.