I do not want a learning product to harden around a nice-looking screen before I understand the learning model.
The screen has to serve attention, memory, difficulty, pacing, feedback, and motivation. If the product is for kids, the design question is not only, “does this look good?” It is, “does this help a child learn without adding noise?”
That is the ordering I want to protect. Pedagogy first. Interface second.
sourced Apr 10 2026 · high confidence · argue it, don't flatten it
Field notes are dated working notes. Some also have a small agent-readable record that keeps source, confidence, related notes, boundaries, and reuse limits attached.
Read it as a thought from a specific moment. It is here to invite challenge, connection, and better language.
Use this note when designing education products: research how learning works before deciding what the screen should look like.
Which field note this record belongs to.
target.type, target.id, target.url, target.path When the source happened, when the note was compiled, and when it was last updated.
dates.sourceDate, dates.compiledDate, dates.publishedDate, dates.lastUpdatedDate Where the note came from and how much confidence the source deserves.
source.provenanceLabel, source.sourceType, source.sourceConfidence, source.sourceTrail The current public read of what the note means and what question it opens.
interpretation.summary, interpretation.agentSummary, interpretation.conversationStarter, interpretation.topics Nearby notes, writing, and clusters that help orient the thread.
routes.routeMembership, routes.relatedNotes, routes.relatedWriting How to use the note without making it more certain or more private than it is.
reuse.citeAs, reuse.reuseGuidance, reuse.doNotInfer Private kids learning app UX capture from 2026-04-10, same-day working transcript.
https://jared.is/texture/field-note/2026-04-10-pedagogy-before-interface.json