Begin with one question
Write the question the note is meant to answer. Name the audience and the decision or task the note should support. A narrow question makes it easier to see what belongs in the document.
The downloadable file is a blank authoring template, not a completed research report. It is ordinary Markdown: readable as plain text, editable in a text editor, and usable without an account.
State the finding—and its status
Give the reader your current answer before the supporting detail. Say whether it is a direct observation, an interpretation, or an open question. Do not turn an attractive layout into a claim that the conclusion is verified.
Keep the wording proportional to the material you have reviewed. When the answer is not yet established, name the missing information rather than filling the gap with certainty.
Keep the original material within reach
Assign a stable identifier to each source, such as S-001. Record its title, author or organization, date, location, and the page or section you used. Distinguish a source you read in full from an excerpt or a summary.
Put the source identifier beside the statement it supports. Keep quotations separate from paraphrases and your own interpretation. A source ledger is useful only when a reader can trace the connection.
Give the limitations their own space
Describe what the sources do not establish. Note conflicting accounts, incomplete records, date limits, and assumptions that could change the conclusion. Put a qualification next to the affected finding, not only in an appendix.
Finish with a concrete next step: inspect the original, seek a missing record, test an alternative explanation, or leave the question open.
Sources & implementation notes 1
Public project references. Earlier design notes describe the original direction; implementation contracts describe this edition.
- Covenant design doctrineEarlier project design notes · Markdown file