Capture
Definitions
A frozen copy of a page's markup and whatever stylesheets were reachable, with a URL and a date
The raw material. A capture becomes a Specimen when it is given a role — control or subject — and a Page when the gate types it.
A dev-instance or production read of an estate, taken to establish what reading source cannot
The estate captures: which components exist, which dialogs, which fields can only be enumerated live.
The first of GTD’s five steps: getting everything that has your attention out of your head and into a trusted place — an inbox, a note, a voice memo — as it occurs, before deciding anything about it
Capture costs nothing by design: no sorting, no judging, no filing. That is what makes it habitual, and the habit is what makes the rest of GTD possible — a system that is missing things cannot be trusted, and a head that is holding things cannot be clear. This garden’s notes are captures first; the review gate and the weekly review are where they get clarified.
Used in all four repositories and defined in none of them until now. A capture is what you have; specimen and page are what you call it once you have decided what it is for. The rebuild repository uses only this word for its own output, on purpose.