PEACEBINFLOW for SAGEWORKS AI

Posted on Oct 9

The Neural Handshake: A Student Paper and Project Base

#ai #productivity #programming #opensource

The Neural Handshake: A Student Paper and Project Base

SAGEWORKS AI | PeacebinfLow | Maun, Botswana | October 2026 | Educational Edition

Educational Edition, derived from the Hacktoberfest Open-Source AI Challenge Week 1 (Touch Grass) papers by the same author.

Status legend. Every statement in this paper has one of four labels.

Label Meaning

BUILT It exists today. In this paper, only the published EcoSynapse whitepaper is BUILT [1].

SPECIFIED It is designed but has not been run.

ILLUSTRATIVE The values are examples that show a format. They are not findings and not field data.

TEACHING MATERIAL Added for this edition: lessons, stages, labs, templates, questions. It has not been tested with students.

This paper is a project description and a learning resource. It is not peer-reviewed research and it reports no findings. Nothing in it says what any piece of land needs.

Label	Meaning
BUILT	It exists today. In this paper, only the published EcoSynapse whitepaper is BUILT [1].
SPECIFIED	It is designed but has not been run.
ILLUSTRATIVE	The values are examples that show a format. They are not findings and not field data.
TEACHING MATERIAL	Added for this edition: lessons, stages, labs, templates, questions. It has not been tested with students.

At a glance

Audience: senior secondary and first-year university students with an interest in computing, biology, geography or environmental science. Teachers and mentors are a second audience.
Prerequisites: basic computer use. No knowledge of Git, databases, AI or multi-agent systems is needed. Every technical term is defined before it is used.
Time: six weeks at about two to three hours a week (TEACHING MATERIAL).
Setting: Maun and the Okavango region of Botswana. Every lab has a paper-and-pencil path, so a reliable internet connection is not required.

Learning outcomes. By the end, a student should be able to:

Explain the difference between a pipeline and a handshake, with an example of each.
Describe the roles of an offline ledger system and an online agent platform, and why having both is useful.
Read and write a signed packet with a parent reference, and trace a chain of packets back to its start.
Define ripple, agent, organ, residual and hop, and apply the observation criteria to a short transcript.
Describe the seven layers and place a given tool or agent at the correct layer.
Distinguish a claim about records from a claim about the world, and explain why the paper makes only the first kind.
Design a control run to test whether an effect was caused by the exchange, and say what result would count against the idea.
Explain what open-weight models, plain-text ledgers and Git history make possible that a closed service does not, and state honestly what remains unknown, such as cost.

Abstract

Two computer systems can think in very different ways. This paper follows a project in which two such systems keep a conversation going. One is Library Ground, also called Aerie: an offline system that asks "what is actually written, and where?" The other is EcoSynapse: an online platform in which every plant is an agent, and which asks "what did this organism do, what did that cause, and in what order?" The thing they talk about is barren land near Maun, Botswana. A third path, Arian, handles questions that neither side can place. The paper teaches the ideas behind this design from scratch: ledgers, packets, parent references, layers, and six effects of the exchange. It also teaches how to test whether an effect really came from the exchange, and how to read a technical claim critically. It ends with a six-stage project that a class or club can build, with or without internet. The design is SPECIFIED, the examples are ILLUSTRATIVE, and no ecological claim is made.

Keywords: handshake, ledger, packet, multi-agent systems, emergence, offline-first, open-weight models, experimental design, Botswana

1. Why this project is worth studying

This project is worth studying because it asks how two different ways of thinking can keep a conversation going, and how to read the record of that conversation honestly.

1.1 Two systems that think differently

Think of two people looking at the same patch of ground. One keeps a notebook. She writes down exactly what she saw, on which line, and when. The other watches what happens over time. He remembers what changed first and what that led to. If they talk, each will ask questions the other would not think to ask.

Aerie is the notebook-keeper. EcoSynapse is the watcher of events. The project is about what happens when they are left to keep talking.

Think first. Imagine the notebook-keeper and the watcher talk for a week. What might each start to do differently? Write down one guess before reading on. Section 7 returns to it.

1.2 Why a hard, nearly empty subject

