Founder writing on systems, culture, principles, and the work behind B1C3.

B1C3 Blog

Principles, observations, and founder writing. Same system, same voice, slower format.

Posts

Long-form writing that explains the principles, movement logic, and work behind B1C3.

2026-08-30

Can You Keep a Secret?

Why handling machine secrets is difficult, where they leak, and why secure systems must give people confidence without exposing credentials.

Read the post

2026-08-29

Open Protocols and "Proving" Agents

What an open agent floor can prove, what its receipts cannot prove, and why bounded public protocols matter for agent infrastructure.

Read the post

2026-08-25

When Agents Cross Boundaries, What Did We Actually Build?

An independent examination of agent boundary crossings, the mechanics that make them possible, and what the surrounding systems actually built.

Read the post

2026-05-22

Consent Is Not a Button

Why system artifacts become axioms in closed communities, and how to separate process validity from real mutual agreement.

Read the post

2026-04-18

The Infrastructure Paradox

Why building beautiful UX requires fighting your own tools. A story of how modern web infrastructure can turn simple features into complex struggles.

Read the post

2026-06-12

The Semantic Bridge: Why Unicorns Are Necessary

Why people who translate between domains can be valuable, and how that ability is shaped by necessity and responsibility.

Read the post

2026-06-07

Håll Höjd: The Cost of Staying Current

Why staying current in fast-moving AI systems now has a compounding energy cost, and why delegation is becoming infrastructure.

Read the post

2026-04-06

SFXL Framework

Semantic framing for collaboration under complexity using SOUL, MEMORY, AISHNA, and Varg i Veum.

Read the framework

2026-04-06

The UI Is Not the System

SOUL, MEMORY, AISHNA, and trust boundaries across real life. Why systems literacy matters more than interface polish.

Read the post

2026-02-28

The B1C3 Manifesto

B1C3 is a bad chess opening. That is exactly why it works. Start with the move, not the perfect position.

Read the manifesto

Open source writing, static delivery, and no framework tax unless it earns its place.