motusos 0.3.13

Local control plane for work with claim, evidence, receipt, and work-ledger primitives

Motus CLI

The Motus CLI is the reference local interface for the work-packet and ledger loop. It is the reference implementation of the shipped Motus packet and ledger surface.

1. define or select a work item,
2. claim active ownership,
3. attach evidence while the work happens,
4. release with a terminal receipt.

Install

pip install motusos
motus --help

First Local Loop

motus install
motus init --empty --path .
motus doctor
LEASE_ID=$(motus work claim ADHOC-QUICKSTART-001 --intent "First local work item" --json | python3 -c 'import json,sys; print(json.load(sys.stdin)["lease_id"])')
motus work evidence "$LEASE_ID" test_result --passed 1 --failed 0
motus work release "$LEASE_ID" success

What this proves:

• the CLI is installed,
• the local workspace is initialized,
• a work item can be claimed,
• evidence can be attached,
• a terminal receipt can be emitted.

Reference Release Workflow

Motus now includes a bounded compiled release workflow surface:

motus release scaffold --release-id 0.3.13
motus release sync --release-id 0.3.13
motus release validate --release-id 0.3.13
motus release finalize --release-id 0.3.13

When running from the source tree instead of an installed CLI, bind to the repo package explicitly:

PYTHONPATH=src python3 -m motus.cli release scaffold --release-id 0.3.13
PYTHONPATH=src python3 -m motus.cli release sync --release-id 0.3.13
PYTHONPATH=src python3 -m motus.cli release validate --release-id 0.3.13
PYTHONPATH=src python3 -m motus.cli release finalize --release-id 0.3.13

That workflow forms the release as explicit work:

• one authored release-source.json,
• one generated workflow manifest,
• six generated stage packets,
• one generated receipt template,
• one generated metrics template,
• one strict final-receipt.json.

Workspace layout:

.motus/releases/{release-id}/
  release-source.json
  generated/
    workflow.json
    packets/*.json
    receipt-template.json
    metrics-template.json
  final-receipt.json

Rules:

• release_id must be a slug using only letters, digits, ., _, or -.
• release-source.json is the only authored release-instance surface.
• generated outputs are disposable and are rebuilt by sync.
• validate is no-write and fails closed on drift.
• finalize emits one immutable final receipt.

It is a reference workflow surface, not a hidden orchestration engine. The packets route to capability classes and keep runtime-brand decisions behind the adapter boundary.

Read Next

• Operator Guide
• Release Workflow Reference
• Architecture
• Specification Status
• CLI Reference
• Docs Index