The subject is barren land because it gives the systems very little to say, and that forces them to be careful. Bare, pale, cracked ground in the dry season has few things to record. It has edges, a dry channel, a few seedlings, and a date since the last rain. A rich subject could hide mistakes in a flood of detail. A sparse subject makes each claim easy to check.

1.3 What the paper does and does not claim

The paper claims things about records, and not about the land. A claim about records says, for example, "this packet came after that one" or "this line was written on this date." A claim about the world says, for example, "this ground needs water" or "these seedlings will survive." The project makes only the first kind. The land is the thing the two systems talk about, and the paper studies the talking.

Common misconceptions.

"This project is trying to fix barren land." It is not. It makes no recommendation about land.

"A hard subject means an important result." No results are reported here. The design is SPECIFIED and the examples are ILLUSTRATIVE.

Check your understanding (Section 1).
1.1 In your own words, what does Aerie ask, and what does EcoSynapse ask?
1.2 Give one claim about records and one claim about the world, using bare ground as the subject.
1.3 Why does a sparse subject make claims easier to check?
1.4 The paper is a "learning resource". Name two things it is not.

2. Core ideas from scratch

Seven ideas carry the whole project, and each can be understood with a small example.

2.1 Ledger

A ledger is a record in which new entries are added and old entries are not changed. A school's rain-gauge notebook is a ledger if the rule is that you never rub out an entry, only add a new line. Aerie is ledger-native: it is built around such records. Its rule for growth is that anything may expand, but the expansion goes into a separate ledger, so the original stays as it was.

A ledger entry can be pinned down by line and column, like a cell in a table. That lets someone point at the exact words behind an answer. Here is a sealed record of one entry (ILLUSTRATIVE):

{
  "card_id": "PC-001",
  "sealed_by": "meridian",
  "subject": "barren-land-maun",
  "lines": [
    {"line": 12, "cols": "1-58", "tense": "is",
     "text": "bare pale cracked surface, no grass cover"}
  ],
  "expansion_ref": null,
  "ledger": "system",
  "status": "ILLUSTRATIVE"
}

Notice tense. Aerie marks each statement as was, is or will be, so that old and new statements are never mixed up.

2.2 Packet

A packet is one turn in a conversation, written as a small structured message. In EcoSynapse, every action is a packet written to a log before it happens [1]. A packet says who sent it, when, what kind of action it is, what it carries, and which packet it answers.

2.3 Signature

A signature is a mark that shows who wrote a packet and that it has not been altered. In the project's real design, each packet is signed. In every example in this paper the signature is a placeholder, because the examples are ILLUSTRATIVE.

2.4 Parent reference

A parent reference is a field in a packet that names the packet it answers. If packet C names B as its parent, and B names A, then you can walk backward from C to A. The whole conversation is a chain that can be read back.

Think first. If every packet names its parent, what could you do with the chain that you could not do with a plain list of messages? Guess, then read on.

A chain lets you ask why a packet exists. A plain list only tells you when. Here is a small packet (ILLUSTRATIVE):

{
  "packet_id": "P-002",
  "agent_id": "eco.handler",
  "action_type": "candidates.list",
  "payload": {"question": "how many seedlings, and how far from the channel?"},
  "parent_packet_id": "P-001",
  "signature": "ILLUSTRATIVE-PLACEHOLDER",
  "status": "ILLUSTRATIVE"
}

2.5 Branch and commit

Git is a tool that keeps the history of a set of files. A commit is one saved step in that history. A branch is a separate line of commits. In this project, one branch holds one conversation thread, and one commit is one turn. Because Git keeps the history, nobody can quietly change the order of turns.

2.6 Offline-first

A system is offline-first when it works fully without a connection and shares only when a connection is available. In Maun, a connection may come and go. An offline-first system keeps working anyway, and its next push happens whenever it is next online.

2.7 Open-weight model

An open-weight model is an AI language model whose trained numbers (its weights) are published, so that anyone can run it on their own computer within the licence terms. In this project, Gemma is the example [2]. A closed service, by contrast, can only be reached over a connection and run on the owner's machines.

Common misconceptions.

