kmshdev/nautilus-agent-kit/building-nautilus-actors

Build a Nautilus actor

Input: the actor's input streams, derived output and lifecycle requirements, plus existing code when repairing a component. Infer established conventions from the target project; do not invent trading rules. Output: a native order-free component with the requested delivery/state behavior and evidence at the affected callback or runtime boundary.

Bundled examples use =0.64.0 and Rust 1.98.1+. Existing applications retain their lockfile, features and source overrides unless an upgrade is requested. For upgrades or framework workarounds, use version and integration.

Instructions

1. Identify the missing behavior and its input/output identity. Read

the actor guide for the affected API, not every reference.

1. Implement DataActor, one DataActorCore, Debug and nautilus_actor!.

Subscribe/request after registration; keep order methods out of the actor.

1. Preserve causal timestamps and one indicator update owner. Bound warm-up and

restore subscriptions/timers on the relevant lifecycle transitions.

1. Exercise the affected path. For delivery defects, include native

registration and dispatch rather than only directly calling the hook. Report what that evidence establishes and any unresolved failure.

Use runtime contracts for cross-component ordering, connection recipes for publication or history handover, the offline example for native dispatch, and source evidence for version disagreements.

Use typed run configuration, component composition, and the Rust test ladder when those concerns are affected.

Examples

• "Count quotes and custom signals": use the order-free offline actor. In

assets/quickstart, run cargo test --locked then cargo run --locked; expect four quotes, one signal, zero orders and zero positions.

• "My timer advances but no callback runs": match returned TestClock events

to handlers, release the clock borrow, then execute them.

• "Submit a bracket": this is a Strategy job, not an actor extension.

Deliver the requested artifact with focused verification and material limits. Follow the user's authorized scope and the target application's ownership.