North Light Path
Sandbox

Things I've built.

Experiments and working tools, built with code and AI. Each one works on the same problem: what pressure does to the way we talk, and how to get from thought to action without the static.

Where this started ↓
00 · The approach

Language Is the Leading Indicator

The Honeycomb Approach, for program managers who want the report to show what's actually moving.

Status reports, milestones and budget show where a program arrived. Words are the cue: the language a program already produces shows what's moving now, at three layers.

  • Individual
  • Team
  • Organization
Read it Open the briefing →
01 · Start here

The 90-Second Scan

Four quick readings of how you're doing right now.

Rate yourself from 0 to 100 on four readings. It gives you a baseline before you try the other tools.

  • Stability
  • Bandwidth
  • Clarity
  • Momentum
Coming soon Under construction →
02 · Writing

Comment Filter

Say the point, keep the respect.

Type the raw comment you're about to post. Get a rewrite that keeps your point and removes the extraction. Not softer. Navigable.

Coming soon Under construction →
03 · Reading

Pattern Decoder

What is this paragraph really saying?

Paste in a mission statement or any corporate paragraph. It reads the source underneath the words, and whether they hold to the mission or drift from it. Then it rewrites. Not nicer. Honest.

  • Wells or Fountains
  • Alignment or drift
  • Honest rewrite
Coming soon Under construction →
04 · Listening

Resonance Recorder

Catch the sound of the moment.

Pressure shows in the voice before it shows in writing: a faster pace, shorter breath, a thinner sound. Record a moment as it happens, note what you heard, and keep it in your archive.

How it's built. The browser's Web Audio and MediaStream Recording APIs capture your microphone directly, and recordings are held in the browser for instant playback.

Try it Open Resonance Recorder →
05 · Looking

The Painting Experiment

What version of this painting would you hang in your house?

Most software assumes decisions are analytical and linear. Under pressure, the important ones never are: they carry a layer of gut feeling. Intuition is fast, subconscious pattern recognition, and it deserves to be honoured, not designed out. This experiment starts with a painting instead of words, and shows how each person meets ambiguity.

Coming soon Under construction →
06 · Defining

The Hourglass Standard

Built on Honeycomb principles

Many sources. One shared core. Every report.

Every organization already holds its data. What it doesn't hold in common is what the words mean. The Hourglass Standard narrows thousands of fields to a small shared core, with one owner and one agreed definition for each. Everything else stays with the department that uses it.

Contested
Two or more owners claim the field
Drift
Same word, different rules
Blank
No owner named
Agreed
One owner, one rule, written down
In development Ask about the standard →
Where this started

Three questions

I once asked a room three questions.

Do you show up to work as your authentic self? Everyone said yes, confidently.

Does your team show up as their authentic selves? The certainty wavered.

Are you vulnerable with your team? Silence.

That room didn't have a broken culture. It had a language gap. Under pressure, people wrap what they really mean in cushioning: softened, padded, over-explained. That cushioning is noise on the signal. Decisions slow down, and messages get longer without saying more.

These tools work on that gap at the three layers the Honeycomb Approach reads:

  • Individual · Signal integrityCatching the self-editing that stops an idea before it's said, so it moves cleanly from thought to action.
  • Team · Collective resonanceTaking the over-polite padding out of how a team talks, so what's left is honest and usable.
  • Organization · Adaptive capacityKeeping things transparent when the organization is under strain, so compliance doesn't quietly drift.