Clear Box · System design

We build systems people can
understand, use, and change.

Bring us what you’re trying to make possible. We’ll learn from your people and data alike, uncover what’s missing, and build the tools to help you move forward, like a better website or an application shaped around how you operate.

What Clear Box does

Build from what your organization already knows.

The people closest to the work often know where it stalls, what has already been tried, and what falls through the cracks. We begin there.

Learn from the work

Your team brings experience that a report can’t always capture. We listen, look at the records and tools alongside you, and pinpoint which questions need a better answer.

Build a way to learn

Sometimes the information you need has never been gathered. We identify what to capture and build a practical way to collect it as the work happens, keeping the context that turns information into knowledge.

Put the learning to work

That could mean an inquiry tool, a loyalty program, a reporting system, or a custom application. We build solutions around your people and constraints, then refine them through your team’s use and feedback.

In practice · a neighborhood website

The site led with the homes. Residents moved for the intentional community.

A new, sustainably built neighborhood’s website had grown over time, with pages written by different hands. We looked at what the site said, what its search data showed, and what the developers and residents told us, then rebuilt it around what we learned.

What the developers told us
  • Many inquiries came from people searching for something else altogether.
  • Few inquiries turned into a serious conversation about buying.
How people found the site
  • Nearly every search visit came from someone who already knew the neighborhood’s name. New people rarely found it.
  • Sustainability searches drew attention but few clicks.
What attracted residents
  • A chance to get to know their neighbors.
  • Children playing outside, surrounded by adults they trust.
  • A come-as-you-are community: join in often, or keep your own pace.
What visitors saw first
  • Language that drew interest in how the neighborhood was built, not in living there.
  • Most visitors left the site before scrolling far enough to reach the content about community life.
What came into focus

People are looking for connection and community, with a private space of their own to call home.

What we changed

The site now leads with private homes and shared spaces, uses the words people search for, and trades stock and AI images for residents’ own photos, credited to the people who took them.

What comes next

We pay attention to which search terms are gaining or losing interest, which pages and sections hold visitors’ attention, what new neighbors say drew them to the community, and adjust accordingly.

Analytics count visits without identifying anyone, and visitors can opt out. Residents choose what they share and receive credit for their photos.

Open projects

Built for our work, released for yours.

These tools grow out of our own work and collaborations. We release them freely so others can use, adapt, and build on them. They also give you a closer look at how we build and the experience we can bring to your project.

commonllama

Reusable context makes local AI usable on hardware people actually own.

When you’ve spent time getting AI ready to work with your material, you don’t want that effort to go to waste. commonllama lets you reuse the model’s prepared context, so you can return to the work or explore another direction without processing that whole starting point again. Less time rebuilding the starting point means more room to try something, assess it, and try again.

Strata separates the reusable foundation, the material for the task at hand, and the conversation as it develops. commonAgent brings that memory into an OpenCode-powered workspace for conversation, tools, permissions, and continuing work.

The benchmark compares preparation and restoration at six context depths under one recorded model and machine configuration. Every result stays attached to the conditions that produced it.

commonAgentprepared context restored · local

YouLoad the biology chapter I prepared last week and ask my six check questions again. Did any answers change?

commonAgentLoaded the same prepared chapter and asked the same six questions. Five answers match last week’s. One said “cell membrane” where the chapter says “plasma membrane.”

runs on restored context
Time to a working contextone recorded model · one machine
shallow contextsix depthsdeep context
Prepare from scratchReload from diskRestore prepared context
commonFrame

Connect information with action.

commonFrame is our clearest expression of a clear box: a foundation for applications where people can run work, inspect what happened, revisit an earlier decision, and change what comes next.

Desk brings that foundation to the everyday work of reading, writing, questioning, assessing, and revising. Build connects those activities to the workflows underneath them while keeping the history available to the people who need it.

When we build with commonFrame, the foundations for keeping information secure, managing access, and revisiting earlier work are already part of the design. That gives us more room to concentrate on the application your team actually needs.

Desk · Chapter 4, adaptedv3 · revised after review

Core text kept from the open textbook, with its credit.

Practice questions drafted by Qwen3 4B, then reviewed.

Lab example rewritten around a local creek.

Build · the workflow that drafted the questionsTrigger → Agent → Channel out
commonFrame Build canvas with Trigger, Agent, and Channel out blocks connected

DeviseNina Castillo

AuthorNina Castillo, Qwen3 4B (ai)

ReviewTheo Grant

PrepareNina Castillo

Nina, an instructor, adapted a chapter from an open biology textbook for her course. Qwen3 4B drafted the practice questions. Theo, a librarian, checked that the license and credit carried over correctly.
DARP

Preserve who contributed what.

Most work carries the thinking and labor of more people and tools than a byline can hold. DARP is a simple way to record who devised, authored, reviewed, and prepared the work, so credit can travel with it and remain open to conversation.

In the field

Putting our projects to the test, together.

Our open tools and methods get better when people use them in their own work, ask hard questions, and show us what we missed. In October, we are bringing two of those conversations to open education communities.

We welcome funded research and co-development around attribution, reusable context, assessment, local capability, and access to useful knowledge.

Work with us

Bring a question, a hunch, or a rough idea. Share what you’ve tried. We’ll start by listening, then figure it out together.

We take on paid projects, ongoing technical responsibility, funded research, and co-development. Start a conversation below. We reply within two business days, Monday to Friday.