Aegean Intelligence Group
BRIER™ by AEIG

Built to be checked.

Living software for predictive analysis.

BRIER is the firm's own system. It keeps every call on a hash-chained ledger. Each morning it seals that ledger with a public timestamp anchored in Bitcoin. It grades each call against a source named in advance. Anyone can check the result without trusting us.

Every diagram on this page shows what runs today, read from the record at build. Parts still being built are marked.

System status, 28 October 2026
  • The ledgerAppend-only and hash-chained. Each approval names who, when and why.Live
  • Daily anchorSealed at 07:00 each day on the public OpenTimestamps calendars, committed to Bitcoin.Live
  • Public record223 calls · fingerprint 10dfa35cc0e9Live
  • Snapshots46 published versions, each named by its fingerprintLive
  • Selection437 statements reviewed · 223 enteredLive
  • Domain desks6 desks · 64 reportsLive
  • World data42 series · 14 early-warning indicatorsLive
  • Forecast LabBlind framings, preregistered. Shipped 21 October 2026Trial
  • LineageEach role carries forward what it learnedIn build
  • Agent cellA disposable cell per job, default-deny networkIn build
The ledger

Append-only. Sealed every morning.

Every act that matters is an entry: a call locked, an outcome recorded, an approval given. Each entry carries the hash of the one before it. The record can only grow. Nothing edits it. A correction is a new entry.

entry 211A call lockedwho · when · whyhash of entry 210
entry 212An outcome recordedwho · when · whyhash of entry 211
entry 213An approvalwho · when · whyhash of entry 212
Each morning, 07:00A dated statementThe day, the entry count and the SHA-256 of the newest entry. Each statement names the one before it.
32 bytes leave the firmIts fingerprint, timestampedSent to the public OpenTimestamps calendars. Nothing else about the record leaves.
Hours laterA Bitcoin blockThe calendars commit the fingerprint to a block. Its height fixes when the statement existed.
LiveKept by a nightly copy outside the firm's serverIn buildPublished with the site's record at every publish

What the seal rules out

  • Edit an entryThe chain breaks at that entry. Every entry after it no longer matches.
  • Remove entriesThe count no longer matches a statement already made.
  • Rewrite and resealA new statement cannot be backdated. Its Bitcoin block shows when it first existed.
One call, end to end

A call moves forward only.

Each call passes through five states. What is fixed at each one never changes afterward. The counts are today's.

  1. 01Candidate437 reviewed

    A sentence from a report, tested against the standard. Private working material, never shown.

  2. 02Locked223 entered

    The statement, its probability, its date and the rule that will settle it are fixed.

  3. 03Open186 waiting

    The window runs. A named public source has not settled it yet.

  4. 04Resolved37 graded

    A named person records the outcome from the source the rule named. The evidence is linked.

  5. 05Scoredfrom 30 families

    Eligible calls enter the public score once enough related groups are graded.

Contested

Sources of equal standing disagree. The call stays open and adds nothing until the founders rule.

Void

A call found wrong in its probability, premise or outcome is voided in the open. It keeps its reason and a correction record. It is counted separately.

Selection is counted

What did not qualify stays in the count.

A forecaster can look good by keeping only the easy calls. So every statement reviewed is counted. Each one that failed the standard is counted by its reason. Selection cannot hide in the denominator.

One square per statement reviewed, 437 in all.

  • Entered the record223
  • A scenario, not a probability108
  • No unambiguous window67
  • No probability21
  • Not publicly resolvable8
  • Another failure of the standard7
  • Duplicate or overlapping3
Independent verification

Check it without taking us on trust.

The whole public record is one file with one fingerprint. Your own browser can compute that fingerprint and compare it. Try it here.

  1. DownloadYour browser fetches the public record, one JSON file.
  2. FingerprintIt computes the file's SHA-256 itself. No server does it for you.
  3. CompareThe result must equal the published fingerprint, character for character.
  4. Go back in timeEvery earlier version is kept as a snapshot named by its own fingerprint: 46 so far.
Run it here
Published fingerprint10dfa35cc0e9e6ca257acb14db0ef714a1a9837a4b92cb658fb6130e0588b81cYour browser's answernot yet computed

How a probability is made

One core remembers. One core reasons.

The reasoning core does not work from a model's general knowledge alone. It anchors each case on a reference class from the memory core. Each class carries its sample size and sources. A named person decides what becomes a call.

