Field notesPlanned
Raw notes from where the work actually happens.
Field notes are meant to be short, timestamped, and unpolished: an installation, a network issue, a prototype behaving oddly, a quick observation from a phone. There is one early customer relationship informing this work today, and no field notes have been published yet.
What a note can contain.
- What happened, roughly when, and in what kind of environment, in the founder's own words.
- A prototype or software behaviour observed outside a controlled test.
- A quick phone recording, a UI test, a failure, or a plain founder thought about what the observation means.
What never gets published.
- The precise location of any site, or details that make it identifiable.
- Network topology or configuration details that create risk if exposed.
- Passwords, tokens, or any credential.
- Private information about an employee or customer, including their name, without permission.
- Anything that would reveal a security camera's blind spots or its credentials.
Consent comes first.
A note involving a real operating partner is written to be published only after the founder judges it will not identify that partner without their agreement. The current early customer relationship has not consented to publication, so it will not appear by name or by identifying detail in any note.
What is not claimed.
No field notes have been published yet. This page describes the format and the rules that will govern them, not an archive that already exists.