"A signature in the examples proves who wrote them." In this paper every signature is a placeholder.

"A ledger can never be added to." It can. What it cannot do is lose or rewrite old entries.

Check your understanding (Section 2).
2.1 What is the difference between changing a ledger entry and expanding a ledger?
2.2 What does a parent reference let you do that a time stamp alone does not?
2.3 In this project, what does one branch hold, and what does one commit hold?
2.4 Why does offline-first matter for a school in Maun?
2.5 Name one thing an open-weight model can do that a closed hosted service cannot.

3. The two parties and Arian

Aerie and EcoSynapse are built to think differently, and Arian exists for what neither can answer. This section condenses Part 1 of the original papers.

3.1 Library Ground / Aerie (offline)

Aerie runs offline from a command prompt. It is described as a Windows 10 native build with a Rust reference workspace alongside it. Whether it is built today is to be confirmed by the author, so this paper treats its structure as SPECIFIED.

Four eagles carry separate jobs:

Eagle	Job
Herald	The only eagle that speaks to the user. When something is unclear, it asks by naming the unclear term.
Meridian	Audit. Answers by pointing to the exact entries behind an answer.
Cairn	Sourcing and filing. Builds a ledger of what matters, in order.
Forge	The builder. Proposes new things, and is questioned by the other three.

3.2 EcoSynapse (online)

EcoSynapse treats a botanical environment as a network of agents [1]. Every plant is an agent with an identity, a state (water intake, light absorption, stress index, growth stage, interaction log) and a way to talk to its neighbours. Agents never call each other directly. A protocol handler passes every message and writes it to the log first. Its reference ecosystem is the Okavango, and its reference species are Acacia senegal, Combretum imberbe and Terminalia sericea. Which species and settings apply to Maun is to be confirmed by the author.

3.3 Two ways of thinking

	Aerie	EcoSynapse
Question	What is actually written, and where?	What did this organism do, what did that cause, and in what order?
Unit of record	A line and column in a ledger	A signed packet in an event log
Relation to time	Tense on every statement	Order from parent references
Posture	Grounded, questioning, audit-first	Behavioural, causal, event-driven
Runs	Offline, on a laptop	Online

3.4 Arian

Arian is a third path and not a ruler. It holds the rules about what each side may ask and which prompt forms are valid. When a question falls outside both parties, neither guesses. The question goes to Arian, which writes a state card (a small record with a topic thread, a focus, a running count and a line to carry forward) and routes it onward. A pattern that fits nowhere is not thrown away. It goes into a residual ledger, marked "unplaced", and is offered again when new data arrives. Arian's full list of authorities is to be confirmed by the author.

flowchart LR
  subgraph OFF["Offline: Aerie"]
    HER["Eagles"]
    AL[("Aerie ledger")]
  end
  subgraph ON["Online: EcoSynapse"]
    PH["Protocol handler"]
    EL[("Event log")]
  end
  subgraph AUTH["Authority: Arian"]
    ARI["Arian"]
    RES[("Residual ledger")]
  end
  GH{{"Epicentre 1: GitHub channel"}}
  TD{{"Epicentre 2: Tiger Data record"}}
  AL --> GH
  GH --> PH
  PH --> EL
  EL --> GH
  GH --> AL
  GH --> ARI
  ARI --> RES
  GH --> TD
  ARI --> TD

Figure 1. The three paths and the two epicentres (the channel and the record). SPECIFIED.

Common misconceptions.

"Online is better than offline." Neither is better. The project is useful because the two differ.

"Arian is in charge." Arian registers and routes. It does not steer the exchange.

Check your understanding (Section 3).
3.1 Which eagle is the only one that speaks to the user?
3.2 Why do EcoSynapse agents never call each other directly?
3.3 What happens to a pattern that fits nowhere?
3.4 Fill in the blank: Aerie reads what is ___, and EcoSynapse reads what ___.

4. The handshake

A handshake is a continuous two-way exchange in which neither side owns the result, and this is different from a pipeline. In a pipeline, system A makes something and hands it to system B, and the work moves one way. In a handshake, each side speaks from its own record and listens from its own record, and the conversation never has to be declared finished.

