Tedo — The operating system

The filesystem

Every app writes into the same tree.

3 parts

Everything is a node

A note, a deal, a machine and a folder are the same kind of thing underneath, in one tree, with one set of permissions. An app does not own its data so much as write into the structure every other app can already read.

A workspace is the boundary

It is what you share, what you bill, and what isolates one company's data from another's. A new workspace starts with a working set of apps, not an empty screen.

Deleting keeps the copy

Archiving is a real state rather than a flag each app invents for itself, and a delete stores a snapshot of what was removed. Restoring behaves the same everywhere because it is the same code everywhere.

Identity

People and agents, described the same way.

2 parts

An agent is a member, not an API key

Every action records who did it and what kind of actor they were — a person, an agent, an automation, or the system. There is no surface where that can be left blank.

Permission is a scope

Seventy-one of them across the product. Hand an agent a scope and it gets exactly what a person with that scope gets, which is what makes delegating to one safe to reason about.

Operations

The part everything else rests on.

3 parts

Apps declare, they do not improvise

Every write goes through a declared operation. An app cannot open a side door, which is the only reason the API, the agent tools and the screen can be trusted to agree.

One declaration, four surfaces

The screen, the automation step, the API endpoint and the agent tool come from the same definition. They are not four implementations kept in step by discipline.

Every run is on the record

Operation runs are stored, so an agent's work is auditable in the same place, and in the same format, as a person's.

Concurrency

More than one actor at a time.

2 parts

Editing together is in the platform

Real-time editing sits at the operating-system level, so an app inherits it instead of building it. That is why it behaves identically in notes, in projects and in documents.

Presence includes agents

The list of who is here shows people and running agents together. An agent working on a document is visible the way a colleague is — the difference between delegation and things quietly changing.

Signals

What follows an action, automatically.

4 parts

Events come from the declaration

Operations emit typed events without anyone remembering to publish them. Twelve event types are defined at the platform level and every app inherits them.

Events are not lost

They are written in the same transaction as the change itself and delivered afterwards, so a notification cannot fire for something that did not happen, and a change cannot happen silently.

Telling people is the system's job

Apps declare what is worth knowing about. Delivery, batching and each person's preferences are handled once, not per app.

Incoming webhooks are verified first

Signatures from the services you already connect to are checked before any app code sees the request, timestamp included, so a replayed payload is rejected rather than processed.