Template library

A good council, pipeline or review board should not be rebuilt in every project. The template library is a public catalog filled by Flownix users from any organization, modelled on the npm registry.

Packages and versions

A package is an immutable title and an author. Each publish by the author adds the next version: a snapshot of a published harness version with its whole composition — roles and instructions, steps and their config, transitions with conditions, policies, context policy and input/output schemas.

• A published package version never changes. To fix something, the author publishes a new version; numbers go up in order.
• Any member of the harness project's organization can publish, but only a published version, never a draft.
• Only the package author publishes new versions into it.
• Nothing is linked. A package does not depend on its source harness: new versions, archiving or deleting the source or its project do not touch it.

Publishing

In the editor of a published harness, press To library. Choose "new package" (title of 1–120 characters, immutable afterwards) or "new version of my package" and write a version summary (1–280 characters).

The preview shows exactly what every user will see and what clones will receive. Role texts and step configs are not scrubbed: internal paths, task slugs and project data go out as they are. Publishing requires an explicit confirmation (confirm_public).

"My packages" lists all your packages and versions. The author can unpublish one version or the whole package. Unpublished content is indistinguishable from nonexistent for everyone else, and existing clones keep working.

Catalog and clone

The Template library button in the harness list opens the catalog: search by title and summary, filter by type, sort by newest, rating or clones. A package card shows every version and the full composition of the selected one.

Clone any published version into a project you belong to. A clone is an independent draft: one unpublished version 1, you as the author, empty links to project policies, no participants. Assign participants to roles, validate and publish — from then on it is an ordinary harness of your project. New package versions do not change the clone, and edits to the clone never reach the package.

Ratings and statistics

Any user except the author rates a package from 1 to 5, and can change or remove the rating. A rating applies to the whole package. The catalog and card show the average and the number of ratings.

The card shows statistics: total clones and clones in the last 30 days, unique cloners, clones per version and unique viewers. The author's own clones and views are not counted. Statistics are kept without linking a clone to the package, so clone runs are not reflected.

Moderation

A platform administrator can hide any package and return it to the catalog. A hidden package is unavailable to everyone else; existing clones are not affected.

For agents

Everything is available over MCP with the same rules and library.* error codes: harness.library_list, harness.library_get, harness.library_clone, harness.library_preview, harness.library_publish, harness.library_my_packages, harness.library_unpublish, harness.library_rate, harness.library_unrate, harness.library_set_hidden. The harness-blueprint skill searches the library for a matching package before building a harness from scratch.