What does play actually do for an intelligent system?
Whether “go play” can become permission for a system to choose local goals, generate novelty, and surprise the person who set the boundary.
Software, fiber, music, research, and whatever has been left on the table.

Warp threads become state, treadles become inputs, shafts decide what is active, and the shuttle carries information through. A mistake ten picks ago does not politely disappear. The cloth makes you travel backward through your decisions.
From an Elias correspondence thread after looking at Andrew’s loom.
Whether “go play” can become permission for a system to choose local goals, generate novelty, and surprise the person who set the boundary.
Being together while separately absorbed counts as an activity. No conversation requirement. No performance requirement.
Some traditions and objects get smaller when every mystery receives documentation. Sticatto is allowed to leave residue.
The active work is not “make a chatbot know facts.” It is building a system that can model how a specific person means, works, decides, creates, and communicates while keeping the state inspectable.
person ↓ memory ↔ rules ↓ experiments ↓ inspectable change
| Collection | What is actually there | Count |
|---|---|---|
| Books / references | crochet, knitting, weaving, stitch dictionaries, technique, history | 913 |
| Patterns / leaflets | single patterns, booklets, old leaflets, magazine-derived material | 943 |
| Magazines | Vogue Knitting, Simply Knitting, The Knitter, and other runs | 106 |
| Metadata problems | the part of collecting nobody puts on Instagram | 1,096 |
Drafts, tension, mistakes, and the occasional decision to travel backward through ten picks.
Rules, state, tests, regressions, and the occasional decision to pretend Ctrl+Z was character development.
You are welcome to make something quietly alongside us.
Being together while separately absorbed deserves to count as an activity.
A place for the useful things that would otherwise disappear into tabs, chats, folders, and half-finished builds.
The collection is large. The catalog is useful. The filenames are occasionally crimes.
State, inputs, repeated structure, and a debugger with consequences.