Documents
The specification and everything around it¶
The normative text is one document. The others exist so that the normative text does not have to argue for itself, apologise for itself, or keep a diary.
| Document | Description | Version |
|---|---|---|
| Common Time Core | The normative specification. Authoritative version. | 1.2a |
| Common Time Core | Finnish version. The working version; English takes precedence. | 1.2a |
| Rationale | Four refusals, eight measured decisions, eighteen rejected alternatives. | 1 |
| Implementation plan | Six phases, five of them measurements. One gate each. | 1e |
| Conformance plan | The test suite as an audit of the specification. Every test cites a clause. | 1d |
| Roles and open items | Who holds the pen on what, and the twelve items awaiting a decision. | 2b |
| Prior art | Around fifty-five comparable systems, and what each one does instead. | — |
| How it came about | Non-technical, spoken. Eight chapters and four refusals. | — |
| The mark | Thirteen rings, 92 vertices, phase-locked to a common anchor. | — |
Application layer — not the protocol¶
Common Time exists because something needed it. These documents describe that something, and they are not part of the specification — a conforming implementation owes them nothing.
| Document | Description | Version |
|---|---|---|
| Musikklubben | The virtual nightclub the protocol was written for. | MVP |
| Material pipeline | How generated audio becomes material the protocol can address. | 1a |
| Operator console | An illustration of a four-deck controller. Not a specification of anything. | — |