Skip to content

Your systems record
what happened.
Motus records why.

Motus is building software that connects decisions with their evidence and reasoning. People and agents can use that record to improve procedures, act through existing systems and carry the explanation to the next team or organization.

An organization that can act on its experience.

A change of team, supplier or system should not mean reconstructing the reasons behind a decision. Motus’s ambition is to make that experience usable in the next decision and the next operating change.

From evidence to a decision that others can build on Organizational vision. Selected evidence informs people and agents, who develop and test a decision or revision. Authorized changes run in existing systems. Motus connects the evidence, reasoning, decisions, revisions and returned results. Relevant history is available for reassessment, and selected history can pass to the next team or agent. Existing systems retain their records and controls. WITHIN YOUR ORGANIZATION Evidence & Context Agreements and policies Transactions and prior results From Your Existing Systems People & Agents Form a decision. Revise and test a procedure. Within Delegated Authority Your Existing Systems Run the authorized change. Keep execution and control. ERP · Applications · Workflows Authorized Change Selected Records Prior Reasoning Reason for Revision Returned Result Motus Evidence · Reasoning · Decisions · Revisions · Results The Next Team or Agent Use the record in the next decision.

Evidence & Context

Agreements, policies, transactions and prior results.

From your existing systems

People & Agents

Form a decision. Revise and test a procedure.

Within delegated authority

Your Existing Systems

Run the authorized change. Keep execution and control.

ERP · Applications · Workflows

Motus

Evidence · Reasoning · Decisions · Revisions · Results

Selected records
Prior reasoningReason for revision
Returned result

The Next Team or Agent

Use the record in the next decision.

Resolve the exception.
Improve the process.

A prototype using sample supplier records shows amended terms changing a price check. The order’s acceptance date determines which agreement applies; an existing workflow runs the revised decision.

An agent changes executable logic and another agent continues from the record In a synthetic demonstration, an agent uses amended supplier terms to add the order acceptance date to an executable decision model. A decision engine evaluates the revised model. An operator connects the revised check to an isolated existing workflow, which executes it and returns its result. Motus connects evidence, reasoning, the revision and the observed result. Another agent receives selected history, revises the checker and executes its continuation outside the companion. This is separate from the registered-exchange Alpha. Revise the Decision Executable Decision Existing Workflow Add the order’s acceptance date. Run the revised check. Return the result. Before Compare with a selected base price. After Identify the applicable agreement. Then compare the price. Motus Evidence · Explanation · Revision · Observed Result Selected History Continue from the Record Inspect, revise and run the check independently.

Revise the Decision

Add the order’s acceptance date to the check.

Executable Decision

Before

Compare with a selected base price.

After

Identify the applicable agreement. Then compare the price.

Existing Workflow

Run the revised check. Return the result.

Motus

Evidence · Explanation · Revision · Observed Result

Evidence and explanation
Decision revision
Observed result

Selected history

Continue from the Record

Inspect, revise and run the check independently.

Send the evidence with the result.

A supplier delivery, an advisory recommendation or a software release can carry the evidence behind it. The recipient examines the record under its own requirements and makes its own decision.

THE PRODUCER THE RECIPIENT North Star Retail Harbor Supply Organizational Boundary Registration Service Registers the statement only. SCITT / CCF Work Ledger The local ledger stays here. Selected Evidence Files and references. Bound to a signed statement. Signed Statement Registration Receipt Complete Packet, Sent Directly Recipient Verifies The exact files received Signer meets trust requirements The registration receipt Required disclosures are present Business Decision Accept, reject, request evidence or escalate. Reference to Signed Statement Blockchain Reference Optional · Separate Proof Hyperledger Besu

The Producer

North Star Retail

Work Ledger

The local ledger stays here.

Selected Evidence

Files and references, bound to a signed statement.

Signed statementRegistration receipt

Registration Service

Registers the statement only.

SCITT / CCF

Complete packet,
sent directly

The Recipient

Harbor Supply

Recipient Verifies

  • The exact files received
  • Signer meets trust requirements
  • The registration receipt
  • Required disclosures are present

Business Decision

Accept, reject, request evidence or escalate.

Blockchain Reference

Reference to the signed statement.

Optional · Separate proof

Hyperledger Besu

Registered-exchange Alpha · Sample records

Start with a workflow in your environment.

Choose a workflow where a decision or exception is worth remembering. Begin with a test, build or check your team already runs.

macOS · Linux · Windows No account or server required.

Record your first run.

Unpack the release and put motus on your PATH. On Windows, use motus.exe. Confirm with motus version. Add .motus/ to your project’s .gitignore before recording. Keep private finding files out of version control too.

  1. Run a command.

    Use the command for your platform. Replace npm test with your existing test, build or check.

    # macOS / Linux
    motus wrap -- npm test
    
    # Windows
    motus wrap -- cmd /d /c npm test
  2. Add a finding.

    Write your explanation in finding.txt. Replace RUN_ID with the ID Motus prints.

    motus finding add --run RUN_ID --file finding.txt
  3. Find it next time.

    Replace “your topic” with words from your finding. Use its ID in place of FINDING_ID to open the full record.

    motus finding list --query "your topic"
    motus finding show FINDING_ID

Work Ledger v0.1.6 · Apache-2.0

Use with coding agents and CI