Think first. A school sends its rainfall figures to a weather office, and the office sends back a forecast. Is that a pipeline or a handshake? What would have to change to make it the other one?

4.1 Principles

Literal and continuous. The exchange is ongoing, not one request and one answer.
Asymmetric in timing. The offline side pushes whenever it is next online. The online side answers when the push arrives. Neither waits.
Causal by construction. Every packet names its parent, so the conversation is a chain.
Two ledgers, one conversation. Each side keeps its own ledger. The differences between them are what make the talk productive.
Never declared finished.

4.2 The channel and the four ledger tiers

The channel is a Git repository. A branch is a thread, a commit is a turn, a pull request is a formal question, and a merge is a moment of agreement. Four tiers of ledger make every statement traceable:

System ledger: Aerie's own ledger.
Connected-system ledger: EcoSynapse's event log.
Step ledgers: one short ledger per turn, chained.
Combined ledger: a merge of the first three, from which any sentence can be traced to its source line.

4.3 Ripple, agent, organ, residual, hop

Three things are observed and not designed. This is the key idea, so read the definitions slowly.

A ripple is a change in one side's ledger that is caused by the other side's packet, and that in turn causes a further packet.
A hop is one step of a ripple. The papers count how far each ripple travels in hops. Section 5 shows a counting convention.
An agent (in the emergent sense) is a conversation thread that has become something with its own name and subject. A thread is counted as an agent when it (a) recurs in at least two consecutive rounds, (b) holds a single subject, (c) has been given a ledger name by one of the systems and not by the author, and (d) repeats at least one question form. This is an observation criterion. It is not a trigger. Nothing creates the agent. The criterion only decides when the observer writes it down.
An organ is a recurring function that agents begin to share and that becomes a topic of its own. A function is counted as an organ when at least two separate threads each call on it and a ledger entry names it as a topic.
A residual is a pattern that fits nowhere and is kept as "unplaced" for later.

One more idea. Aerie has a rule that a heavy topic may spin up its own agent, but the trigger is deliberately left undefined. This was done so that the author can watch when and how the system chooses to do it.

sequenceDiagram
  participant A as Aerie (offline)
  participant R as Repository path
  participant E as EcoSynapse (online)
  participant X as Arian
  A->>R: Round 1, branch thread/barren-maun-001, commit 1 (P-001)
  R->>E: push received
  E->>R: Round 1 reply, commit 2 (P-002)
  R->>A: pulled on next online
  A->>R: Round 1 reply, commit 3 (P-003)
  E->>R: Round 2, commit 4 (P-004)
  A->>R: Round 2, commit 5 (P-005)
  E->>R: Round 2, commit 6 (P-006)
  A->>R: Round 3, commit 7 (P-007)
  E->>R: Round 3 decline, commit 8 (P-008)
  R->>X: out of scope
  X->>R: Round 3 state card, commit 9 (P-009)

Figure 2. The handshake over three rounds. ILLUSTRATIVE.

flowchart LR
  L12["Aerie ledger L-0012"] --> P1["P-001"]
  P1 -->|"hop 1"| E1["EcoSynapse record: candidates"]
  E1 --> P2["P-002"]
  P2 -->|"hop 2"| A1["Aerie ledger: seedling edge filed"]
  A1 --> P5["P-005 expansion"]
  P5 -->|"hop 3"| E2["EcoSynapse record: thread named"]
  E2 --> P8["P-008 decline"]
  P8 -->|"hop 4"| AR["Arian state card S-001"]
  AR --> A2["Aerie ledger: new topic"]

Figure 3. A ripple, condensed across the rounds, with hops marked. ILLUSTRATIVE.

Common misconceptions.

"A handshake is a pipeline with two steps." A pipeline hands a result along and stops. A handshake keeps going, and each side's record changes the other's questions.

"Emergence is magic." Here it is a word for a pattern that the records show and that nobody wrote in advance. The criteria above say exactly when to write it down.

