Acacia Wiki What We Build · 1 of 2

ContextOS

A system for understanding, documenting, and transferring context — the container for intelligence.

The Core Argument

Context is the container for intelligence. Without context, intelligence is just data — it cannot be understood, trusted, or acted upon.

We have seen the Context Problem: in a world of abundant intelligence, the challenge is not producing answers — it is knowing which answers to trust.

ContextOS is the answer to that challenge. It is a system that helps organisations understand, document, and transfer context — so that intelligence can be evaluated, trusted, and acted upon.

ContextOS is the shipping container of the Judgment Economy.

What ContextOS Does

Five functions of the system.

1. Makes context visible

ContextOS surfaces the context that is often hidden — the assumptions, constraints, history, and relationships that give intelligence meaning.

2. Documents context

ContextOS provides a structured way to document context — so that it can be shared, reviewed, and preserved over time.

3. Transfers context

ContextOS enables context to move between people, teams, and organisations. It makes context portable and reusable.

4. Supports judgment

ContextOS provides the structure that judgment needs — a clear process for evaluating intelligence, weighing options, and making decisions.

5. Enables accountability

ContextOS records decisions and the context in which they were made. This enables accountability and learning.

The Acacia perspective:

ContextOS is not just software. It is a system — a way of working that makes context visible, transferable, and accountable. It is the container for intelligence in the Judgment Economy.

The ContextOS Process

A structured way to move from answers to decisions.

ContextOS provides a structured process for moving from answers to decisions. It is based on the insights from the Context Problem section:

  • Information is not context. Context must be actively surfaced and documented.
  • More answers create problems. We need a way to evaluate and filter intelligence.
  • Symptoms are not causes. We need to diagnose before we advise.
  • Diagnosis must come before advice. Understanding comes before action.

Understand the situation

Begin by understanding the situation — the history, constraints, relationships, and context that matter.

Clarify the problem

Define the problem clearly. What is the challenge? What are we trying to solve?

Identify the friction

What is getting in the way? What is the friction that needs to be addressed?

Examine the evidence

What evidence do we have? What do we know? What do we need to find out?

Consider possible responses

What are the options? What are the trade-offs? What are the risks?

Support better decisions

Make the decision. Document the reasoning. Act with confidence.

Learn from what happens

Review the outcome. What worked? What didn't? What can we learn?

Key insight:

The ContextOS process is not a linear checklist. It is a cycle — a continuous loop of understanding, deciding, and learning. This is how judgment improves over time.

Explore ContextOS

Eleven pages that unpack the system and its implications.

01

What Is ContextOS?

An introduction to the system.

Read →
02

The Problem ContextOS Addresses

Why we need context infrastructure.

Read →
03

Understand the Situation

The first step in the ContextOS process.

Read →
04

Clarify the Problem

Defining what needs to be solved.

Read →
05

Identify the Friction

What is getting in the way?

Read →
06

Examine the Evidence

What do we know?

Read →
07

Consider Possible Responses

What are the options?

Read →
08

Support Better Decisions

Making decisions with confidence.

Read →
09

Learn from What Happens

Reviewing outcomes and improving.

Read →
10

ContextOS and AI

How ContextOS works with artificial intelligence.

Read →
11

What ContextOS Does Not Do

The limits of the system.

Read →

Reading path:

Previous

What We Build

Status

Working Concept Note