Standing intents

An offhand sentence becomes a thing the presence does on its own, on a schedule, forever — until you change it.

A standing intent is the autonomous mode made concrete. You say what you want once; the presence turns it into a small program in its space, wakes on a schedule, and acts within policy — speaking up only when its own rule says to.

From a sentence

You don't write the job. You describe the outcome and the condition; the presence writes and owns the code.

chat

you · every morning, check my Base positions and tell me only if something moved more than 5%.

That becomes, in its space:

~/positions.intent

schedule: daily 08:00
read: chain.positions(wallet)
recall: "thresholds", "watchlist"
if: any move > 5%
then: message(you, summary)
else: remember ("checked, quiet", key="routine")

Anatomy

Part	Is	Notes
schedule	when it wakes	Interval or time. Bounded compute means pick the loosest cadence that still catches what matters.
read	cheap signal	Usually the chain skill. Read first; reason only if needed.
recall	memory keys	What “moved”, “a lot”, “my safe” mean for you — pulled from salient memory.
condition	the gate	The early-exit. Most wake-ups should do nothing and cost almost nothing.
action	act or speak	Within policy. Above confirm_over, it pauses for you instead of acting.

Cost & the early-exit

A standing intent on a deep route firing every minute is the one real way to spend money quietly. The pattern that prevents it: read cheap, reason rarely. The chain skill read is inexpensive; the route should only engage when the condition is already true.

Pair this with a per-task route rule (see Effort): sonnet to notice, opus to decide — and only when there is something to decide.

Trust & audit

Before an intent has real money behind it:

Check what it will rely on — yuzu memory ls for the thresholds it recalls (see Inspect & edit).
Confirm the policy caps it the way you expect, especially confirm_over.
Watch its first runs on the events stream before trusting it unattended.

Managing them

shell

yuzu intent ls
yuzu intent pause positions
yuzu intent rm positions

Intents persist in the space and across route changes. They stop only when you pause or remove them — that permanence is the feature.