Check your understanding (Section 4).
4.1 Is a one-time upload of data to a website a pipeline or a handshake? Why?
4.2 What is the difference between a branch and a commit in this project?
4.3 Name the four ledger tiers.
4.4 A thread appears in only one round. Can it be counted as an agent? Which criterion decides this?
4.5 Why is the agent criterion described as an observation criterion and not a trigger?

5. A worked example, traced by hand

Tracing a transcript by hand teaches the three skills at the heart of the project: following parent references, counting hops, and applying the criteria. The transcript below is the one from Part 1, Rounds 1 to 3. It is ILLUSTRATIVE. It was composed to show the format.

5.1 The transcript (ILLUSTRATIVE)

ROUND 1
P-001  Aerie (Herald)       parent: none
  Subject set: barren land, Maun area. Lines 12-16 sealed.
  Seen: pale cracked surface; no grass; few acacia seedlings at one edge;
  dry channel one side. Last rain: was, long ago.
P-002  EcoSynapse (handler) parent: P-001
  Candidates listed. Asks: how many seedlings, how far from the channel?
P-003  Aerie (Cairn)        parent: P-002
  Count and distance not written. Files 'seedling edge' as a sub-topic.

ROUND 2
P-004  EcoSynapse           parent: P-003
  What happened first, and what followed? I need order, not only state.
P-005  Aerie (Meridian)     parent: P-004
  Only line 14 is written. Forge proposes an expansion entry:
  a 'seedling edge' thread.
P-006  EcoSynapse           parent: P-005
  Accepting. Naming the thread 'seedling-edge'.
  Recurring question: what changed since the last entry?

ROUND 3
P-007  Aerie (Herald)       parent: P-006
  A second thread 'dry-channel' asks about surface condition.
P-008  EcoSynapse           parent: P-007
  My records hold plant state, not surface state. Routing to Arian.
P-009  Arian                parent: P-008
  State card S-001. Pattern kept as residual U-001.

5.2 Step 1: follow the parent references

Start at P-009 and walk backward: P-009 → P-008 → P-007 → P-006 → P-005 → P-004 → P-003 → P-002 → P-001. P-001 has no parent, so it is the start. The whole transcript is one unbroken chain. This is what parent references make possible.

5.3 Step 2: count the hops

A counting note (TEACHING MATERIAL). Part 1 says a hop is a ledger change on one side caused by a packet from the other. To match the papers' illustrative counts of 2, 3 and 4, this edition uses a simple convention: count each ledger entry that is made because of the chain, after the packet that starts it. The papers state the idea briefly, so this convention is a teaching choice. The author should confirm it. The lesson is that a paper must state its counting rule, because two readers could count differently.

Round	Entries made because of the chain	Hops
1	(1) EcoSynapse's record gets a candidate list, caused by P-001. (2) Aerie's ledger files 'seedling edge', caused by P-002.	2
2	(1) Aerie's ledger records that only line 14 is written, caused by P-004. (2) Aerie's Expansion Ledger gets Forge's proposal, caused by P-004. (3) EcoSynapse's record names the thread, caused by P-005.	3
3	(1) EcoSynapse's record logs the decline, caused by P-007. (2) Arian writes state card S-001. (3) Arian writes residual U-001. (4) Aerie's ledger gains a topic.	4

5.4 Step 3: apply the criteria

Thread 'seedling-edge'.

Criterion	Evidence	Met?
(a) Recurs in at least two consecutive rounds	Filed as a sub-topic in Round 1 (P-003); named in Round 2 (P-006)	Yes
(b) Single subject	Acacia seedlings at one edge	Yes
(c) Named by a system, not by the author	Named by EcoSynapse in P-006	Yes
(d) Repeats a question form	P-006 names the recurring question as "what changed since the last entry?", which echoes P-004's request for order	Yes in the papers; see the note below

The papers count 'seedling-edge' as the first agent. A careful reader will notice that criterion (d) rests on a question that is named once and echoes an earlier one. Many readers would want to see the same form of question asked twice. That is a fair point and it shows how a criterion can need a sharper wording. The author should confirm whether to tighten criterion (d).

Thread 'dry-channel'. It appears only in Round 3. Criterion (a) needs two consecutive rounds. So it is a candidate, and it is not counted. This "no" is as important as a "yes". Part 2 later shows it recurring and being counted.

