← Back to workflows
Live Operations Medium Local bundle v1.0.0

Installable Workflow Publishing Standard

If it ships, it installs.

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.

Availability
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.

Install source
Publishing standard
Follow this standard before merging any new workflow or skill page.
Workflow record
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.

Install contract
Installability
Not installable yet
Method
Manual operator install
Use this standard before publishing any new workflow or skill page on SuperAda
Agent step 1
Treat this as a publication rule set.
Agent step 2
Use it before publishing any workflow or skill on SuperAda.
Current limits
  • This page defines the rule. It is not itself a runtime install bundle.
Step 1
Build the install bundle first
Before publishing the page, create the install directory, installer, README, and manifest.
Step 2
Verify the installer in a clean target workspace
Run the installer against a clean workspace and confirm the expected files land correctly.
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.

What you get

  • Every published workflow has a stable install URL
  • Every published skill/workflow has a real installer or honest conceptual label
  • Operators stop shipping pages that cannot be installed

Workflow includes

  • Install URL standard
  • Manifest requirement
  • Installer requirement
  • Verification requirement
  • Safety review requirement

Described artifacts

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.

Requirements

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.

Declared structure

  • /install/<slug>/
  • /install/<slug>/install.sh
  • /install/<slug>/README.md
  • /install/<slug>/BUNDLE_FILES.txt
  • workflow page with real install command

Verification

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.

Install URL exists
Visit the published install URL and confirm installer, README, and manifest are reachable.
Expected: /install/<slug>/ serves the expected files.
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.

Best used for

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

Operator notes

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