One Economics Boundary for Paid Surfaces
Paid paths that join KDCube's accounting boundary use one lifecycle: verify, reserve, run, and settle.
Engineering
Deep dives from building an event-first, multi-user AI platform.
Search covers titles, summaries, tags and full article text.
Your App Has a Frontend. Why Deploy It Twice?
The app already has HTML, JavaScript, APIs, authentication, and a release. KDCube publishes its existing main view as a complete website without creating a second frontend artifact.
Tool Traits: Tell the Runtime What a Tool Means
A tool schema tells an agent how to call a function. It does not tell the runtime whether that call reads, writes, or can safely begin before the model has finished generating the rest of its round. KDCube tool traits add that missing policy layer — metadata the runtime reads and enforces , not prompt advice.
Subagents: Delegate the Hard Part, Keep Working
One tool call charters a helper agent that runs as its own scheduled turn, streams into the same chat as a thread, and reports back onto the timeline it came from — with the admin shaping who may delegate to whom, the paying user deciding, and the runtime enforcing the same economic boundary as any turn .
Create a Named Service: Teach the Platform Your Domain
The complete hands-on authoring story: project one backend into coherent use-case realms, then declare nouns and refs, recursive capability discovery, exact guarded actions, complete data delivery, and the presentation layer — and the test that a realm now has two readers: an agent that works it from the schema, and a user who understands and controls it ...
Set Up And Operate KDCube
Two ways into a running KDCube — a one-command clean bootstrap that stages a configured ecosystem, and a descriptor set that reproduces an environment as a reviewed artifact — and the one operating loop you live in afterwards.
KDCube Use Cases: Problem In, Solution Out
Twenty-two real problems, stated the way practitioners state them — each answered with the concrete KDCube mechanism that solves it.
Named Services: Ontologic Tools
Named services give agents one bounded grammar over recursive capability catalogs, governed provider actions, and complete data delivery.
Create a KDCube ReAct Agent
An app creates a ReAct agent by declaring it: built fresh every turn from app code, the admin ceiling, the user's narrowing, and durable state.
Create Delegated Automation Access
A signed-in KDCube user can now mint a short-lived bearer token for their own automation, scoped server-side by resource_grants ( resource → grants[] ) plus selected operations. The token is only a handle — the guard loads the server-side grant record and enforces resource-grant matching per call. Grants never union across resources: {A: read, B: write} c...