OmniMarket
OmniMarket is the portable ONEX (OmniNode eXecution) workflow package registry — the consolidation target for all OmniNode automation logic. It ships 407 contract-backed node entry points covering build loops, PR lifecycle management, sweeps, projections, ledger, memory orchestration, session management, and diagnostics. Platform wrappers invoke Market nodes for execution, but never own the business logic themselves.
Every node is a self-contained package with a contract.yaml declaring its
handler bindings, input/output models, subscribed and published topics, FSM
transitions, and terminal event. The runtime loads those contracts to wire
event-bus subscriptions and inject handler dependencies — handlers never
hardcode topic strings or construct their own collaborators.
| Archetype | Purity | Description |
|---|---|---|
compute |
Pure | Stateless transformation. No I/O side effects. |
reducer |
Pure | FSM state transition. Emits next-state events. |
effect |
Effectful | Performs external I/O (API calls, file writes, deployments). |
orchestrator |
Effectful | Composes sub-handlers via FSM. Owns in-process state. |
Documentation
Architecture, guides, and reference documentation for this repo live in the OmniNode knowledge base, not in this repository:
- Package model — layers, node package shape, contract rules
- Skill, package, and node boundaries
- Dependency boundary
- Event registry
- Build-loop migration boundary
- Node catalog
- Node metadata reference
- Node testing pattern — including how to add a node to the harness
- Skill-backing node pattern
Governance policy and operator runbooks are not part of this repository.
Repository Layout
omnimarket/
├── src/omnimarket/
│ ├── nodes/ # All node packages (node_<name>/)
│ ├── events/ # Shared event models (ledger, envelopes)
│ ├── models/ # Cross-node shared Pydantic models
│ ├── protocols/ # Shared protocol interfaces
│ ├── projection/ # Projection helpers and base classes
│ ├── routing/ # Event routing and dispatch
│ ├── intelligence/ # LLM and inference abstractions
│ ├── inference/ # Model selection and endpoint routing
│ ├── classifiers/ # Shared classification logic
│ ├── cli/ # CLI entry points
│ ├── config/ # Configuration models and loaders
│ ├── configs/ # Configuration files and overlays
│ ├── data/ # Static data assets
│ ├── registry/ # Node registry helpers
│ ├── enums/ # Shared enumerations
│ ├── adapters/ # Adapter templates for external platforms
│ ├── runtime/ # Runtime version handshake utilities
│ ├── logging/ # Structured logging helpers
│ └── experiments/ # Experimental sub-projects (ADK eval, etc.)
├── tests/ # Golden-chain and contract tests
├── scripts/
│ ├── ci/ # CI gate scripts (runtime sweep, metadata check)
│ ├── validation/ # Additional validation scripts (leaked literals, contract overlay boundary, topic lint)
│ ├── generate_node.py # Node scaffold generator
│ ├── generate_adapters.py # Adapter output generator
│ └── lint_no_hardcoded_topics.py
├── docs/ # Non-prose artifacts only: brand assets, OCC
│ # work-tracking contracts, generated evidence
│ # and audit data. Prose lives in the knowledge
│ # base (see Documentation above).
├── pyproject.toml
└── CLAUDE.md
A node package is src/omnimarket/nodes/node_<name>/ with contract.yaml,
metadata.yaml, and handlers/; orchestrators add protocols/, and nodes may
add models/ and node-local tests/. Nodes are discovered through the
onex.nodes entry-point group in pyproject.toml — the runtime iterates those
entry points, loads each contract.yaml, and wires subscriptions automatically.
Adding a Node
uv run python scripts/generate_node.py --name node_<name> --type compute
Then register the entry point in pyproject.toml under
[project.entry-points."onex.nodes"], add a golden-chain test at
tests/test_golden_chain_<name>.py proving the contract over EventBusInmemory,
and run the validation gates below. The full pattern — contract fields, metadata
fields, harness requirements, and the canary nodes to copy from — is in the
knowledge base pages linked above.
Common Commands
# Install dependencies
uv sync --all-extras
# Run tests (excluding Kafka-dependent tests)
uv run pytest tests/ -v --tb=short -m "not kafka"
# Unit tests only
uv run pytest tests/ -v -m unit
# Lint and format
uv run ruff check src/ tests/
uv run ruff format --check src/ tests/
# Type-check
uv run mypy src/omnimarket/ --strict
# CI gates
uv run python -m omnimarket.nodes.node_runtime_sweep --import-check
uv run python scripts/ci/check_node_metadata_dependencies.py
Test markers: unit (isolated), integration (multi-component), slow (>1s),
kafka (requires a running broker).
What This Repo Owns
onex.nodesentry points for contract-backed workflow nodes.- Node package directories under
src/omnimarket/nodes/node_*. contract.yamlandmetadata.yamlfiles defining node interfaces, capabilities, dependencies, and runtime expectations.- Handler logic for compute, reducer, effect, and orchestrator nodes.
- Adapter templates for external platform integrations.
- Golden-chain tests and metadata checks proving node contracts with an in-memory event bus.
- Shared Market primitives (projection, inference, routing, intelligence, ledger, and metadata helpers) that prevent cross-node reach-in.
What This Repo Does Not Own
-
Platform-specific UX prompts, slash-command presentation, editor rules, or user-facing skill copy — those belong in the wrapper repo for that platform.
-
Concrete infrastructure services (Kafka, Postgres, Docker, secrets) — those belong to the runtime/infrastructure layer.
-
Core ONEX primitives (
RuntimeLocal,EventBusInmemory, envelope types, shared validators) — those belong toomnibase_coreand compatibility packages. -
Governance policy and documentation evidence — those belong to
onex_change_control. -
Memory persistence semantics and storage adapters — Market may host runnable memory workflow nodes, but the memory domain is owned by the memory repo.
-
Prose documentation — it belongs in the knowledge base (see Documentation).
Retention Effect Bindings
The consumer-flow and dead-letter prune effects resolve their archive and
DB bindings at the effect boundary, after the scheduled interval gate. Shared
overlay and secret-store resolution lives in node_prune_binding_effect, a
library-style effect invoked in process without topics or subscriptions.
config.<kind>_prune.binding accepts an absolute archive_dir and either
database_url or database_secret_ref. The shipped bindings are unconfigured;
a missing key returns a typed refused result with zero pruning. Skipped ticks
resolve neither binding and return sink_location: null.
Runtime instances also read the normal typed ~/.omnibase/overlay.yaml, or the
file selected by the bootstrap pointer OMNIMARKET_PRUNE_BINDING_OVERLAY.
The file must be owner-only (chmod 600); an explicitly selected missing or
invalid file refuses. Configure its services.prune section, for example:
services:
prune:
consumer_flow.archive_dir: /var/lib/onex/archive/consumer-flow
consumer_flow.database_secret_ref: database.consumer_flow.retention_url
dead_letter.archive_dir: /var/lib/onex/archive/dead-letter
dead_letter.database_secret_ref: database.dead_letter.retention_url
These keys override contract bindings. A database reference replaces a contract URL, and a URL replaces a contract reference. References resolve through an injected secret store, the configured lane mapping, or the existing local credential store; no ambient DB-value environment fallback is used. Manual CLI archive options remain explicit, and its DB uses the same boundary. Archive verification, encryption, source drift, retention bounds, and exact-key deletes continue to govern every pruning run.
1 maintainer
Metadata
1 maintainer
Release files for omnimarket 0.4.305
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| omnimarket-0.4.305.tar.gz | 16.2 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| omnimarket-0.4.305-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 25.9 MB
Release files / omnimarket-0.4.305.tar.gz
| Download URL | omnimarket-0.4.305.tar.gz |
|---|---|
| Size | 16.2 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
345e0d12939be343db6f344e2a0432b6b68d7a0130967d651559ec5d3f740617
|
|
BLAKE2b-256 checksum How to use checksums |
9db30bee16419f9eb52481c71edb17b1ef28ba6fe04134fb5f982392cf495aaa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.12.23 {"installer":{"name":"uv","version":"0.12.23","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / omnimarket-0.4.305-py3-none-any.whl
| Download URL | omnimarket-0.4.305-py3-none-any.whl |
|---|---|
| Size | 9.6 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
781e0ab0b40a356698f955a1b9a7e14885f599ee49699839664c0e6e7c9f4663
|
|
BLAKE2b-256 checksum How to use checksums |
d790ac758982536e96cf83de9c98ab7cd6ecfbba9a96f26bc78bf3fce88e1a03
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.12.23 {"installer":{"name":"uv","version":"0.12.23","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
