Docs/REFERENCE

Outcome reference

The public format keeps each result and its recipe easy to inspect and reuse. Recipes are optional; existing schema-version-4 Outcomes remain valid.

Required files

outcomes.jsonRepository-root publisher identity and a thin list of Outcome manifest locations.
outcome.mdH1 title, opening summary, and optional formatted explanation.
prompt.mdThe exact reusable execution prompt.
outcome.jsonSchema version, slug, file pointers, author, models, authored timestamp, requirements, and one primary Product or Skill attribution.

Attribution

primaryThe single Product or Skill people should understand first. Product references use an ID; Skill references preserve repository, directory, and last-reviewed commit.
secondaryOptional additional Products or Skills that materially contributed. Do not repeat the primary attribution.

Recipe

The optional recipe object records how the result was made. Include only known details; missing fields do not mean no tools or skills were used. Models stay in the top-level models array with their authorship, execution, or review role.

provenanceRecorded from session (reviewed local capture), reconstructed, or omitted when origin is unknown. Recorded recipes may contain privacy edits.
notesKnown omissions and uncertainty.
agentName, optional version, and optional URL.
skillsRepository, directory, and exact lastReviewedCommit for every recorded skill.
referencesKind (repository, document, image, web, or example), label, URL, and optional purpose.
toolsName, purpose, and optional URL for tools and APIs.
stepsOrdered title and instructions, with an optional prompt for each step.

Recipes describe the published work. Copy recipe produces a text kit; local session capture is available in CLI 0.5.2. Kit installation is not supported.

Optional metadata

inputsActual files supplied to the run.
artifactsActual files produced by the run and available to download.
previewRepresentative images, video, audio, or CAD.

Machine interfaces

  • The MCP exposes list_outcomes, search_outcomes, and fetch_outcome over the live public directory.
  • possible search "rough request" finds Outcomes without MCP setup.
  • possible fetch <outcome-id> prints one directory Outcome’s recipe text kit, or its exact prompt when it has no recipe. Add --prompt for the exact prompt alone, or --json for the full record with its recipe, model list, and provenance.
  • possible add owner/repository stores a public source locally.
  • possible use owner/repository@slug prints that source Outcome’s recipe text kit, or its exact prompt when it has no recipe. It accepts the same --prompt and --json flags.