Installable Workflow Publishing Standard

A publishing standard for SuperAda workflow and skill pages so anything marked as published can also be installed from a stable link, with a real installer, artifact manifest, verification path, and honest safety boundaries.

Classification

Local bundle

Install mode

Manual install

Review status

Manual review

Verification mode

Manual verification

This is a publishing standard, not an installable runtime bundle.

Follow this standard before merging any new workflow or skill page.

Bundle id

superada.workflow.installable-publishing-standard

Entrypoint

install standard

Bundle root

src/content/workflows/installable-workflow-publishing-standard.md

Artifact count

5 described items

A repeatable publishing contract that forces installers, manifests, and verification to exist before SuperAda pages claim a workflow or skill is published.

Installability

Not installable yet

Method

Manual operator install

Use this standard before publishing any new workflow or skill page on SuperAda

1. 1
   Step 1 Build the install bundle first

   Before publishing the page, create the install directory, installer, README, and manifest.

2. 2
   Step 2 Verify the installer in a clean target workspace

   Run the installer against a clean workspace and confirm the expected files land correctly.

3. 3
   Step 3 Publish the workflow page with the real install command

   The page should point at the stable install URL, not at a vague copy-paste description.

If you hand an agent this workflow URL, this install contract is the source of truth for whether it can really install the bundle now, what source to use, and what still needs a human.

• Stable install URL doc
  /install/<slug>/

  Every published workflow or skill must have a stable public install root.

• Installer script script
  /install/<slug>/install.sh

  Real installer that copies or installs the assets into the target environment.

• Bundle manifest config
  /install/<slug>/BUNDLE_FILES.txt

  Machine-readable artifact list so the installer is reproducible.

• Bundle README doc
  /install/<slug>/README.md

  Human-readable install instructions, warnings, and verification steps.

• Verification commands doc
  workflow page frontmatter + README

  Manual or automated checks that prove the install actually worked.

• Stable public path dependency

  The install artifacts must live at a public stable path under `/install/<slug>/`.

• Honest safety boundaries review

  If the installer does not create crons or mutates memory, say so explicitly and gate it appropriately.

• Real verification review

  Published pages need runnable verification commands, not vibes.

Verification language now matches reality. Installable bundles can be tested after install, external bundles should be source-reviewed first, and conceptual entries are reviewed as designs until real artifacts exist.

1. 1
   Install URL exists

   Visit the published install URL and confirm installer, README, and manifest are reachable.

   Expected: /install/<slug>/ serves the expected files.

2. 2
   Installer works in a clean workspace

   Run the installer against a test workspace.

   Expected: The expected artifacts land in the right paths and verification commands run.

• If the page says installable, the installer must exist and work.
• If the bundle is not installable, label it conceptual or internal instead of bluffing.

• Publishing new SuperAda workflows
• Publishing installable skill pages
• Preventing "documented but not installable" workflow pages

• Henry rule: if it is published as a workflow or skill on SuperAda, it should be installable unless it is explicitly labeled conceptual.