The Pinboard of Proxies
Objects from many apps sit together on one board without merging their databases. Every durable card is a proxy: canvas owns the card; the provider named by the ref owns the object.
KDCube Writing
Engineering deep dives, industry perspective, implementation notes, and practical recipes.
Search covers titles, summaries, tags and full article text.
What the agent always sees: a live map of its workspace
The native KDCube ReAct Agent gets a live map of its disposable, distributed workspace: what is local now and what survives as a durable ref, so it can read, pull, or checkout by intent.
The model input — what the agent receives, and where it comes from
One ordered block of input, assembled fresh for every call: a per-agent instruction envelope, tool and skill catalogs, a growing timeline, and a volatile tail — each part with a provenance.
The live view — the agent's attention zone, and what's in it
The attention zone at the tail of the model input: the sources pool and the live view — never cached, rebuilt every round, the one place checked first.
How the model input is cached — and kept fresh
How the model input is cached and kept fresh: four moving cache points, the never-cached tail, marked cold turns, TTL pruning, and compaction.