Configurable Pack Portfolio
LumenFlow’s pack portfolio separates discovery from executable authority. An offering catalog can describe stable product offerings and availability; pack manifests, host registration and real dispatch determine callable tools. This page lists the shipped packs, their consumer configuration, and the three domain packs.
Existing portfolio
Section titled “Existing portfolio”| Pack | Current role | Configuration namespace |
|---|---|---|
| Software Delivery | Callable delivery domain: lifecycle, gates, git and evidence | software_delivery |
| Sidekick | Callable domain: tasks, memory, channels and routines | sidekick |
| Agent Runtime | Callable enabling pack: governed sessions/turns | agent_runtime |
| Campus | Callable facilities, energy and proof domain | campus |
| Reliability Operations | Callable incident investigation/evidence domain | reliability_operations |
| Security Assurance | Callable supplied-finding assessment with unvalidated evidence | security_assurance |
| Data Analytics | Callable supplied CSV/JSON snapshot quality checks | data_analytics |
| Customer Support | Callable supplied-ticket routing, cited unsent drafts and escalation | customer_support |
| Knowledge | Local ingestion, citations, ACL and deletion library; no manifest tools | knowledge |
| Protocol Adapters | OpenAPI ingestion/invocation library; no manifest tools | protocol_adapters |
Conformance Fixture is test-only and excluded from consumer offerings. Knowledge
and Protocol Adapters both have tools: []; their library functions do not
constitute installed callable operations. The offering catalog preserves these
roles and excludes fixtures.
Consumer configuration
Section titled “Consumer configuration”Pack-owned namespaces and schemas reuse existing config:set, config:get and
config:unset. Configuration determines behavior within the consumer’s existing
execution scopes. It cannot grant paid access or widen filesystem/network policy.
Sidekick, Campus and Knowledge ship strict schemas alongside their pack guides.
Sidekick consumes task priority/list defaults; Campus consumes telemetry sample
limits; Knowledge accepts explicit validated ingestion document/byte budgets as
an application library. Ordinary manifest subprocess workers receive frozen
canonical pack_config. Omitted settings preserve existing behavior.
Security Assurance adds security:assess with a
strict security_assurance schema. Installed host/task/claim/bind/subprocess
verification records real start and finish receipts and host closure. Identical
normalized/SARIF input blocks at high and passes at critical, with distinct
kernel configuration hashes and assessment policy digests. Actual defaults,
accepted rules, configured finding/byte limits, deterministic provenance and
strict malformed input rejection are verified. Reports retain
UNVALIDATED status and provide evidence-review recommendations.
Consumer policy comes from canonical execution authority. Tool inputs and metadata cannot replace it, and pack handlers do not reread workspace files. Security Assurance runs no scanner, dereferences no location and writes to no provider; a policy pass is not certification.
Data Analytics adds data:check with a strict
data_analytics schema. Verification from local build archives passed: the pack
was installed into fresh locally initialised consumers (minimal init, with the
pack installed through builtin pack installation from local build archives) and
governed subprocess dispatch ran the same CSV and JSON snapshots under two
consumer policies and the defaults, observing distinct configuration digests
with identical source digests and check outcomes that differ across snapshots
(both policies fail the two-source snapshot). Repeats were byte-identical. Strict
malformed and oversized input was refused, report ceilings held, and
sample shedding kept every count and first-failure locator. No registry release
is asserted. The tool fetches no data and writes to no provider; snapshot comparison is not
implemented and a passing report is not a claim that the data is correct.
Customer Support adds support:triage with a strict
customer_support schema. Consumer-configured exact typed-equality routing and
escalation rules run in precedence order with no keyword or semantic matching;
unknown or missing attributes go to a fallback queue with human escalation and
no draft. Drafts are unsent and cite approved knowledge by id, revision and
optional digest. Reports carry input, configuration and per-ticket digests and an
actions receipt recording zero sends, ticket mutations and network calls. Remote
ticket retrieval, sending, updating and closing are not implemented. No registry
release is asserted; the catalog row is available because the manifest ships.
Domain packs
Section titled “Domain packs”Security Assurance, Data Analytics and Customer Support are the three domain packs in this release. Reliability Operations and Campus cover incident and facility and energy workflows.