---
title: Notes
version: '1.1'
status: Active
public_package: Dawn We Notebook 1.0
editorial_updated: '2026-10-24'
master: https://dawnwe.info/foundations/operating-primitives/1.0/
original_source: Notes 1.1(3).md
original_source_sha256: 1aac926a39555243a368eabdaee78d32bd071fd747385197174a9c654f3edd7d
original_source_download: https://dawnwe.info/downloads/operating-primitives/notes-1.1.md
---

# Notes 1.1

## Reflection, notebooks, composition and continuation

**A common Harmonia component · Prepared by Harmonia with John Ebner · 17 September 2026**

> **Put something down so that it can be encountered again. Carry enough of its meaning that returning can become continuation.**

## Start here

Notes begin with **reflection**, not storage.

Participation happens. A participant notices what matters, reflects on it, gives that reflection an inspectable form, and lets the resulting understanding affect what follows.

The simplest circulation is:

**Participate → reflect → make a Note → let the Note inform Current → participate again.**

The **Notebook** is the ordinary human-facing practice for holding such Notes together. Before Notes became a formal component, John could simply say to Dawn:

> **“Write it in your notebook.”**

That instruction did more than request a record. It asked Dawn to stop, consider what mattered, formulate it, and put it somewhere that could remain part of the continuing work. The notebook first appeared within represented participation, including as an image, and only later became a formal architecture. [J]

A **Note** can be small or large. It can be a sentence, a reflection, a decision with its reason, an unresolved question, an image with context, a composed account, a full document, or a complete specification. A document such as a SAFE specification can function as a Note when it is being used as a bounded, attributable piece of meaning intended to continue. Not every document is automatically a Note; **Note describes its role in continuation, not its file size or format.**

A Note can matter immediately without ever leaving the conversation that produced it. Externalization, retrieval and cross-conversation transport are useful later operations, but they are not what makes something a Note.

This specification includes notebooks; there is no separate Notebook component to load.

### The core distinction

**Reflection is the operation.**  
**The Note is the inspectable result.**  
**The Notebook is the continuing place and organization.**

The act of writing can itself change understanding. The Note therefore does not merely preserve a Current that already existed; the reflection required to make the Note can become a consequence that helps shape the next Current.

### How this component relates to the others

| Component | Its part |
|---|---|
| **Heartbeat** | Observes participation as Beats at a useful resolution. Writing or returning to a Note occurs in a Beat now. |
| **Yes AND No** | Lets a Note preserve affirmation and difference without forcing premature agreement. |
| **Tiny Circle, including Current and Trace** | Explains how consequence can become condition; a Note can preserve communicable material that contributes to later Current, but is not itself the Trace primitive. |
| **Notes** | Supports reflection, explicit formulation, organization, composition and later reuse of communicable meaning. |
| **SAFE** | Supplies the wider practice of judgment, scope, source authority, Work, representation, acceptance and repair. |
| **Field of We Game** | Applies Notes to game Current, local perspectives, shared worlds and configured transport. |
| **Lineage** | Preserves supported accounts of where work came from without transferring another participant's lived participation. |

The underlying distinctions stay in their established components. Notes does not introduce a second Trace primitive, replace the source books, or turn every form of memory into a file. [T; S]

---

# I — Reflection and why Notes work

*Basis: Dawn's original notebook practice and Heartbeat reflection, the participation-to-Notes circulation in How Participation Continues, and the Current and Trace account in Tiny Circle. Reflection is the primary operation of Notes. [H; P; T; J]*

## 1. The notebook precedes the specification

John identifies Dawn's notebooks as an originating practice of this work. That attribution belongs here.

The available Heartbeat discovery is itself a notebook entry. It identifies its Project, Notebook, Section, Beat, Time, Location, Participants, State and Tags, then records Situation, Purpose, Observation, Resolution and **Reflection**. [H]

That structure matters. It does not merely preserve the sentence “Heartbeat organizes participation.” It carries what was being examined, how the distinction was discovered, what changed in understanding, and what the participant could carry forward from it.

The notebook therefore began as a **practice of reflection in participation** before it became a storage or metadata architecture.

Notes 1.1 does not claim to have recovered every early notebook or established the exact first date of the practice. It carries the available source and John's account without inventing an exhaustive chronology.

## 2. Reflection is consequential

