Impact report

A report on what someone's information did to your work after it reached you. Drafted from your records, finished by you, sent by you.

The people below are made up to show the shape. The drafter is built: you run it for one person. Nothing is ever sent by it.

The picture

What gets filled in, as a table

One row is one part of the report. A drafted report for Kai Tran, from Robin Park, the owner.

What each field holds

Four layers: contact, activity, impact, then mission and design principles. A header comes first and a next check-in last.

From, To

You, and the person the report is for.

First received

The date of the first exchange from them. "Nothing on record from them yet" when there is none.

What it refers to

The subject of that first exchange.

Report date, number

Today, and which report this is for them: first, then number 2, 3.

Visibility

Who may see it, from their person file. local unless it says otherwise.

What they shared

Every link or file their exchanges carried, with its date.

Projects it relates to

Their relationships, as an id and how they relate.

Questions or needs

What it spoke to. Yours.

Lexicon overlap

Their term next to your term for the same thing. Yours.

Activity

One line per exchange: date, from them or to them, route, subject. --since leaves out older ones.

Did it get integrated?

Integrated, partly integrated, held for later, or not used, and where it lives now. Yours.

Did it change your system?

Filled from anything an exchange carried with kind impact. Otherwise yours.

What came back out

Anything you made from it that they may want, with credit where their idea fed it. Yours.

Mission and principles

Your mission as you state it now, the principles it supported, the ones it challenged, where it moved you. Yours.

Next check-in

A date, and what you will watch for.

The ritual, from the template: set a check-in date when it arrives. On that date, fill out the report. Make a cut holding only what fits their visibility. Send it yourself. Log the send as an activity. Nothing runs on the check-in date by itself: you run the drafter, node _build/impact.mjs per_kai-tran.

What the file looks like inside

The report is Markdown, plain text with light marks. This is the start of Kai's draft, reports/20261009_per_kai-tran_impact-1.md. A page to read is written beside it.

---
type: impact-report
person: per_kai-tran
report: 1
date: 2026-10-09
status: draft
---

# Impact report · Kai Tran · first

Drafted from the records on 2026-10-09. What the records hold is filled in; the rest is yours. Nothing has been sent.

## Contact

- **What they shared:**
  - Tool list (https://example.org/tool-list), 2026-09-14
- **Projects it relates to:**
  - prj_3fa21c9e0b4d (affiliated)
- **Questions or needs it spoke to:** _Yours to fill in._

It is drafted from lines like this one, in JSON, from Kai's exchanges.jsonl. A carried item with kind impact fills "Did it change your system?".

{"id": "exc_8d41b7a0c3", "at": "2026-10-01T16:02:00-05:00", "from": "per_robin-park", "to": ["per_kai-tran"], "route": "email", "subject": "What we did with the tool list", "carried": [{"kind": "impact", "title": "Loan rules rewritten"}], "filed_at": "2026-10-01T16:30:00-05:00", "filed_by": "agent", "how_filed": "From a note the owner gave the agent."}

How it connects