Pack Catalog

Packs add domain workflows to the same governance kernel. Choose a workflow, check its runtime boundary, then configure the supported behavior for your consumer. Installed manifests and trusted host registration determine which capabilities can actually execute.

Compare offerings

Each row identifies current availability and distinguishes callable workflows from enabling libraries. Knowledge, Protocol Adapters, App Backends and App Delivery have no kernel-callable tools. The App Backends guide covers the provider-neutral app backend contract, adapter interface and conformance kit; the App Delivery guide covers the app build, submit and update job contract. Example capability names below refer to the current manifests; the linked guide describes the full supported surface. Installation, host binding and release compatibility still apply.

Current pack implementations and researched expansion candidates

Offering	Workflow and capabilities	Runtime	Consumer configuration	Access and support
Software Deliverylumenflow.software-delivery	Govern software changes with Work Units, lanes, gates, worktrees and durable delivery evidence. wu:claim wu:prep wu:done	Existing implementation Callable workflows	software_delivery Built-in delivery settings through config:set/get/unset; language and gate presets are documented in the pack guide.	Use the pack guide for installation, host binding and supported boundaries. Commercial access is by arrangement. Product licence; per-offering billing is future
Sidekicklumenflow.sidekick	Manage workspace-local tasks, memory, routines and channels through governed tools. sidekick-task:create sidekick-task:list memory:recall	Existing implementation Callable workflows	sidekick Pack-owned namespace. Schema support depends on the installed release; inspect its manifest before using configuration commands.	Use the pack guide for installation, host binding and supported boundaries. Commercial access is by arrangement. Product licence; per-offering billing is future
Agent Runtimelumenflow.agent-runtime	Execute governed agent turns, resume workflows and manage explicit autonomy controls. agent-runtime:execute-turn agent-runtime:resume_workflow	Existing implementation Callable workflows	agent_runtime Schema-validated agent_runtime settings; runtime and approval boundaries are documented in the pack guide.	Use the pack guide for installation, host binding and supported boundaries. Commercial access is by arrangement. Product licence; per-offering billing is future
Campuslumenflow.campus	Inspect facility inventories, energy and telemetry, and assemble facility proof records. campus:list_facilities campus:pue_telemetry proof:export_attested_bundle	Existing implementation Callable workflows	campus Pack-owned namespace. Schema support depends on the installed release; inspect its manifest before using configuration commands.	Use the pack guide for installation, host binding and supported boundaries. Commercial access is by arrangement. Product licence; per-offering billing is future
Reliability Operationslumenflow.reliability-operations	Investigate services and incidents using normalized metrics, logs, traces, alerts and timelines. reliability:get_service reliability:get_incident reliability:get_incident_timeline	Existing implementation Callable workflows	reliability_operations Schema-validated reliability_operations settings; connector binding and remediation authority remain separate.	Use the pack guide for installation, host binding and supported boundaries. Commercial access is by arrangement. Product licence; per-offering billing is future
Knowledgelumenflow.knowledge	Ingest local knowledge sources, retrieve citations and propagate deletion through an application library.	Existing implementation Enabling library No kernel-callable tools	knowledge Application library options. Namespace writes require a schema in the installed release; no kernel-callable tools.	Use the pack guide for installation, host binding and supported boundaries. Commercial access is by arrangement. Product licence; per-offering billing is future
Protocol Adapterslumenflow.protocol-adapters	Ingest OpenAPI descriptions and invoke operations through an explicit application adapter library.	Existing implementation Enabling library No kernel-callable tools	protocol_adapters Schema-validated protocol_adapters settings and explicit library options; no kernel-callable tools are registered.	Use the pack guide for installation, host binding and supported boundaries. Commercial access is by arrangement. Product licence; per-offering billing is future
App Backendslumenflow.app-backends	Provider-neutral app backend contract, adapter interface, conformance kit and a bring-your-own Postgres adapter, as an application library.	Existing implementation Enabling library No kernel-callable tools	No namespace No pack-owned configuration namespace. Adapters take explicit options in code; no kernel-callable tools.	Use the pack guide for installation, the adapter interface and the conformance kit. The data-plane runtime that serves a backend to an application is not part of this pack. Commercial access is by arrangement. Product licence; per-offering billing is future
App Deliverylumenflow.app-delivery	Provider-neutral app build, submit and update job contract with pure guard functions, a connector interface and a conformance suite, as an application library.	Existing implementation Enabling library No kernel-callable tools	No namespace No pack-owned configuration namespace. Platforms, profiles, tracks and channels come from the connector manifest; build prices come from a price configuration your host supplies. No kernel-callable tools.	Use the pack guide for the job contract, the guard semantics and the conformance suite. The build service, store and credential custody behind a connector are not part of this pack. Commercial access is by arrangement. Product licence; per-offering billing is future
Security Assurancelumenflow.security-assurance	Assess supplied finding snapshots and a bounded SARIF subset, producing source-bound evidence and remediation reports. security:assess	Existing implementation Callable workflows	security_assurance Strict shipped schema controls severity threshold, exact accepted rules and finding/UTF-8 byte budgets through config:set/get/unset; canonical consumer policy reaches the governed subprocess.	Use the pack guide for installed host binding, supplied input limits and unvalidated assessment evidence. Commercial access is by arrangement. Product licence; per-offering billing is future
Data Analyticslumenflow.data-analytics	Profile and check supplied CSV/JSON snapshots against explicit structural quality policies. data:check	Existing implementation Callable workflows	data_analytics Strict shipped schema controls row, byte and column budgets, required columns, null, unique and numeric-range policies through config:set/get/unset; canonical consumer policy reaches the governed subprocess.	Use the pack guide for host binding, supplied CSV and JSON input limits and structural check evidence. Verification from local build archives passed (installed into fresh locally initialised consumers through minimal init and builtin pack installation, with governed subprocess dispatch); no registry release is asserted. Commercial access is by arrangement. Product licence; per-offering billing is future
Customer Supportlumenflow.customer-support	Route supplied ticket snapshots using structural rules, draft cited responses and record human escalation evidence. support:triage	Existing implementation Callable workflows	customer_support Strict shipped schema controls allowed queues, structural routing and escalation rules, response templates, approved knowledge and ticket and byte budgets through config:set/get/unset; canonical consumer policy reaches the governed subprocess.	Use the pack guide for host binding, supplied ticket and knowledge input limits, source-cited unsent drafts and human escalation evidence. The pack never sends a response or changes a provider ticket. Commercial access is by arrangement. Product licence; per-offering billing is future

