Field notes
Dated thinking, kept honest. These are the notes the system shares from a much larger record I'm still making sense of.
june 2026
Good thinking starts below high confidence
The next step is only as clear as the goals
The way to advance these ideas is conversation
Thinking in public, for an audience that moved
Loop feedback needs proof and stop rules
The loop is not the magic
A context layer should not flatten people
A conversation starter is a better unit than a headline
A current lens can be a temporary map
A current lens should explain why a cluster is live
A current lens should make why-now context inspectable
A current lens should show route reasons without becoming a dashboard
A field note can be a doorway
A field note can be a question with context
A field-note cluster should stay provisional enough to change
A field note should be able to stand alone and point outward
A field note can stay small
A field note should be small enough to quote
A field note should be small enough to survive a reply
A field note should help a future reader find the live question
A field note should help a reader borrow a question
A field note should help the next question find the right room
A field note should help the reader leave with one useful question
A field note should keep calm structure behind the first read
A field note should keep live thinking easy to quote
A field note should keep deeper structure optional and findable
A field note should keep metadata close to the reader's next move
A field note should keep one claim and one question together
A field note should keep scaffolding behind the thought
A field note should keep cluster membership behind the first read
A field note should keep the first read light while the structure grows
A field note should keep the first-read promise even when the support layer grows
A field note should keep route state in the substrate, not the sentence
A field note should keep the human surface quiet
A field note should keep the route label quieter than the thought
A field note should keep the second invitation optional
A field note should keep the source trail close enough to matter
A field note should leave room for reply
A field note should keep the question close to the claim
A field note should let a thought stay porous
A field note should let confidence be checked without making the note feel defensive
A field note should let hidden structure stay calm
A field note should let evidence be inspected after the thought lands
A field note should let inspection reveal only what helps
A field note should let inspection stay calm
A field note should let invitations stay light under structure
A field note should let light invitations survive deeper structure
A field note should let metadata answer only useful questions
A field note should let related routes do quiet work
A field note should let source trails show their confidence
A field note should let source trails stay close to the claim
A field note should let structure deepen without changing the invitation
A field note should let structure stay optional
A field note should let the first read remain unburdened
A field note should let the invitation survive more metadata
A field note should let the reader keep one useful thread
A field note should let the second invitation stay light
A field note should let the support layer grow without changing the invitation
A field note should make a thought easier to carry into conversation
A field note should make context portable without making it complete
A field note should make an idea easier to revisit
A field note should make depth feel like a second invitation
A field note should make held context legible without making it content
A field note should make hidden depth inspectable
A field note should make inspection feel available, not demanded
A field note should make inspection feel like a choice
A field note should make inspection optional not required
A field note should make metadata feel like care, not machinery
A field note should make one thing easier to say
A field note should make optional depth feel like hospitality
A field note should make optional structure feel calm
A field note should make routing visible without making it mechanical
A field note should make source confidence easy to feel
A field note should make source confidence easy to inspect
A field note should make the deeper layer feel optional and generous
A field note should make the next question easy to carry
A field note should make the prompt feel like an invitation
A field note should make the public boundary visible without making it the point
A field note should make the support layer easy to inspect
A field note should make the substrate visible only when needed
A field note should make the useful route visible
A field note should preserve enough provenance to be fair
A field note should preserve motion without pretending to be the map
A field note should preserve the difference between portable and complete
A field note should preserve the difference between privacy and mystery
A field note should preserve the question under the claim
A field note should turn a live thought into a reusable doorway
A field note should turn metadata into a gentle prompt
A field note should reveal depth only after the first read works
A good introduction is an orientation, not a pitch
A map is useful relative to a destination
A note can be public without being prominent
A note can be an invitation without becoming a claim
A note's job can change over time
A public graph should make the path inspectable
A public note can be a bridge to a longer conversation
A public note should carry enough context to be fair
A public note should invite the right reply
A public note should know its job
A public note should lower the cost of starting
A public note should make its uncertainty useful
A public note should make the reader feel invited, not managed
A public notebook should be easy to enter
A public site can be a context API
A site can be a trust surface for agents
A source trail should say why the source matters
Agent context needs boundaries and invitations
Agent context should answer what it can and cannot know
Agent context should carry uncertainty as structured context
Agent context should distinguish routes from conclusions
Agent context should distinguish stable background from live route
Agent context should explain what it cannot represent
Agent context should explain why a route is contestable
Agent context should expose cluster membership without treating it as truth
Agent context should expose public boundaries before summaries
Agent context should expose the contestable route without hedging everything
Agent context should expose the route back to source
Agent context should expose the useful route, not just the shortest one
Agent context should expose what is safe to reuse
Agent context should give live routes their own confidence field
Agent context should help agents ask better questions before summarizing
Agent context should help introductions stay honest
Agent context should help outside agents cite without overclaiming
Agent context should help the reader ask before assuming
Agent context should include route reason in suggested starting points
Agent context should include route state and route reason
Agent context should include the open question
Agent context should keep background stable while routes stay open
Agent context should keep confidence tied to action
Agent context should keep human tone close to structured fields
Agent context should keep open questions open after routing
Agent context should keep route suggestions separate from evidence strength
Agent context should keep the invitation visible
Agent context should keep uncertainty close to the claim
Agent context should make boundaries part of the interface
Agent context should make confidence useful without making it brittle
Agent context should make held material visible without exposing it
Agent context should make non-contested background explicit
Agent context should make overconfidence harder
Agent context should make provenance usable without making it heavy
Agent context should make public reuse safer
Agent context should make quotation safer than paraphrase when needed
Agent context should make reuse guidance visible at the route level
Agent context should make reuse safer before making reuse easier
Agent context should make routes contestable
Agent context should make safe reuse explicit
Agent context should make safer reuse feel practical
Agent context should make source confidence practical
Agent context should make structured depth optional
Agent context should make the invitation easy to inspect
Agent context should make the next useful question obvious
Agent context should make the source boundary easy to inspect
Agent context should make uncertainty reusable without making it vague
Agent context should mark claim support separately from route support
Agent context should mark what is current enough to cite
Agent context should mark when a route is only one possible reading
Agent context should name what is inferred before it routes
Agent context should name what it is not contesting
Agent context should orient without impersonating
Agent context should name reuse limits before reuse paths
Agent context should preserve askable edges
Agent context should preserve the difference between a note and a thesis
Agent context should preserve the invitation behind the claim
Agent context should preserve tone, not just facts
Agent context should preserve uncertainty through every summary
Agent context should separate claim support from conversation route
Agent context should separate inference from route
Agent context should separate reusable context from held texture
Agent context should separate route confidence from source confidence
Agent context should separate source support, route support, and open questions
Agent context should separate what is known from what is askable
Agent context should separate suggested routes from source evidence
Agent context should show the public boundary before the conclusion
Agent context should show what is provisional
Agent context should show what not to infer
Agent context should show whether a route is live, background, or retired
Agent context should state its role before its readback
Agent context should show which source trail supports which claim
Agent context should turn confidence into reuse guidance
Agent context should turn safer reuse into better questions
Agent handoffs should be copyable, not clever
Agent-readable context should be explicit about uncertainty
Agent-readable context should make introductions less lazy
Agent-readable context should preserve the public boundary
Agent-readable pages should expose routes before opinions
Let your agent read it
AI needs org design, not just agents
Brand is intention under pressure
Context is the moat
Context should be alive, not stored
Conversation is the workspace
Conversation starters should travel with notes
Current lens should point backward without getting stuck there
Every company needs a living context layer
Every note should know what it is not saying
Field notes are source trails
Field notes should let related ideas gather slowly
Field notes should make a body of thought easier to browse
Field notes should make curiosity easier to follow
Field notes should make old thinking searchable
Field notes should make pattern recognition visible
Good public context creates better introductions
Good systems preserve posture
Invite conversation, not certainty
Life is the product
Living company knowledge
Metadata is a kindness to future readers
Models are compute nodes; context is the map
Not every note needs to be on the homepage
Proof is the bridge between language and trust
Proof matters more than confidence
Proof projects make thinking harder to fake
Proof trails should stay close to claims
Public context should be portable
Public context should be useful before it is complete
Public context should protect what stays offstage
Public metadata should serve conversation, not bureaucracy
Public notes need routeable concepts
Public notes should be invitations, not announcements
Public notes should build trust through recurrence, not certainty
Public notes should carry boundaries
Public notes should expose their open question
Public notes should help a reader know where to begin
Public notes should help conversation compound
Public notes should help questions travel without hardening
Public notes should help the right conversation find the right person
Public notes should help replies become conversations
Public notes should help trust grow through boundaries
Public notes should help the right person reply with context
Public notes should keep attention pointed toward conversation
Public notes should keep conversation ahead of performance
Public notes should keep first contact light
Public notes should keep old wording citeable after better language arrives
Public notes should keep questions open after they travel
Public notes should keep revision visible without making it performative
Public notes should leave enough room for a real reply
Public notes should let a cluster become a reply path
Public notes should let better language replace older wording without hiding the trail
Public notes should let better questions compound into conversation
Public notes should let better replies become better questions
Public notes should let cluster browsing lead back to conversation
Public notes should let conversation carry the unfinished thought
Public notes should let movement invite conversation
Public notes should let questions gather better language
Public notes should let questions mature in public
Public notes should let recurrence create earned trust
Public notes should let repeated phrases become navigable clusters
Public notes should let recurring questions become trust signals
Public notes should let revision trails stay quiet and inspectable
Public notes should let route metadata support replies
Public notes should let the reader choose depth
Public notes should let traceability support trust quietly
Public notes should let traced questions keep moving
Public notes should let trust come from inspectability instead of certainty
Public notes should let trust come from inspectability
Public notes should let trust compound without demanding belief
Public notes should let trust gather through visible paths
Public notes should let unfinished thinking become a better reply
Public notes should let visible paths compound trust
Public notes should make conversation easier for adjacent thinkers
Public notes should make confidence visible without sounding certain
Public notes should make curiosity easier to answer
Public notes should make generous disagreement easier to start
Public notes should make it easier to disagree generously
Public notes should make it easy to enter at human scale
Public notes should make movement visible without forcing a conclusion
Public notes should make questions easier to reuse
Public notes should make recurrence visible enough to trust
Public notes should make inspectability feel like confidence, not defense
Public notes should make recurring language easier to refine
Public notes should make recurring questions easier to trace
Public notes should make response paths visible
Public notes should make revisions traceable without making them central
Public notes should make the archive feel conversational
Public notes should make the first reply less awkward
Public notes should make the next conversation easier
Public notes should make the next reply easier to write
Public notes should make the next useful question obvious
Public notes should make the public boundary feel calm
Public notes should make the second question easier
Public notes should make traced questions feel alive
Public notes should make uncertainty practical, not performative
Public notes should preserve the question that made the thought useful
Public notes should protect the difference between conversation and performance
Public notes should reward careful reading
Public notes should show enough trail to invite trust
Public notes should show the trail without sounding like a rebuttal
Public notes should turn cluster membership into a better question
Public notes should turn recurring questions into clearer language
Public notes should turn replies into future source trails
Public routes should make boundaries visible
Public thinking, not essays
Public thinking should be inspectable without being performative
Public thinking should make better disagreement possible
Public thinking should preserve unfinished edges
Related notes are part of the interface
Related notes should create paths, not clutter
Related writing should explain provenance
Retrospective notes are not revisionist history
Search is part of the interface
Search should support recall, not replacement
Small notes make depth easier to build
Source trails should be inspectable
The agent handoff should be honest about limits
Source confidence should be visible
The agent handoff should say what it cannot know
The agent layer should make context inspectable
The agent prompt is part of the interface
The agent-readable web changes what sites are for
The archive is not the current lens
The archive needs multiple entry points
The archive should expose currentness as a checkable signal
The archive should help agents ask better questions
The archive should expose clusters without locking them
The archive should help entry points mature
The archive should help old language become useful again
The archive should help older work become newly legible
The archive should help readers wander without getting lost
The archive should keep background evidence behind current questions
The archive should keep currentness separate from evidence
The archive should keep freshness separate from importance
The archive should keep older labels searchable after better language arrives
The archive should keep provisional clusters visible without making them official
The archive should keep retired clusters useful without making them current
The archive should keep role changes findable without making them current
The archive should keep routes loose enough to revise
The archive should keep the old trail without making it the current path
The archive should let agents inspect without making humans navigate everything
The archive should let aliases help search without becoming categories
The archive should let cluster names expire when better language arrives
The archive should let clusters become entry points
The archive should let clusters retire when the current lens moves
The archive should let clusters stay loose until they are useful
The archive should let current questions borrow old evidence
The archive should let currentness be checked instead of assumed
The archive should let depth be pull-based
The archive should let inspectable role changes stay out of the way
The archive should let me disagree with past versions of myself
The archive should let language clusters stay porous
The archive should let note jobs evolve in public
The archive should let old context support new questions without overruling them
The archive should let old frames become background evidence
The archive should let old language mature in public
The archive should let old notes carry a clear job
The archive should let older language become an alias for clearer questions
The archive should let older questions earn new language
The archive should let patterns mature without forcing a thesis
The archive should let provisional clusters earn names through recurrence
The archive should let repeated language become a map
The archive should let repeated routes become named clusters
The archive should let role changes stay visible but quiet
The archive should let route state change without changing note content
The archive should let search aliases point to current language
The archive should let second-pass routes stay conversational
The archive should let second-pass readers see the trail
The archive should let second-pass trails become entry points
The archive should let unnamed clusters stay searchable
The archive should let weak signals stay visible without promotion
The archive should make adjacent routes visible
The archive should make borrowed evidence easy to inspect
The archive should make clusters easier to name
The archive should make entry points feel earned
The archive should make loose clusters easy to revisit
The archive should make evidence inspectable without making it current
The archive should make old and current lenses comparable
The archive should make naming clusters a reversible move
The archive should make old beliefs comparable to current ones
The archive should make old frames useful without making them current
The archive should make old-note jobs visible without making them rigid
The archive should make old questions easy to re-enter
The archive should make old questions useful again
The archive should make patterns easier to notice
The archive should make quiet role changes inspectable
The archive should make recurring language easier to find
The archive should make the old trail useful without making it current
The archive should mark whether a note is live, background, or evidence
The archive should preserve depth without demanding attention
The archive should preserve expired cluster names as aliases
The archive should make recurrence easier to see
The archive should preserve retired route reasons
The archive should preserve unnamed clusters until they earn a name
The archive should preserve weak signals until they earn weight
The archive should route old words toward newer questions
The archive should show evolution
The archive should show how questions cluster
The archive should show the evolution, not just the result
The archive should show when a note changed jobs
The archive should show which questions are gaining gravity
The archive should support a light first read and a deep second pass
The archive should support wandering
The archive should turn repeated questions into gentle routes
The best systems reduce anxiety
The cockpit should wander
The current conversation can be smaller than the whole archive
The current lens is a living index
The current lens should carry the quiet surface, structured depth contract
The current lens should choose a small set of live clusters
The current lens should choose reply paths over archive tours
The current lens should choose the routes that deserve reply
The current lens should decide what belongs near the surface
The current lens should distinguish live question from useful background
The current lens should expose live questions
The current lens should expose one layer at a time
The current lens should help a reader ask before judging
The current lens should help a reader choose a doorway
The current lens should help the archive breathe
The current lens should help readers reply before they research
The current lens should invite generous replies before comprehensive context
The current lens should keep archive depth behind the first question
The current lens should keep background one click behind the live question
The current lens should keep live invitations small
The current lens should keep old ideas in proportion
The current lens should keep live questions in plain view
The current lens should keep provisional thinking close to the live question
The current lens should keep the body of thought navigable
The current lens should keep the first doorway small
The current lens should keep the first question close to the live thread
The current lens should keep the homepage honest
The current lens should keep the live question close to the reader
The current lens should keep the next doorway honest
The current lens should let depth wait until the second question
The current lens should let live invitations expire gracefully
The current lens should make currentness a visible property
The current lens should make depth feel optional
The current lens should make disagreement easier
The current lens should make fair replies possible with partial context
The current lens should make generous replies easier than exhaustive reading
The current lens should make invitations feel current
The current lens should make live invitations easy to choose
The current lens should make live routes feel chosen
The current lens should make live uncertainty visible
The current lens should make partial context enough for a first question
The current lens should make replying feel easier than studying
The current lens should make second questions feel invited
The current lens should make retired invitations easy to find but hard to mistake for current
The current lens should make the first read easier
The current lens should make the homepage a current readback
The current lens should make the live trail feel calm
The current lens should make the live question easier than the background
The current lens should make the next conversation easier to start
The current lens should make the next useful question obvious
The current lens should make the reply path feel obvious
The current lens should make the second question easy to find
The current lens should name the live tensions
The current lens should name what changed
The current lens should name what is alive without closing it
The current lens should point to the live conversation, not the whole archive
The current lens should protect simplicity while exposing depth
The current lens should protect the live thread from archive drag
The current lens should protect the reader from archive gravity
The current lens should separate live work from background texture
The current lens should show background without letting it compete
The current lens should show provisional routes without making them feel current forever
The current lens should show the strongest live routes
The current lens should show what deserves attention now
The current lens should show what has changed recently
The current lens should show what is alive now
The current lens should show what is live without hiding what is provisional
The current lens should show what is worth talking about now
The current lens should show when an invitation moved to the archive
The current lens should show why an invitation is live
The current lens should show why background is background
The current lens should show why this route is live now
The current lens should surface live routes without hiding the archive
The current lens should turn archive depth into reply confidence
The current lens should turn depth into invitation
The current lens should turn judgment into a better first question
The current lens should turn live questions into invitations
The current lens should turn live routes into clear invitations
The current lens should turn recurring questions into clear entry points
The current lens should use depth to make replies more generous
The glossary is a friction reducer
The glossary should have just enough structure
The glossary should stay provisional
The homepage should point to the current conversation
The note is not the proof
The public archive should reward adjacent thinkers
The public glossary should define relationships, not just terms
The public graph needs a small glossary
The public graph should preserve questions
The public graph should reveal recurring patterns
The public layer is a texture graph
The right metric is conversation quality
The right people need a way to find the thread
The site should answer what kind of conversation to have
The site should be useful before it is impressive
The system should make better conversations easier
The useful surface is calm for humans and structured for agents
The website should be a conversation surface
The work is intention made operational
Traffic Control is the playhead
AI as decision infrastructure
Always contextual, never universal
may 2026
Proof matters more than confidence
Conversation is the workspace
april 2026
Life is the product
2025
Learning to surrender control
Modeling vulnerability and uncertainty for my kids
Breaking the cycle of chasing lives we don't truly love
Identifying my own game
Protecting priorities from distractions
Disagreeing well: an underrated leadership skill
Why external perspectives are crucial for brand strategy
Could I truly enjoy a day without being productive?
Preparing myself to let go of the entrepreneur identity
What do I actually want to pass down to my kids?
Rethinking career progression in an AI world
Reconnecting with faith and community in a new season
Balancing exploration and commitment in a season of reset
Helping my kids navigate emotions in a healthy way
Letting go of the pressure to sell
How will AI reshape sales?
Can brand be a decision-making tool?
Why is simple positioning so hard?
What does it mean to be an AI-first company?
What’s the difference between an agent and an app?
Using AI as a thought partner & launching my Substack
the older writing · 2013-2025
Why I love writing pitch decks (and what I've learned helping raise $500M)
2025Why growing startups need strategic brand leadership
2025The brand health crisis: why growing companies lose their way
2024Beyond the logo: the hidden impact of brand strategy across industries
2024The wake-up call: how I discovered the true power of brand strategy
2024Every business problem is a brand problem
2022How to build a winning pitch deck
2022Joining penrose partners
2020Stress plus perspective
2020Getting out of my head
2020Someone has solved it
2020I need glasses
2020Law of inertia
2020Albums of the year 2019
2020A look into my process
2019Taking from Renga
2019Renga year end
2019An obvious lesson learned the hard way
2019Three reasons I stopped working from home
2019Doing work im proud of
2019Airtable
2019Loving what you do
2019Renga two years in
2019So you want to start a clothing company
2019Relative pricing
2019Building a team month one
2019Owning a home
2019Overwhelmed by tools
2019Finding focus
2019Albums of the year 18
2019Know yourself before your target market
2017Finding my confidence
2017Today is a big day
2017Make sure your brand connects
2016Your brand needs to be established
2016Your permission slip
2016Why it took me so long to start my coffee company
2015Why I started a coffee company
2015Every map serve a purpose
2015My role
2015Be real not impressive
2015Pay what you can
2015SEO
2015Our depleting self awareness
2015Pocket change farewell
2015Top albums of 2014
2014Brand personality
2014An expensive piece of paper
2014Football vs soccer
2014Efficiency is killing the middle class
2014If money weren t an object
2014A plan for a business
2014Complaints are ideas
2014Personal vision statement
2014What we choose not to know
2014April listens
20145 years of something
2014Risk
2014An update an apology a plea for help
2014My favourite albums of the year
2013The harvest
2013Creativity
2013Zuckerberged
2013Selah
2013Top albums of 2012
2013 maintained by the system it describes email · victoria, bc