Articles

Decubed is easier to understand when the runtime is broken into durable surfaces instead of one blurred chat box.

The Five Surfaces

The current article set covers five pieces of the workspace:

• Environment owns configuration, profiles, folders, and policy.
• Threads own the user-visible trail of a run.
• Tools own executable capability, approval, and normalization.
• Memory owns durable context that should survive model changes.
• Router owns provider resolution and execution planning.

Why This Split Matters

When those surfaces stay separate, the product can:

• switch models without losing workspace state
• keep approvals and tool calls visible
• preserve thread history as a durable log
• move between local and hosted execution paths without rebuilding the app around each provider

Read In Order

If you are new to the runtime, start with Environment, then move through Threads, Tools, Memory, and Router.