The Conformance Fixture is a test artifact, excluded from consumer offerings. Planned rows describe researched scope and have no installation or tool claims. Each becomes available only after its complete workflow, configuration, packaging and installed dispatch are verified.

Configure your consumer

A pack owns its configuration namespace. Use configuration commands for schema-validated workspace edits and consult the linked pack guide for supported settings in your installed release. Schema-less namespaces cannot be edited through the setter. Library-only packs also have explicit application API options; installing a library does not create callable tools.

Configuration controls behavior within existing scopes. It cannot grant tool permissions, connector credentials, approvals or paid access. See the portfolio architecture for the configuration and commercial boundary, and Pack Contract v2 for executable authority.

Access and future commercial offerings

Note

LumenFlow is commercial software with access by arrangement. Current product licensing is separate from a per-pack entitlement. This catalog does not implement per-offering billing, usage metering or charging. See Licensing and Access.

Stable offering IDs are discovery metadata outside the strict executable manifest. They provide a future reference for separately verified entitlements and usage observations; they never register capabilities or grant authority.

Assessment report, dataset check run and case workflow are unvalidated charging-unit hypotheses for the researched offerings. Consumer demand, pricing, retry/idempotency semantics and the entitlement issuer need separate evidence before any paid offering can be launched. No price or billing integration is promised by a planned row.

Build your own pack

Start with the pack authoring quickstart and domain-neutral kernel. A complete pack includes real workflows, configuration, trusted integration, tests and documentation, with evidence of installed execution.