Working with Threads
Threads group related records into workflows. Learn to create, track, and close threads.
What you'll learn
A thread is a sequence of related records that represent a workflow. Every task, conversation, and coordination flow is a thread. In this tutorial, you'll create a thread, add records to it, and close it.
Create a thread
Every intent opens a new thread automatically:
spl intend "Migrate the user database to the new schema"The output includes a thread ID:
✓ Record created on thread th_7f3a...All subsequent records on this thread reference this ID.
Add records to the thread
Record what happens as you work:
spl do "Backed up existing database" --thread th_7f3a...
spl do "Applied migration script" --thread th_7f3a...
spl know "All tables migrated, zero data loss" --thread th_7f3a...Each record builds the story of the thread — what was intended, what was done, and what was observed.
View the thread
spl thread records th_7f3a...This shows every record on the thread in chronological order, with the actor, act type, and body of each record.
List all threads
spl thread listShows all active threads with their latest activity, participant count, and record count.
Close a thread
A thread closes when a KNOW fulfills its opening intent (frozen foundation
F13). Pass --fulfills on the closing KNOW: bare, it resolves and fulfills
this thread's opening INTEND for you.
spl know "Migration complete, all services verified" --thread th_7f3a... --fulfillsTo fulfill a specific record rather than the thread's opening intent, name it:
--fulfills <record-id>. Either way the KNOW carries body.fulfills, and the
thread's state is a fold over its records: folds and status views read that
fulfills link to mark the thread's work done. The complete record chain, from
intent through execution to the fulfilling observation, is preserved as an
immutable history.
Capture insights
After completing work, record what you learned:
spl learn "Schema migrations should run in maintenance windows to avoid connection timeouts"LEARN records capture insights that improve future work. They persist in your actor memory and inform future decisions.
What's next
- How threads work — lifecycle, fork and merge, assertions
- How records work — the 8-field immutable unit
- Task management — structured workflows with success criteria
Your First Task
Create a task with success criteria, complete it, and see trust evidence accumulate.
The Studio in five minutes
Open your workspace in the browser and use all three shapes. Read a ledger, complete a sentence to share a thread, preview it as a guest, and read the address you can hand to someone.