BBARANES
Technical depth

Baranes Architecture Atlas

A technical view of Baranes for readers who want to inspect lifecycle, effect boundaries and evidence flow. Every view distinguishes current evidence, open-source code and target architecture.

Curated public projectionInteractive
Available now

RepoOps Architecture

The public Atlas starts with RepoOps Architecture: lifecycle, persistent artifacts, bounded candidate boundary, governed Git adoption, execution roles, governance primitives, identity trace and inspectable cognitive cards.

Interactive RepoOps Flow

The diagram is primarily a target architecture cognitive model. SDD lifecycle contracts are separately open source; some RepoOps mechanisms are implemented and evidenced separately, but the map must not be read as a production-deployment claim.

target architectureSDD open sourceclickable nodespan / zoom / local layout
Public boundary

Technical depth with a clear scope.

The public Atlas is deliberately scoped to product architecture, effect boundaries and evidence flow.

Authority boundaries

Three distinctions behind governed effects.

AI systems can execute actions, observe outcomes, verify evidence and record facts. The difficult part is keeping those different acts from silently becoming the same authority.

This short series explains three boundaries in Baranes: the difference between finishing an action and establishing its effect, who owns that effect determination, and what strong evidence can — and cannot — prove.

01 · DONE VS TRUE

Done Is Not the Same as True

A successful execution result and the durable truth of its effect are related, but they are not automatically the same proposition.

Read 01 →
02 · WHO OWNS EFFECT TRUTH?

Who Owns Effect Truth?

Baranes leaves authoritative effect determination with the semantic domain whose state was affected — without requiring one service per domain.

Read 02 →
03 · WHAT EVIDENCE CAN PROVE

What Evidence Can — and Cannot — Prove

Hashes, signatures, provenance and attestations can strengthen evidence without turning the evidence layer into a truth authority.

Read 03 →
EXECUTION REPORTS WHAT IT DID.THE AFFECTED DOMAIN DETERMINES EFFECT TRUTH.EVIDENCE SUPPORTS THAT DETERMINATION WITHOUT OWNING IT.
Technical depth

Curated by explanatory value.

Additional views appear only when they clarify the public product architecture without turning every source diagram into a product claim.