Shaping the hidden forces that rule organizations in the age of AI

Living community edition

The Library

Browse everything in the adaptive operating system — the interactive map in the Navigator, or the full detail tables in the Browser.

Click a column to open it, then click an item to light up how it connects to everything else.

Browse the detail

Values & Principles

Value Tensions

IDNameTension

Principles

IDStatementPrimary meta-structureValue tension

Meta-Structures

All

IDNameCategoryStructural question

Patterns

All

IDNameTypePrimary meta-structure

Interventions

All

IDNameFocus (AAA)Primary meta-structure

Concepts

The vocabulary and reasoning behind Imperception — read straight through for the full picture, or jump to any topic. This is the reference material behind the Diagnostic Engine and the Library.

Imperception

See the hidden structural forces that shape how your organization really works — and what to do about them.

Community initiative · Free · Non-commercial · No registration ·

Diagnose an issue

Describe a recurring symptom in your own words. The engine finds the matching pattern and suggests interventions.

Browse the library

Every value tension, meta-structure, pattern and intervention — as an interactive map or searchable tables.

Understand the concepts

A plain-language guide to the ideas behind the tool: organizational gravity, meta-structures and the TERA cycle.

Propose a Change

Spotted something missing? Suggest an edit or propose a new entry, for a moderator to review.

Diagnostic Engine

Describe a recurring symptom in your own words. The engine matches it to a known pattern, flags the implicated meta-structure(s), and links to any suggested interventions.

Proposal Interface

Draft a new pattern or suggest an edit to an existing entity. Proposals are saved in this browser and can be opened as a pre-filled GitHub Issue for a moderator to review.

How do I propose a change? Step by step

Two things you can do here: edit an existing entry (a wording fix, a wrong link, a missing intervention) or propose a new one (a pattern, principle, meta-structure, value tension or intervention that isn't in the library yet).

Editing an existing entry

  1. Choose Suggest an edit, then pick the entry type — for example Patterns.
  2. Pick the entry itself from the dropdown. Each row shows its reference ID and name, e.g. PA16 · Decision Fog.
  3. You'll see every field twice: the current value on the left, an editable copy on the right. Change only what needs changing — untouched fields are ignored.
  4. Use the Notes / rationale box to say why. This matters more than the edit itself: a moderator who understands your reasoning can apply it correctly even if the wording needs adjusting.
  5. Review the diff. Only genuinely changed fields appear — if a field you edited isn't listed, your value matched the original.
  6. Submit. You can also save a draft, or export the proposal as a PDF, before you commit.

Proposing a new entry

  1. Choose Propose a new entry and pick the type. If you're unsure which type fits, see Concepts → The Gravity Model first — proposing a pattern when you mean an intervention is the most common mix-up.
  2. Fill in the fields. Name and description carry the most weight; leave anything you're unsure about blank rather than guessing.
  3. Link it up. A new entry that connects to nothing is hard to review and easy to lose. Wherever you're offered a picker for related meta-structures, patterns or interventions, use it — this is the single most useful thing you can do for the moderators.
  4. Add your rationale, review, submit.

What happens next

  • Your proposal is saved in this browser and sent to the moderators for review.
  • A moderator accepts, edits or declines it. Accepted changes are published into the live library.
  • You'll be asked for an e-mail address so we can come back to you — see Data Protection in the footer for what happens to it.

What makes a proposal easy to accept

  • One change per proposal. Three unrelated fixes in one submission usually means all three wait on the slowest.
  • Describe the observable signal, not the judgement — "decisions get re-opened three or four times before anything ships", not "leadership is weak".
  • Say what you'd expect to see if the structure were genuinely working. That's what turns a complaint into a diagnostic.

Stuck, or think something bigger is wrong? Use Contact us in the footer — a plain e-mail is a perfectly good proposal.

Master Dashboard

Review pending proposals, compare current vs. proposed content, and publish an updated master_db.json.