Library

The Library is where Farna Control primitives live and are shared. Every platform primitive is a first-class library citizen: schemas, agents, workflow bundles, pipeline templates, composites, connector type packages, lifecycle maps, test fixtures, and collections.

Primitive types

Primitive types
Type Description
schema Versioned input and output schema definitions
agent A stored agent: prompt template, model backend, schemas, and evals
workflow A workflow bundle
pipeline_template A complete pipeline you can install as a starting point
test_fixture A captured fixture map that replays a run’s inputs against the stub model backend
composite A reusable subgraph that a composite pipeline node references
integration A connector type package
lifecycle_map A declarative lifecycle map
library_collection A curated set of pinned primitives installed together

Primitive sources

Every primitive lives in one library_primitives table with a source discriminator:

Primitive sources
Source Meaning
local Created within the org
Farna Control The Native library shipped by Farna Control, signed and verified
community Opinionated example pipelines published in the community database, not verified by Farna Control
registry Cached read-only copy synced from the hosted community registry

Copy to adapt

One-click copy creates a local editable instance. forked_from is immutable provenance metadata.

  • By default, copied primitives check for upstream updates (auto_update is true)
  • When an update is available, update_available_version_id is set on downstream forks
  • The owner can apply the update or set auto_update to false to diverge freely

Trust tiers

Community registry primitives carry one of two trust tiers. This table is the canonical list; Contribution Provenance explains how a primitive earns its tier.

Trust tiers
Tier Badge Behavior
Verified publisher Green Ed25519-signed by a Farna Control-vetted key. No warning on copy
Community Amber Unsigned or self-signed. Warning on copy: “This primitive has not been verified by Farna Control. Review the prompt template and schema before use.”

For how signatures and fork provenance work, see Contribution Provenance.

Rating system

  • One rating per user per primitive
  • Self-rating is blocked
  • Rating requires at least one prior copy-to-adapt (you must have used it)
  • 10-minute submission cooldown per user
  • Ratings display as a weighted average with a review count

Battle-tested defaults

The Library is the primary onboarding path. On first boot, the UI surfaces recommended primitives for the user’s declared tool stack. Users start from library primitives and migrate to bespoke configurations over time.