Ravi Dabbiroo

Builder's Journal

By Ravi Dabbiroo

05-sep-2026

Documentation preserves evidence. Reflection preserves the experience of becoming.

I have built many things in my life. Businesses, coaching frameworks, expeditions and, more recently, software. I am thrilled to bits about this phase of my life.

I remember many of the outcomes, but I have forgotten an extraordinary amount of what it took to arrive at them.

The small discoveries. The wrong assumptions. The quirks. The changes of mind. The moments when something suddenly made sense.

Most of that has disappeared.

I documented plenty along the way, but I am beginning to understand that documentation is not the same as memory.

While building Oceans7, the code name for my stealth project, Ravi Wiki has become the place where the evidence survives. Experiments, decisions, failures, technical details and the reasoning behind them can live there.

But preserving the work is not necessarily the same as preserving the experience of building it.

That thought arrived around the same time I bought a ridiculously small 3.7-inch E-Ink reader.

I chose it precisely because it does very little.

My laptop is where I build. My monitor is where I investigate. My phone is where the world finds me.

I wanted one small place where I could simply read and think without distractions.

That led to another experiment.

Every day, we already know what happened while building Oceans7. But at the end of every week, we can ask something more valuable:

Instead of allowing those answers to disappear into another folder, I can turn each weekly reflection into a chapter of an EPUB:

Oceans7: Builder's Journal, 2026

Week after week, the book grows while the product grows.

Ravi Wiki keeps the evidence.

The EPUB carries the story and, perhaps more importantly, the meaning.

I wish I had done this earlier.

I would love to read what I was thinking before an expedition when I did not yet know how it would end. I would love to revisit an old business decision before hindsight made everything look inevitable.

Those books cannot be recreated now because I already know their endings.

This time, I am writing from inside the uncertainty.

The discipline required is almost trivial.

Stop once a week. Notice what changed. Write it down. Add one chapter. Read it.

But small disciplines repeated for years have a peculiar ability to become large assets.

Fifty-two weekly reflections become a year of thinking.

Ten years become something much more difficult to name.

Perhaps that is the real experiment.

We spend so much time asking how to preserve our files.

How much effort do we make to preserve the person we were becoming while we created them?

A simple Wiki → EPUB system

The system does not need to be complicated.

The simplest version is one place to preserve the work, one weekly reflection habit, and one EPUB that keeps growing.

1. Keep the evidence in the wiki

Use Ravi Wiki for the detailed record:

The wiki should remain detailed enough that you can trace backwards and understand what actually happened.

2. Write one weekly synthesis

At the end of each week, do not copy everything that happened.

Instead, answer a few questions:

The synthesis should capture the movement in your thinking, not reproduce the week's logs.

3. Build one EPUB for the year

Each weekly synthesis becomes one chapter in:

Oceans7: Builder's Journal, 2026

At the end of the next week, add another chapter and regenerate the EPUB.

The book grows alongside the project.

4. Read it

This is the part that matters.

Move the EPUB onto an e-reader and actually return to it.

Read away from the screen where the work happened.

Occasionally add a monthly or quarterly reflection when larger patterns begin to appear.

5. Keep the roles separate

The wiki and the EPUB should not become the same thing.

The wiki preserves evidence.

The EPUB preserves the evolving story.

Do not put every log, screenshot, technical artifact or experiment into the book.

That would turn the book back into documentation.

The point is reflection.

The loop

DAILY WORK
    │
    ▼
RAVI WIKI
Notes
Experiments
Decisions
Evidence
    │
    │ End of week
    ▼
WEEKLY SYNTHESIS
What happened?
What did I learn?
What changed?
What happens next?
    │
    ▼
YEARLY EPUB
Week 01
Week 02
Week 03
...
Week 52
    │
    ▼
E-READER
Read
Reflect
    │
    ▼
BETTER JUDGMENT
    │
    └──────→ NEXT WEEK

The technology is almost incidental.

A folder of Markdown files, a wiki, an EPUB tool and an e-reader are enough.

The real system is the discipline of turning experience into reflection before memory smooths away the uncertainty.

Related ideas

#continuity