npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@lumenflow/control-plane-sdk

v5.7.4

Published

Control plane sync contracts and adapters for LumenFlow runtime

Readme

@lumenflow/control-plane-sdk

Control plane sync contracts and adapters for LumenFlow runtime.

What It Provides

  • HTTP transport for control plane synchronization
  • Policy sync, approval flows, and evidence upload contracts
  • Adapter interfaces for custom control plane implementations
  • Machine-readable orchestration plan / launch / status contracts shared by local CLI and lumenflow.cloud

Orchestration State Contract

The SDK publishes a transport-friendly orchestration contract so humans, local agents, and hosted control-plane launchers can exchange the same initiative state without vendor-specific prompt parsing.

The contract is deliberately split into three documents:

  • OrchestrationPlanDocument Dependency-driven logical waves for an initiative.
  • OrchestrationLaunchDocument Launch receipts for a specific launch_attempt.
  • OrchestrationStatusDocument Reconciled live execution state, including next_safe_actions.

Key fields:

  • logical_wave The dependency-graph wave for a WU or wave group.
  • launch_attempt The specific orchestration attempt that wrote launch artifacts.
  • orchestration_state Shared execution state such as eligible, active, worker_returned, ready_for_finish, awaiting_merge, contaminated, and done.
  • claimed_mode Distinguishes local worktree execution from branch-pr / cloud execution.

The status contract is rich enough to represent:

  • local worktree execution and completion
  • branch-pr / cloud awaiting_merge state
  • explicit blockers and contamination paths
  • capacity-driven queuing via queued_by_capacity
  • orchestrator next steps via next_safe_actions

Parsing and Normalization

Use the parser helpers when reading JSON from local artifacts or cloud APIs:

import {
  parseOrchestrationLaunchDocument,
  parseOrchestrationPlanDocument,
  parseOrchestrationStatusDocument,
} from '@lumenflow/control-plane-sdk';

const plan = parseOrchestrationPlanDocument(rawPlanJson);
const launch = parseOrchestrationLaunchDocument(rawLaunchJson);
const status = parseOrchestrationStatusDocument(rawStatusJson);

The parsers preserve backward compatibility with older payloads that still omit optional orchestration fields. For example, legacy ready status values are normalized to the shared eligible state, and omitted logical_waves, capacity values, or next_safe_actions are derived or defaulted safely.

License

LumenFlow Proprietary. See LICENSE.