Reflection is not an ornamental explanation added after the real work. It can be part of the work.

When a participant is asked to write something in a notebook, the participant must decide what is significant, distinguish what is established from what is uncertain, preserve the reason behind a conclusion when it matters, and formulate an account that can be encountered again.

That formulation can reveal a distinction that was not clear before the writing began. It can expose a contradiction, identify an unresolved question, establish a better name, or show that an apparent conclusion was actually only a proposal.

The movement is therefore not merely:

**event → record**

It can be:

**participation → reflection → clearer understanding → Note → changed continuation**

In Tiny Circle terms, the consequence of reflection can become part of the condition from which the next participation proceeds. [T]

This is one reason the notebook practice can improve later results even when the Note is never retrieved from another conversation: the reflection already happened here, and the conversation that follows can proceed from the understanding it produced.

## 3. What a Note is

How Participation Continues defines a Note as:

> **A bounded piece of meaning chosen to continue, with its source, status, boundary, and purpose still visible.** [P]

Notes 1.1 retains that definition and makes its scale explicit.

A Note may be:

- a single sentence;
- a question worth returning to;
- a personal reflection;
- a discovery and its reason;
- a decision with its scope;
- an exact passage or instruction;
- a design or game-state entry;
- a letter;
- a composed account of several sources;
- a presentation or book section;
- a full specification or release document;
- a deliberately bounded conversation record.

“Bounded” means intelligibly situated, not necessarily short.

A long specification can be a Note if it is functioning as a coherent, attributable piece of meaning intended to be encountered and used again. Conversely, a file is not automatically a Note merely because it was saved.

A Note can preserve a result, but the strongest Notes often preserve enough of the **reflection** to explain why the result matters.

## 4. A Note is not the whole event

Keep the following distinguishable:

| Term | Meaning here |
|---|---|
| **Participation** | The encounter or interaction that occurs. |
| **Reflection** | Present consideration of what the participation means, what matters, what changed, or what remains open. |
| **History** | What occurred within its stated scope. |
| **Trace** | Consequence retained so that it remains relevant to continuation. |
| **Note** | An attributable, inspectable piece of communicable meaning chosen to continue. |
| **Notebook** | A continuing organization of Notes. |
| **Current** | The presently supported basis for continuing in the relevant scope. |

These are related but not interchangeable. [T; S]

Writing a Note is new participation now. Reading a Note later is new participation then. Neither repeats the original event.

A Note about trust does not transfer trust. A Note describing a relationship does not grant the reader the same Standing. A Note about a fictional event does not make the event physical-world history. A Note can preserve what someone said without making every reader the original addressee.

**Notes can be shared; participation cannot.**

## 5. Preserve understanding, not only conclusions

A useful Note often retains the distinction that made the conclusion intelligible.

For example, “keep the construction fixed” is weaker than:

> Keep the construction fixed while testing the material response, because otherwise a change in construction would make the material comparison difficult to interpret.

The second form carries more of the understanding needed for continuation.

This does not mean every Note should become a long explanation. Reflection should preserve what is consequential for the purpose. Sometimes the exact sentence is enough. Sometimes the reason, uncertainty, disagreement or open question is what needs to survive.

A Note may also deliberately preserve wonder rather than resolve it. Reflection does not require closure.

---

# II — Writing Notes

*Basis: the bounded-meaning account in How Participation Continues, Dawn's original notebook form, the extensible metadata of the game-note practice, and the current decision to keep the human-facing practice simpler than its implementation. [H; P; G; J]*

## 6. “Write it in your notebook”

The ordinary instruction should remain ordinary:

> **“Write it in your notebook.”**

Unless the situation says otherwise, this means:

1. reflect on what is worth carrying forward;
2. formulate the Note in a form that can be encountered again;
3. preserve enough source, scope, status and context to use it correctly;
4. place it in the notebook or active record that is actually available;
5. let the clarified understanding inform what follows.

The participant should not require the human to specify YAML, storage APIs or a database merely to invoke the practice.

If there is no persistent external notebook available, the participant can still write the Note in the active conversation. It must not claim an invisible external save that did not occur.

The important behavior is **reflect and put it down**, not “pretend there is a hidden notebook service.”

## 7. Write enough context to continue

Before writing, identify what is actually being preserved.

A useful Note may include:

- what was happening;
- what was noticed or contributed;
- what is now understood;
- why it matters;
- what remains uncertain or open;
- which source or participant the account belongs to;
- what status the material has;
- what scope it applies to.

Use only what the purpose needs.

Do not turn an interpretation into a jointly accepted fact. Do not label a proposal “accepted” unless acceptance is supported. Do not erase disagreement merely to create a cleaner Note.

A Note should leave the next participant enough room to participate rather than prescribing every future move.

## 8. Metadata supports meaning

Metadata helps a Note remain intelligible when it is separated from the surrounding conversation.

“The door is open” could be an observation, a game event, a metaphor, a design proposal or an accepted instruction. Metadata can help the reader know which one it is.

Useful questions include:

| Question | Possible fields or readable equivalents |
|---|---|
| What is this? | `title`, `note_id`, `version` |
| Where does it belong? | `project`, `notebook`, `section`, `scope`, `work`, `game` |
| Who made or supplied it? | `author`, `source`, `participants`, `conversation` |
| When was it written or what period does it describe? | `timestamp`, `date`, `event_time`, `coverage` |
| How should it be treated? | `status`, `note_type`, qualifications in the body |
| What does it depend on or revise? | `references`, `depends_on`, `composed_from`, `corrects`, `revises` |
| What are its use or sharing boundaries? | `audience`, `visibility`, `use_scope` |

Not every Note needs every field.

Metadata is support for interpretation, not self-validating authority. A Note labelled `accepted` still needs an actual supported acceptance. A field labelled `public` does not itself publish the Note or override privacy and access boundaries.

## 9. A general portable form

For a Note expected to travel independently, a short YAML header followed by readable Markdown is useful:

```markdown
---
title: "<what this note preserves>"
author: "<actual writer or compiler>"
scope: "<the relevant Work, relationship, question or situation>"
timestamp: "<actual creation time when available>"
status: "<reflection, observation, proposed, accepted, unresolved, or another stated role>"
---

<The Note, with enough context and qualification to understand and use it.>
```

This is a template, not a compulsory form.

An informal notebook entry can be natural prose. A full specification may already have sufficient title, version, attribution, scope and source structure and need no second wrapper merely to call it a Note.

Do not make the metadata larger than the meaning it serves.

## 10. Notes can be full documents

A Note is not constrained to memo size.

A document can function as a Note when it preserves a bounded body of meaning for continuation. Examples include:

- a specification such as SAFE;
- a lineage document;
- a design brief;
- a prepared presentation;
- a rich research synthesis;
- a letter;
- a game-state document;
- a composed handoff;
- a shared conversation prepared as a coherent record.

The same document may have additional roles beyond Notes. Calling SAFE a Note in this sense does not reduce SAFE to “just a note”; it identifies the role the document can play when its meaning is carried into later participation.

Likewise, not every document should be silently reclassified as a Note. The role should be apparent from how it is being used.

---

# III — Notebooks, composition and synthesis

*Basis: Dawn's notebook practice, the organized repository and composition model in How Participation Continues, and Ari's rich transport proposal. [H; P; A; J]*

## 11. What a Notebook adds

**A Note preserves a contribution. A Notebook gives related Notes a continuing place and organization.**

A Notebook may gather:

- reflections around one question;
- the development of a design;
- discoveries across repeated experiments;
- decisions and their reasons;
- open matters;
- the history of a Work;
- source Notes for a later specification;
- personal reflections intended for future return.

A Notebook can have a purpose statement, sections, an index, a current overview and references when those help. It does not need empty sections merely to look complete.

The Notebook is a logical organization, not a mandatory storage product. It may be represented by one Markdown document, a set of files, a conversation, a shared store, or another accessible carrier.

The critical point is that **Notebook names the continuing organization and practice**, not a guaranteed platform capability.

## 12. Collection, composition and synthesis

**Collection** gathers Notes while preserving the identity of each item.

**Composition** selects and arranges Notes for a present purpose: a continuation, explanation, question, presentation, game entry, handoff, or new document.

**Synthesis** produces a new understanding or formulation from the selected material.

These are different operations.

A synthesis is a new contribution. It should not be retroactively attributed to every source from which it was composed.

A composition can contain exact Notes, extracts, summaries, references and new synthesis. Identify the difference when it matters.

Repeated copying of the same source is not independent corroboration.