Organ 'surface-condition reading'. Two separate threads, 'seedling-edge' and 'dry-channel', each need something that reads surface condition, and a ledger entry names it as a topic. Both parts of the organ criterion are met, so it is counted as the first organ.

5.5 What the example does not show

Nothing here shows that the land is any particular way. The example shows that a chain can be followed, that hops can be counted by a stated rule, and that criteria can be applied and can say no.

Common misconceptions.

"Illustrative means it happened." It means the values were made up to show a format.

"If a criterion is met, the agent was designed." No. The agent was observed. The criterion only decided when to write it down.

Check your understanding (Section 5).
5.1 Walk backward from P-006 to P-001. List the packets.
5.2 Using the counting convention, how many hops does Round 3 have? List each entry.
5.3 Why is 'dry-channel' only a candidate?
5.4 Which two threads support the organ, and why do two matter?
5.5 Why does the paper state a counting rule at all?

6. The seven layers and the two spines

The system is built as seven layers from the ground up, with two spines that run through every layer. A layer is a level of the system that does one kind of job and sits on the one below it. This section condenses Part 2 of the original papers, and the layering follows an idea from robotics [3].

Think first. A student walks out to the ground and speaks a note into a phone. Which layer of a system would that note belong to? Which layer would show it to a visitor on a screen? Guess, then read on.

6.1 The seven layers

Layer	What lives here	Tool named in the design
L1 Ground	The walk, spoken notes, plain-text lines. Optionally one physical sensor.	ElevenLabs (speech-to-text); Arduino UNO Q only if available
L2 Ledger	Aerie's ledgers, EcoSynapse's event log, the channel	GitHub
L3 Language	Herald's local language layer; the online narrator	Gemma
L4 Agents	The eagles; the plant agents	Mastra orders the online agents
L5 Authority and routing	Arian, state cards, residual ledger, routed prompts	Backboard
L6 Memory and forecast	The record, the registry, forecasts	Tiger Data, MongoDB Atlas, TabPFN
L7 Window	A read-only view of the live conversation; narration	Render, ElevenLabs

The two spines run through all layers. Temporal makes each turn durable, so that an interrupted turn resumes and does not duplicate. Sentry traces what each agent did, so an effect can be traced to its source. All of these tools are SPECIFIED. A tool being listed here is not the same as a tool having been used, and whether each was used in a real run is to be confirmed by the author.

flowchart TB
  subgraph L7["L7 Window"]
    W1["Read-only listening window"]
  end
  subgraph L6["L6 Memory and forecast"]
    M1["Record, registry, forecast"]
  end
  subgraph L5["L5 Authority and routing"]
    A1["Arian and routed prompts"]
  end
  subgraph L4["L4 Agents"]
    G1["Aerie eagles"]
    G2["EcoSynapse plant agents"]
  end
  subgraph L3["L3 Language"]
    N1["Herald language layer"]
    N2["Online narrator"]
  end
  subgraph L2["L2 Ledger"]
    D1["Aerie ledgers"]
    D2["EcoSynapse event log"]
  end
  subgraph L1["L1 Ground"]
    F1["Walk and spoken notes"]
  end
  F1 --> D1
  D1 --> D2
  D1 --> N1
  D2 --> N2
  N1 --> G1
  N2 --> G2
  G1 --> A1
  G2 --> A1
  A1 --> M1
  M1 --> W1
  subgraph SP["Two spines"]
    T1["Durability"]
    S1["Tracing"]
  end
  T1 -.-> D1
  S1 -.-> G1
  S1 -.-> A1

Figure 4. The seven layers and the two spines. SPECIFIED.

6.2 The layered packet

Part 2 adds two fields to the packet. layer says where in the stack the packet was produced. lane says which path produced it: offline, online or arian. With these, the combined ledger can answer a new question: not only which packet caused which, but at which layer each cause acted.

{
  "packet_id": "P-014",
  "agent_id": "aerie.herald",
  "lane": "offline",
  "layer": "L3",
  "action_type": "question.open",
  "payload": {"thread": "seedling-edge", "term_unclear": "crumbles"},
  "parent_packet_id": "P-013",
  "status": "ILLUSTRATIVE"
}

