motusos 0.3.6

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

Motus

Motus is a local control plane for work. Define the work item. Attach proof as it happens. Close with a receipt you can trust.

What Motus Solves

Important work disappears into chat, tickets, logs, and memory. Motus gives that work a bounded transaction path and a durable receipt.

What Motus Is

Motus is the system that:

1. defines work as a bounded transaction,
2. records ownership with a lease,
3. attaches structured evidence,
4. closes with an explicit outcome,
5. preserves the result as durable work lineage.

Runtime session inspection is available as a supporting capability, but it is not the primary day-1 product surface.

What Motus Is Not

Motus is not:

1. an orchestration app,
2. a replacement for Git, CI, N8N, ticketing, or ERP,
3. a cloud control tower.

Install

pip install motusos
motus --help

Day 1 (10 Minutes)

motus install
motus init --lite --path .
motus doctor
LEASE_ID=$(motus work claim ADHOC-DAY1-001 --intent "Day1 smoke" | awk -F': ' '/^Lease ID:/ {print $2}')
motus work evidence "$LEASE_ID" test_result --passed 1 --failed 0
motus work release "$LEASE_ID" success

Expected:

• motus doctor reports healthy.
• Work is claimed with a lease ID.
• Evidence is attached to that lease.
• Release returns a success receipt.

Why this loop exists:

• the work item is the atomic unit,
• the deterministic path is claim -> evidence -> release,
• ADHOC-* IDs are for solo/day-1 work,
• managed lanes use pre-registered work IDs.

Learn More

• Implementation Guide
• Architecture
• CLI Reference
• Docs Index

Links

• PyPI: https://pypi.org/project/motusos/
• GitHub: https://github.com/motus-os/motus
• Contributing: ../../CONTRIBUTING.md
• Security Policy: ../../SECURITY.md

License

Apache License 2.0. See LICENSE.