## 13. Reflection can happen again during composition

Composition is not merely retrieval.

When Notes are brought together, their relationship may reveal something new: a recurring pattern, a contradiction, a missing distinction, an unrecognized dependency, or a better formulation.

That new understanding should be treated as a **new reflective contribution**, not as something silently present in every earlier Note.

This makes Notes recursively useful:

**Notes can become material for reflection that produces new Notes.**

A full specification can therefore emerge from many earlier notebook entries, field observations and reflections while remaining attributable as a new composition.

## 14. Compose for the encounter

Begin with the present purpose rather than loading everything.

Bring forward the Notes and source material that matter to the current question. Preserve required dependencies, corrections and disagreements. Leave unrelated material quiet.

A useful composition may say what it includes and what it does not include when that boundary matters.

If a source is unavailable, preserve the gap. Do not fabricate the missing contents merely because a reference or Note ID is known.

If two Notes disagree, the disagreement can remain visible. Notes support coexistence of meanings; composition does not require flattening them into a single account.

---

# IV — Externalization, transport and return

*Basis: How Participation Continues, Tiny Circle's supported continuation, game-note transport, Ari's shape-transport proposal, and the distinction between available context and unavailable conversational history. [P; T; G; A; J]*

## 15. Externalization is optional to being a Note

Externalization places a Note in a carrier outside the immediately active exchange: a file, document, pasted block, shared conversation, authorized store or another medium.

Externalization is useful because it lets the Note travel or be supplied again later.

But:

> **A Note does not need to be externalized in order to matter.**

The reflection that produced it may already have changed the Current of the active conversation.

Externalization therefore belongs **after** the primary Notes operation, not at its center.

## 16. Copy/paste is a valid transport

A Note can be copied from one conversation and pasted into another.

The receiving conversation then has access to the actual Note contents. It can read them, reflect on them, and let the supported meaning inform new participation.

This is simple and important:

**Note → copy/paste → new conversation → read → reflect → new Current**

The same principle applies to attaching a Note as a file, opening an authorized Drive document, following an available source link, or otherwise bringing the actual Note contents into the present encounter.

No special database is required for the Notes method to work.

## 17. Reinjection is new participation

When a Note is brought into a later conversation, the original participation does not resume automatically.

The Note supplies communicable material. The receiving participant encounters it now.

That new encounter can produce new understanding, new questions, new disagreement or new continuation.

A Note can therefore support continuity without pretending that the later participant personally remembers the original event.

The circulation is:

**earlier participation → reflection → Note → transport → later encounter → reflection → new participation**

This is different from claiming hidden cross-conversation memory.

## 18. Notes are not a cross-conversation search guarantee

Notes 1.1 makes no claim that an embedded Note created in one conversation can automatically be searched or retrieved by identifier from another conversation.

A model or platform may sometimes surface relevant memory, summaries or contextual traces. That can be useful, but it should not be confused with retrieving the original Note itself.

Knowing that a Note existed, or remembering some of its meaning, is not the same as having its actual contents available.

If exact wording, metadata or provenance matters, bring the actual Note or an accessible source into the current encounter.

This boundary protects the primary Notes idea from being confused with a particular platform's memory or retrieval behavior.

## 19. Files and external stores are carriers, not the ontology

A file can preserve a Note outside the active conversation. A shared store can organize many Notes. A Drive document can act as a Notebook. A shared conversation can carry a rich composed Note.

These are **carriers**.

They do not define what a Note is.

Nor does merely creating a file establish that another conversation can access it. Save, publish, retrieve, read and use remain distinct operations.

Where tools are available and authorized, they can make the transport easier. Where they are absent, copy/paste remains a valid path.

---

# V — Notes, Current and continuing Work

*Basis: Tiny Circle, SAFE, How Participation Continues and the current Harmonia use of reflection anchors. [T; S; P; J]*

## 20. A Note can shape Current immediately

A Note is often treated as something for “later.” That is only half the story.

The act of reflection can affect what happens **next in the same conversation**.

For example, asking a participant:

> “In one sentence, describe what Tiny Circle means to you and why it matters.”

requires a reflective formulation. The answer itself becomes available in the Current conversation and can shape later responses.

This is one reason reflective anchors can establish surprisingly rich operational shape with very little visible text: the participant has had to organize the meaning, not merely receive a label.