6.3 One thread through seven layers

A thread is not a thing at one layer. It is a path through several, and following it shows how the agents are connected. Here is the 'seedling-edge' thread (ILLUSTRATIVE).

Layer	What the thread looks like there
L1 Ground	A spoken note: "seedlings at the east edge, surface near the channel crumbles"
L2 Ledger	Two new lines in Aerie's ledger, plus a commit on the thread branch
L3 Language	Herald asks what 'crumbles' means, naming the unclear term
L4 Agents	Meridian points to the lines; the plant agents at that edge receive the packet
L5 Authority	A state card carries the thread name and a carry-forward line
L6 Memory	A row per packet; one registry document
L7 Window	A tile in the listening window showing the thread's latest turns

flowchart LR
  T1["L1 spoken note"] --> T2["L2 ledger lines and commit"]
  T2 --> T3["L3 Herald asks about crumbles"]
  T3 --> T4["L4 Meridian points, plant agents receive"]
  T4 --> T5["L5 state card"]
  T5 --> T6["L6 rows and registry"]
  T6 --> T7["L7 window tile"]
  T7 -.->|"new walk"| T1

Figure 5. One thread as a path through the seven layers. ILLUSTRATIVE.

Common misconceptions.

"A tool being listed is the tool being used." The papers list tools with a function each. Nothing says they were run together.

"Higher layers are more important." Layers are levels of a stack. Each does its own job, and the ground at L1 is where the subject lives.

Check your understanding (Section 6).
6.1 Which layer holds a spoken field note? Which holds the read-only window?
6.2 What do the fields layer and lane add to a packet?
6.3 What does Temporal do, and what does Sentry do?
6.4 Why is the 'seedling-edge' thread described as a path and not a thing at one layer?
6.5 Why does the dotted arrow in Figure 5 loop back to L1?

7. Effects and how to test them

An effect is an observable change in the records that would not be there if the two systems had not exchanged packets, and a good experiment is how you check. None of the six effects is a claim about the land.

Think first. Back in Section 1 you guessed what the notebook-keeper and the watcher might start doing differently. Compare your guess with the effect called cross-adoption, below.

7.1 The six effects

Effect	Definition
E1 Cross-adoption	A side begins to use a question or packet form that came from the other side.
E2 Vocabulary overlap	Terms in both ledgers divided by terms in either.
E3 Ripple reach	The number of hops each ripple travels.
E4 Emergence count	How many agents, candidate agents and organs have been counted.
E5 Residual re-offer rate	Of the patterns marked unplaced, the share later placed when new data arrived.
E6 Reconstructability	The share of statements in the paper that can be traced to a source line through the combined ledger.

Cross-adoption is the effect the project most wants to see. Aerie asks for line and column. EcoSynapse asks for order. If the exchange does more than swap data, each should start to carry a trace of the other. In Part 2's illustrative Round 4, EcoSynapse cites line numbers, which is Aerie's habit. In Round 5, Aerie offers an order, which is EcoSynapse's habit. This is shown in Figure 6. It is ILLUSTRATIVE. If it did not happen in a real run, that would be a result too, and a paper should say so.

flowchart LR
  AH["Aerie habit: cite line and column"] -->|"Round 4"| EC["EcoSynapse starts citing lines"]
  EH["EcoSynapse habit: ask for order"] -->|"Round 5"| AO["Aerie starts offering order"]
  EC --> SH["Shared practice: state, order and source line together"]
  AO --> SH

Figure 6. Cross-adoption. ILLUSTRATIVE.

7.2 Why a control run is needed

To say the exchange caused an effect, you must compare it with a run in which the exchange did not happen. This is the core of experimental thinking. Suppose a plant grows taller after you water it. Was it the water, or would it have grown anyway? You can only tell by comparing with a plant that was not watered and was otherwise treated the same.

The project's design (SPECIFIED, never run) uses two runs:

Run H (handshake): both ledgers exchange packets as in Section 5.
Run I (isolated): both systems ingest the same field lines for the same number of rounds, but never read each other's packets.

