Belief Engines

The product-side source of truth — for people and for agents.

The product-side source of truth. We write what we want; engineering builds it and proves it works.

be-internal/              ONE repo. No code.
└── docs/
    ├── be-category-name/     an area of work
    ├── be-category-name/
    ├── customers/            client areas, behind their own tab
    ├── handbook/                how to work here
    └── how-to-fly/              how the system works

Flat. One level. Every area is named be-<category>-<name>. The one exception is Customers — client areas nest one level so they can sit behind a header tab.

Start here

• How does it work? — the whole system in one page
• Architecture — why the structure is shaped this way
• The harness — .claude/, and how it onboards you
• Editing the wiki — the change loop

Two rules worth knowing on day one

Nothing here reads engineering source. We architect from what we want, not from what exists.

When a spec is ready it becomes a PR, and the PR link comes back onto the spec page — Handoff.