CA—001

Public memorandum

Knowledge systems

Updated 2026.06

Knowledge infrastructure for collective work

Moving the world from chaos to comprehension.

Common Action designs structures through which groups can discover, organize, verify, and act on complex shared knowledge.

The work begins from a practical observation: climate action is also knowledge work. Coordination speed depends on the quality of the information environment around it.

A coordination loop connecting evidence, people, decisions, and action Four labeled nodes are connected by directional lines around a central Common Action node. 01 / EVIDENCE 02 / PEOPLE 03 / DECISIONS 04 / ACTION COMMON ACTION
MODEL / 01 Coordination loop. Conceptual, not measured.

01 / Premise

Coordination is infrastructure

The climate response has an information architecture.

Discovery of resources and peers, accumulated messages, unclear project structure, and the organizational overhead of complex problems consume the time available for action.

Shared infrastructure can reduce that friction: organizing, disseminating, learning, tracking, flagging, analyzing, and managing become parts of one legible operating environment.

The same proposition extends to open science. Collective knowledge needs durable ways to be produced, accessed, inspected, and carried between groups.

02 / Fields

Four connected pressures

Working fields

Separate domains on paper; one coordination problem in practice.

  1. F—01

    Climate

    Organize evidence, actors, interventions, and time horizons without flattening their dependencies.

    SYSTEMIC
  2. F—02

    Energy

    Make technical, territorial, and institutional decision context navigable across teams.

    NETWORKED
  3. F—03

    Agriculture

    Connect field knowledge, ecological conditions, production systems, and shared research.

    SPATIAL
  4. F—04

    Supply Chain

    Expose dependencies across organizations, geographies, materials, and time.

    DISTRIBUTED

03 / Capabilities

Methods attached to uses

Operational matrix

Technical capacity becomes legible when connected to a pressure and an institutional output.

Pressure Method Institutional output
Fragmented knowledge Knowledge engineering, graph databases, semantic web Shared evidence infrastructure
Distributed teams Business intelligence, information architecture Lower coordination overhead
Spatial complexity GIS, spatiotemporal analysis, physical modeling Decision-ready territorial models
Material at scale Data science, NLP, structured analysis Navigable collective knowledge

04 / Protocols

Public operating commitments

A legibility stack

Useful infrastructure communicates not only what it knows, but the conditions under which it knows it.

P—01

Trace the source.

Knowledge should retain provenance as it passes between people, formats, and institutions.

P—02

Render uncertainty.

Known, provisional, disputed, and absent information should remain visibly distinct.

P—03

Design the handoff.

Outputs should survive the meeting, the software migration, and the original team.

P—04

Keep complexity available.

Summaries should support action without erasing the relationships that produced them.