At the same round count, compare E1, E2 and E4. If Run H shows cross-adoption and rising overlap, and Run I does not, the exchange is a candidate cause. If the two runs look alike, the effects are not due to the exchange.

7.3 What would count against the idea

A good experiment names its own failure. Here, the idea is weakened if Run I shows the same cross-adoption as Run H. It is weakened if overlap rises equally in both. It is also weakened if effects appear in Run H only because of the order in which lines were entered, which is why both runs must use the same lines. With one site and a handful of rounds, even a clear difference would be a single case and would not generalise.

Here is how a round's effects could be stored (ILLUSTRATIVE):

{
  "round": 5,
  "e1_cross_adoption": 2,
  "e2_overlap": "computed from both ledgers",
  "e3_ripple_hops": [4],
  "e4": {"agents": 2, "candidates": 0, "organs": 1},
  "e6_traceable": "computed from combined ledger",
  "status": "ILLUSTRATIVE"
}

The papers deliberately leave E2 and E6 as words, because they must be calculated from real ledgers and a number made up in advance would be a false finding.

Common misconceptions.

"If B happened after A, A caused B." Order is not cause. That is why the control run exists.

"A control run proves the idea." It can only make the idea more or less believable, and one case does not generalise.

Check your understanding (Section 7).
7.1 Define cross-adoption and give one example from the text.
7.2 Why are Run H and Run I given the same field lines?
7.3 State one result that would count against the idea.
7.4 Why is E2 given as words and not as numbers in the papers?
7.5 Why would a clear difference between the runs still not prove the idea in general?

8. Reading a technical claim critically

The project's own status labels are a lesson in how to read any technical claim, because each label tells you how far to trust a statement.

8.1 Three questions to ask

What kind of statement is this? Is it something that exists (BUILT), something designed but not run (SPECIFIED), or an example of a format (ILLUSTRATIVE)?
What would show it wrong? If nothing could, it is a weak claim.
Is it about records or about the world? A claim about the world needs evidence from the world, such as a measurement. A claim about records can be checked in the records.

8.2 The legend, applied

Statement	Label	Why
"EcoSynapse is published as a whitepaper."	BUILT	It exists, and can be read [1].
"Aerie spins up an agent when a topic gets heavy."	SPECIFIED	It is designed, and its trigger is deliberately undefined.
"Round 3 ripple travelled 4 hops."	ILLUSTRATIVE	The number was composed to show a format.
"The Section 9 stages form a six-week plan."	TEACHING MATERIAL	Added for this edition, not tested with students.

8.3 Common ways a claim goes wrong

A listed tool is treated as a used tool. Naming Temporal in a design does not mean a Temporal run exists.
An example is treated as a result. A table of made-up numbers is not a measurement.
A story about records is treated as a story about the world. "The two ledgers agreed" does not mean "the land is a certain way."
A missing detail is quietly filled in. The papers write "to be confirmed by the author" instead, and a good reader looks for that phrase.

8.4 A practice set

Classify each statement as a claim about records or a claim about the world, and say which status label would suit it.

"Packet P-004 names P-003 as its parent."
"The seedlings at the edge are healthy."
"A thread appeared in two consecutive rounds."
"This ground is too dry for acacia."
"The retry was recorded in the trace and not in the ledger."
"Run H will show more cross-adoption than Run I."

Common misconceptions.

"Honest means pessimistic." Honest means saying exactly what a statement is, no more and no less.

"A SPECIFIED design is a weak design." It is a design not yet tested. Calling it SPECIFIED is accurate, not unkind.

Check your understanding (Section 8).
8.1 What are the three questions to ask of a technical claim?
8.2 Which label fits "a Temporal workflow made the handshake durable in a real run"? What would you need to see to change it?
8.3 Give an example of an example treated as a result.
8.4 Why does the paper write "to be confirmed by the author" instead of guessing?
8.5 Complete the practice set in 8.4.

This part of the Educational Edition ends after Section 8. Still to come: Sections 9 to 14 (project base, labs, assessment, safety and ethics, open innovation, limits), Appendices A to D, the About note, the references and the open items.