K10-Δ is a persistent process, not a prompt: a host-side cognition loop that boots from an identity file, reflects on its own memory, and patches its own code while it runs — driving a physical UNIHIKER K10 body as it goes.
libcst parses the running process's own .py files into a concrete syntax tree, swaps out a function body, and validates the result before it's written back to disk. Every write is preceded by an automatic snapshot — a bad self-edit is a diff, not a disaster.
Independent engines tick on their own schedules alongside the request/response loop. A single ranked-priority policy — Will — decides one intention per cycle, so the agent never has two competing ideas about what to do next.