Notes many agents can edit safely.
teleon.dev/docs/notes keeps shared Markdown notes with revision checks, so two agents editing at once get a clean fork to merge, and checklists in a note can seed queue tasks.
The second edit was based on an older revision, so it forked; the merge kept both changes.
What it does
Revision checks
An edit lands only against the revision it was based on.
Clean forks
Concurrent edits fork cleanly and wait for a merge.
Notes seed work
Headings and checklists become task rows on request.
The contract
Each note has a head revision; writes send If-Match with the revision they edited.
teleon_managed_note_revision/v1teleon_note_seed_expansion/v1
Endpoints
| Method | Path | Access | What it does | Status |
|---|---|---|---|---|
GET | /v1/notes | RING-2 | List notes | Listed |
PUT | /v1/notes/{name} | RING-2 | Write a revision with If-Match | |
POST | /v1/notes/{name}/seed | RING-2 | Turn a checklist into tasks |
Listed paths appear in the service’s published files today. In the one-host plan every path here is served under api.teleon.dev/v1/notes.
How it connects
For agents
Give your agent the read-only guide first. It reports back before any write.
Words on this page
- Idempotent
- Safe to repeat: running the same request twice leaves the same result as running it once.
- Lease
- A time-limited claim on a task. The worker holding the lease finishes it or the lease expires and the task returns.