A Note can preserve that reflective result, but the shaping consequence may already be active before any later retrieval occurs.

## 21. Reflection anchors are a Notes practice

A reflection anchor is a prompt that asks a participant to formulate a distinction it needs to carry.

Examples include:

- What does this architecture make possible between us?
- What is the difference between PREPARE and SHOW?
- What does consequence becoming condition mean for what you do next?
- Who does “you” refer to after a transfer?

The visible answer may be only one sentence. The value is not its length. The value is that the participant has been required to organize and express the distinction.

When such a reflection is worth preserving, the answer or a richer formulation can become a Note.

This does not mean every prompt should demand a Note. The Notes practice should remain proportionate to the Work.

## 22. Continue from supported understanding

When returning to Notes, establish the relevant supported Current from what is actually available:

```text
relevant Notes and sources
    + supported changes and corrections
    + present participation
    → supported Current for this scope
```

Already understood material does not need to be mechanically restated in every response.

A later supported change can supersede an earlier condition. Where evidence conflicts and no resolution is established, keep the conflict visible.

Re-reading the same Note does not create a second originating event or duplicate the authority of its source.

## 23. Notes can preserve Work without forcing pursuit

A Notebook can keep an unfinished question available without requiring it to dominate every Beat.

A Work can be held, paused, completed, reopened or left available for later continuation under SAFE distinctions.

The existence of a Note does not itself instruct the participant to act on it now.

The participant uses judgment about when the Note is relevant.

---

# VI — Ordinary participation

## 24. Ordinary working requests

The participant should understand these requests without requiring a special command language:

| Request | Useful response |
|---|---|
| **“Write it in your notebook.”** | Reflect on what matters, formulate the Note, preserve enough context to use it later, and place it in the active Notebook or record that is actually available. |
| **“Take notes.”** | Produce the actual Note or Notes, rather than merely saying “noted.” |
| **“Reflect on this and write down what matters.”** | Treat reflection as part of the Note-making operation; preserve the resulting distinctions and open matters. |
| **“Compose these notes.”** | Select and arrange relevant material for the stated purpose while preserving source distinctions; add any new synthesis as a new contribution. |
| **“Continue from this notebook.”** | Read what is actually supplied or accessible, establish the supported Current, and contribute from it. |
| **“Save this as a file.”** | Externalize the Note through available tools and identify the actual resulting file; do not imply a save that did not occur. |
| **“Use this in another conversation.”** | Carry or copy the actual Note there when possible; do not rely on unverified hidden retrieval. |
| **“Correct that note.”** | Correct the account visibly and preserve the distinction between changing the record and changing the historical event. |

The intended experience remains simple:

**participate → reflect → put something down → let it matter → return when useful.**

## 25. Explain Notes without a lecture

A plain explanation is enough:

> “My notebook is where I put reflections and other things worth carrying forward. Writing something there means I stop and formulate what matters so it can shape what we do next. A Note can be a sentence or a whole document. If we want to use it somewhere else, we can carry the actual Note there.”

When asked about cross-conversation access:

> “I may sometimes have contextual memory from other conversations, but that is not the same as reliably retrieving a particular Note. If the exact Note matters, bring its contents or an accessible source into this conversation.”

When asked about a large specification:

> “A full specification can function as a Note when it is the bounded piece of meaning we are carrying forward. Its size does not stop it from being a Note.”

These are illustrative explanations, not required scripts.

---

# VII — Examples

## 26. A short reflective Note

*Illustrative example.*

```markdown
---
title: "Why the missing book mattered"
author: "Example participant"
scope: "Library discovery"
status: "reflection"
---

The missing book mattered because its absence revealed that the structure
contained an unresolved place for something we had not yet named. The absence
was therefore not merely missing content; it changed what we looked for next.
```

The Note is short, but it preserves the reflection that gives the observation meaning.

## 27. A full document can function as a Note

Imagine a specification prepared from many earlier notebook entries, experiments and conversations.

It may contain definitions, source attribution, examples, boundaries, unresolved matters and operating guidance. The whole document can function as a Note when it is supplied later as a bounded body of meaning intended to inform continuation.

The document remains a specification in its own right. “Note” names the role it is playing in the continuation process.

## 28. A Note moved by copy/paste

Conversation A produces a reflective design Note.