Memory core

What it knows

  • SemanticBase rates for defined reference classes, each with its sample size, window and sources
  • EpisodicThe firm's own scored experience
  • ProceduralThe operating standard: how the work is done
  • WorkingThe live problem
Reasoning core

The calibration engine

  • Anchoron the reference class the case belongs to
  • Weighthe evidence against the firm's scored experience
  • Runthe futures, and the strongest case against
  • Expressa probability or an interval
Human gate

A named person

Every probability is a proposal until a named Principal of the firm locks it. Outcomes return to memory only as scored evidence.

The Forecast Lab

Testing whether independent framings forecast better.

TrialShipped 21 October 2026

Reference classesHow often cases like this one came out
Fresh evidenceThe newest reporting and data
The case againstThe strongest argument against the leading view
Each framing works aloneEach works blind to the others on its own evidence. Their errors do not move together.
Combined into one probabilityTested on the record like any other call.
A control at equal effortOne framing run for the same effort. It tells better framing apart from more effort.

The trial was preregistered before any outcome. Nothing it produces enters the firm's public score. It reports no result before its final read.

Scoring and calibration

Graded by a rule that punishes confident misses.

Every resolved probability call is scored with the Brier score: the squared distance between the probability and what happened. A calibrated forecaster's 70% calls come true about 70% of the time.

Try the score

score = (probability − outcome)2

A call at 80% that comes true scores 0.04. The same call that does not scores 0.64. Saying 50% to everything scores 0.25. Lower is better. Confident misses cost the most.

Why the public score waits

Shown from 30 graded families.

Related calls count as one family. One event cannot pass for many tests. With few graded families, even a skilled forecaster's score can land almost anywhere. Move the slider to see how the range narrows.

0.000.100.200.300.400100200300400Coin flip: always saying 50% scores 0.25A genuinely skilled forecaster (assumed 0.17)Graded calls on the record

An illustration with stated assumptions: a forecaster whose true score is 0.17 and a typical spread of single-call scores. It is not the firm's record.

Six desks, one instrument

From public data to a locked call.

Each desk covers one domain. Every figure it uses carries its source and how far that source can be trusted. A reading with no live source says so.

  1. Named sourcesEach with a reliability tier
  2. Collected daily42 series, 14 indicators
  3. Six desksAnalysts and AI, one domain each
  4. Reports64 so far
  5. Calls223 on the record
Agents inside a fence

AI drafts. It never approves.

AI agents do much of the work, inside limits they cannot change. The system enforces each layer below. None depends on the agent behaving.

The recordWritten only by the app when a named Principal presses. An agent's attempt to approve is refused.
The firm's serverRefuses any approve, lock, apply or retire from an agent, at every entry point, before it reads or writes anything.
One jobA short-lived token bound to one job and one scope. The server holds the scope, whatever the agent asks for.
An AI agentDrafts, checks and calculates. Never holds a password or a key.
Every change to BRIER
  1. Tests fixed firstbefore any code is written
  2. Builderin its own workspace
  3. Independent checkerfresh context; never reads the builder's account
  4. Two fix roundsat most
  5. A named Principalmerges and installs
In build

A disposable cell for every job. It mounts one workspace and nothing else. Its only way out is a proxy that denies by default and logs every request where the agent cannot reach.

Being built

Lineage: a system that remembers what it learned.

Each role in the system, the analyst, the checker and the red team, will carry forward what it learned. Every lesson is earned on evidence, checked by another lineage and accepted by a person. It will be measured against a control group that starts with none.

  1. 01InheritA session starts from its role's accepted lessons, read only
  2. 02WorkIt does the job inside its fence
  3. 03ProposeIt may suggest new lessons backed by evidence the agent could not have written
  4. 04CheckA reviewer from another lineage tests each one
  5. 05AcceptA named Principal accepts, edits or declines
  6. 06SignThe app signs a new version, hash-chained

Lineage is data, never instruction. No agent can write to it. A share of sessions always runs with none as a control. Both are graded on the same questions.

Working with us

Run on your own numbers.

BRIER Intelligence puts this system to work on your own business, in a walled space of its own. Every recommendation is written down and graded. Your people decide.

The proof is public

Our own record is open to anyone.

Most advisors tell you what they think. We write it down first and show you how often we were right.