orchestrata_ultimate.core

Reference › orchestrata_ultimate › core

Orchestrata Core — interfaces, enums, traceability, config, domain, state, adapters.

The foundation layer of orchestrata-ultimate: the shared vocabulary, contracts and infrastructure access that every other package builds on, while core itself orchestrates nothing and (by decision K6) imports nothing from the cxp, postman, orchestrator or kernel packages. The curated core narrative tells the story; the architecture overview places it at the bottom of the import layers.

By role:

• Base classes and domain: base (entity, error, repository, service, the @traces decorator), domain and enums.
• Contracts: protocols (the canonical protocols), interfaces (the older names, aliased), and the CXP message in packet.
• Infrastructure access: infra_config, env_bootstrap, redis_factory, graph_factory with the graph repository seam, prolog_adapter with janus_bootstrap, config and state. The no-literal-fallback rule is in infra_env_rule.
• Observability and traceability: logging, monitoring, tracing, traceability and traceability_utils.
• Parallel test execution: threading.
• Claude Code integration: adapters.
• Utilities and gate support: patterns, artifact_store, capability_mesh, atomic_json, banned_libraries, gate_waivers, lru_cache, paths, standards, graph_directives and isolation.

A process starts by loading the environment contract, then asks the factories for Redis, graph or Prolog access; subsystems talk through the protocols and the packet. There are no command-line entry points here. To start reading, take base, protocols and infra_config.

Curated narrative

The hand-written story of this package: orchestrata_ultimate.core.

92 modules, 18,404 lines of code.

Subpackages

Modules

Dependency diagram