Publish from your source

One folder per Outcome

outcomes.json      # publisher and manifest locations
outcomes/my-outcome/
  outcome.json    # machine metadata
  outcome.md      # human-facing title and explanation
  prompt.md       # exact reusable execution prompt
  media/          # optional previews
  inputs/         # optional supplied files
  artifacts/      # optional downloadable results

Author locally

1. Create the folderRun npx @fraylabs/possible@0.3.0 create my-outcome --product owner/product, or use --skill owner/repository directory commit.
2. Write the human recordPut the title, opening summary, and formatted explanation in outcome.md.
3. Preserve the promptPut the exact reusable execution prompt in prompt.md.
4. Add provenanceName the one primary Product or Skill first, then record optional secondary credits, models, requirements, author, timestamp, and file references in outcome.json.
5. ValidateRun npx @fraylabs/possible@0.3.0 validate.

Publish publicly

The create command adds the Outcome to the repository-root outcomes.json index. Commit the public GitHub repository and run npx @fraylabs/possible@0.3.0 publish owner/repository. Domain publishers expose that index at /.well-known/possible/outcomes.json and publish the HTTPS origin. Possible stores an immutable snapshot of every accepted revision.

Identity and labels

A publisher-domain source is Official for that domain. GitHub sources are Community by default unless ownership of a referenced Skill follows directly from the repository. Authors cannot self-award another company’s identity.