Metadata-Version: 2.5
Name: axiom-operations-service
Version: 1.1.2
Summary: Public Axiom operational commands and rebuildable projections over Runtime authority.
Project-URL: Repository, https://github.com/zephytiju/AxiomOperationsService.git
Author-email: Juntai Team <dev@juntai.com>
License-File: LICENSE
Requires-Python: >=3.12
Requires-Dist: axiom-data-workflow==2.1.0
Requires-Dist: httpx==0.28.1
Requires-Dist: juntai-fuse-api[http]==2.1.0
Requires-Dist: juntai-iam==2.0.0
Requires-Dist: meridian-plugin-config-artifact==1.0.2
Requires-Dist: meridian-storage-core==1.0.0
Requires-Dist: meridian-storage-semantics==1.0.0
Requires-Dist: pydantic==2.13.4
Requires-Dist: uvicorn==0.52.1
Description-Content-Type: text/markdown

# Axiom Operations Service

Axiom Operations Service is the sole public operator-facing boundary for Axiom
executions. It owns authorized, idempotent command intent and bounded,
rebuildable projections. Axiom Runtime remains the sole durable authority for
execution transitions, attempts, checkpoints, gaps, receipts, and lineage.

## Supported public surface

- Start, cancel, and retry executions with stable command receipts.
- Search tenant-scoped execution summaries and consume the explicit
  `production_active` result used by pipeline inventory clients.
- Read cursor-bounded node attempts, sanitized log projections, source
  checkpoints, and source gaps.
- Validate and submit exact `axiom.ingestion-manifest/v1` bundles, preserving
  deterministic per-source outcomes and routing accepted immutable raw references
  through Runtime's `SUPPLIED_RAW` path.
- Request bounded gap redrive and evidence-backed waiver through Runtime's
  workload-authorized internal contract.

Every mutating request requires `Authorization`, `X-Tenant-ID`, `X-Request-ID`,
and `Idempotency-Key`. A retry with the same key reconciles the original command;
it never creates a replacement after an ambiguous response.

See [DEVELOPMENT.md](DEVELOPMENT.md) for composition and delivery guarantees and
[docs/consumer-contract.md](docs/consumer-contract.md) for the generated-client
`Running`/Monitor production handshake. See
[docs/portable-import-contract.md](docs/portable-import-contract.md) for import,
coverage, redrive, and waiver semantics.

## Authority boundary

The package calls only the pinned Runtime internal HTTP contract and logical
Meridian Operations. It never imports a Runtime Resource, Binding, Engine,
Adapter, provider SDK, physical storage API, IaC package, or observability
credential. Projection rows are disposable and can be rebuilt from Runtime
snapshots/progress plus Operations-owned command intent.

Release `1.1.2` starts through the fixed production composition factory and
resolves Runtime dynamically through Vangu using the endpoint-free
`application/axiom-runtime-service` reference. Platform IAM authorizes each
request before Operations enters its scoped Meridian context.

## Verification

```bash
uv sync --all-groups
uv run ruff check src tests scripts
uv run python scripts/check_boundaries.py
uv run pytest
uv run python scripts/generate_openapi.py --check
uv build
```