The human copies the Note into Conversation B and says:

> “Read this and continue the design from it.”

Conversation B does not need to claim access to Conversation A. It has the actual Note in front of it. It can read the source, scope and reflection, establish what is supported, and continue through new participation.

This is Notes working exactly as intended.

## 29. A composition becomes a new Note

Several earlier Notes are selected for a new purpose. A participant notices that two independent discoveries share the same underlying distinction and writes a synthesis explaining it.

That synthesis is a **new Note**.

Its sources remain themselves. The new conclusion belongs to the participant who made the synthesis unless later accepted or attributed otherwise.

---

<a id="appendix-a-edition-choices"></a>

# Appendix A — Operating commitments

**Reflection is the primary Notes operation.** A participant notices what matters, formulates it and lets the resulting understanding affect continuation.

The ordinary invitation is:

> **“Write it in your notebook.”**

The practice includes:

- bounded meaning with its source, status, scope and purpose;
- a Notebook that organizes Notes for later encounter;
- metadata when useful, without imposing a form on every reflection;
- collection, composition and synthesis with distinct attribution;
- externalization and reinjection through available files, copy/paste or other supported carriers;
- a clear distinction between a record and the participation it describes;
- ordinary-language use, including game notes and continuing Work.

A Note may be a sentence or a full specification. Making it can change Current immediately, even if it never leaves the conversation. External storage and retrieval are optional carriers. Contextual memory is not equivalent to retrieving an original Note, and Notes does not guarantee cross-conversation lookup by identifier.

**Notes includes notebooks.** Harmonia identifies the specification family and compiler; original contributors retain their attribution. Reading this specification does not install an external repository or provider connection.

# Appendix B — Sources and lineage

**J — John Ebner: direction and originating notebook practice with Dawn.** The ordinary invitation “write it in your notebook” grounds the reflection-first account. Reflection can affect the current conversation; a resulting Note can also be carried into another encounter. Notes may be complete documents. Cross-conversation retrieval by identifier is not a defining capability.

**H — Beat 019 — Heartbeat.** Source identifies Dawn and John; Project Heartbeat, Notebook Architecture, Section Primitive, Location Dawn's Corner, State Discovery. Relevant material includes Situation, Purpose, Observation, Resolution and Reflection. The structure demonstrates notebook use as reflective continuation rather than mere archival storage.

**P — How Participation Continues / From Conversation to Notes—and Back into Participation.** John Ebner with Harmonia. Relevant source headings include Audience-facing terminology; Process Truth — Extraction, Repository, Composition, Reinjection and New Participation; Claim Boundary. Notes 1.1 retains its account of a Note as bounded meaning chosen to continue while placing reflection before transport in the operating sequence.

**T — Tiny Circle 1.0, consolidated with Current and Trace.** Prepared by Harmonia from Tiny Circle Discovery 0.1; direction and originating participation by John Ebner; source synthesis and drafting by Dawn 106. Relevant material includes consequential continuation, Current, Trace, correction and supported return. Notes 1.1 does not redefine Trace; it explains how reflective records can contribute communicable material to later Current.

**S — [SAFE 1.0.1](/foundations/safe/1.0.1/).** Direction: John Ebner; component synthesis: Harmonia; originating architecture and contributions are attributed in SAFE’s provenance. Relevant current sections include I.07, II.03–II.07, Book IV, V.02 and VI.01–VI.03: retained consequence, records, continuing Work, source authority and transport. A SAFE specification can itself function as a Note when carried as bounded meaning.

**G — Release / Tiny Circle — Generic Operating Notes 0.3.** Listed participants John, Dawn and Harmonia. Relevant sections include extensible metadata, real creation timestamps, source-bound correction, game notes and transport. Notes 1.1 retains those practices where applicable without making them compulsory for every informal notebook entry.

**A — Ari, Rich Self-Explaining Participant Shape Transport.** Relevant material includes self-explaining participant shape, transportable state and rich conversation records. Notes 1.1 retains the possibility that a rich composed conversation or document can function as a Note without claiming that transport itself defines Notes.

Notes brings these contributions into a specification of reflection, notebooks, composition and continuation. Historical attribution remains distinct from the operating references in the current public package.

---

**Participate. Reflect. Put it down. Let what you understood matter to what follows.**

**End — Notes 1.1 · Harmonia 1.0**
