Markdown for engineering teams

The writing surface is the product.

Write the RFC below. It is the real editor: local, keyboard-first, and saved on this device.

rfc-018-bounded-retries.md
Not saved yet 0 words · 0 characters

Three constraints

A document should outlive its editor.

Keyboard-first

Commands stay close to the keys. Format a selection, open the palette, or continue a list without reaching for a toolbar.

Offline-first

The editor keeps working when the train enters a tunnel. Changes save locally first and sync when a connection returns.

Plain files

Every document is Markdown on disk. Open it in another editor, commit it to Git, or delete Cadence without an export project.

Review flow

Write here. Review where the code lives.

Cadence does not replace pull requests. It produces clean files for the review system your team already trusts.

01

Draft

Write the decision with the shortcuts you already know.

02

Commit

Save a normal .md file beside the code it describes.

03

Review

Discuss exact lines in a pull request, with a readable diff.

04

Merge

Keep the reasoning versioned with the implementation.

Scope

What Cadence is not.

Not a wiki

No sprawling page tree, permissions maze, or abandoned team homepage. Files and folders remain the structure.

Not a task tracker

No sprints, points, or status fields. Link to the issue that owns the work.

Not chat

No presence dots or typing indicators. Cadence is for durable writing, not another stream to monitor.