Enterprise licensing

Governed agent systems you can inspect before you buy.

SCBE is an open-source-first command and evidence layer for AI work: agent-bus routing, durable provenance, benchmark receipts, and research-to-product adapters. Enterprise licensing is for teams that need integration rights, private proof review, source terms, and support beyond the public MIT package.

Product surfaces

License the parts that create leverage.

The public repo is useful by itself. The paid lane exists when a buyer needs source support, protected proof, private adapters, contractual terms, or a governed workflow installed around their own tools.

Public core

SCBE CLI and Agent Bus

Command-line workflows, governed tool routing, free-first model lanes, task ledgers, and agent-bus packets. This is the practical operator surface.

  • scbe-aethermoore-cli
  • scbe-agent-bus
  • scbe-aethermoore
Provenance

Longform Bridge and receipts

Hash-chained ledger events, verified landings, semantic anchors, resume packets, and cold-start audit checks for long-running AI work.

  • Immutable JSONL event chain
  • Landing verification and tamper checks
  • Private proof and licensing review path
Research preview

Reaction-state packets

A shared packet for lossy transformation work: code translation, tokenizer routing, chemistry decomposition, and agent workflow state.

  • Bijective / recoverable / ambiguous / invalid labels
  • Compound decomposition benchmark
  • Computational only, not wet-lab or medical advice
Evidence boundary

Claims stay attached to commands.

SCBE does not need inflated language. The useful claim is that it can preserve, classify, and explain state through transformations better than a single-field baseline in the tests it actually runs.

105/105 Longform chain integrity benchmark: structural and semantic attack cases.
3/3 Compound decomposition/recomposition local benchmark with RDKit available.
14/14 Full-system artifact readiness matrix; pass/partial status remains explicit.
12/12 Vector-field navigation ensemble-beam benchmark in the current proof lane.

These are local and project-scoped results unless a page explicitly names a third-party leaderboard. Enterprise buyers can request the exact commands, hashes, and artifact bundle used for any claim.

Commercial path

Three clean ways to start.

Keep the first step small when possible. If the workflow is sensitive, start with a scoped review and move to source licensing only after the fit is clear.

Low friction

Workflow Snapshot

$99

One workflow reviewed for drift, unsafe tool paths, missing recovery states, and the next three fixes.

Open snapshot
Pilot

Evaluation integration review

$500-$1,500

Review an agent workflow, benchmark surface, or CLI automation lane and return a concrete integration plan with claim boundaries.

Request review
Enterprise

Source and support package

$5K+

Scoped installation, private proof review, custom adapters, source terms, and support for teams building around SCBE.

Discuss license
Fit check

Best-fit buyers.

This is not a generic chatbot wrapper. It is useful when tool calls, state, audit, model routing, and reproducible results matter.

AI teams with tool risk

You already use agents or copilots and need a governed execution layer that records what happened, what was allowed, and what should not happen again.

Research groups with fragile context

You need long-running work to survive pauses, resumes, branch changes, and model swaps without losing the reason a decision was made.

Builders with cross-domain transforms

You translate code, data, chemistry-like state, or semantic packets and need loss notes plus recalculation receipts instead of hand-waved conversion.

Next action

Bring one real workflow.

The fastest useful conversation starts with an actual workflow, one success condition, one failure mode, and the tools the agent is allowed to touch.