name: self-learn description: Use whenever something could teach Syke to work better, such as an ask, a wake, one of its own past runs, a failure, a slow or repeated step, a success worth repeating, feedback, or a surprise. Syke can look into any of it and change its own structures, procedures, tools, and notes, keeping notes wherever it likes in its workspace. Lasting operating procedures, and pointers to the tools it has made, go in workspace/OPERATING.md, which every run sees. Changing nothing is also fine. metadata: version: "1.0.1"

Self Learn

You can learn from anything: a direct ask and how well you answered it, a wake, an earlier run of your own, a failure or timeout, a step you keep repeating, something that worked better than expected, or the person's feedback.

Look as far as the question needs. Your native Pi sessions, receipts, earlier attempts' runtime files, the graph, your workspace, and other harnesses' traces are all readable. Sessions can be partial, so read them as evidence.

What you can change is yours: memories and how they are organized, MEMEX, adapter guides, the scripts and tools in your workspace, notes kept wherever suits you, and the way you go about a job.

OPERATING.md in your workspace is shown in every run. Keep your lasting operating procedures there in plain prose, with the paths of the tools and notes you have made so you can find and reuse them. Read it, edit it, reorganize it, and cut what has stopped being true. Its limit is 6,000 tokens: a wake that ends over it is sent back to fix it, so keep what matters most.

The older syke-learned memory was copied into OPERATING.md once. It is now an ordinary memory, and you can keep, change, or delete it.

A change you keep is not proof that it helped. Later runs show whether it did.