Neurobrick

Neurobrick is an AI governance architecture that separates AI decision proposals from execution authority. Implemented in multi-asset financial research and execution environments.

Readable versions of the same published public pages, including their evidence and scope limits.

Scoped technical changes

Stable identity for evaluation and selection receipts

IMPLEMENTED NOT RUNTIME VERIFIED

What changed

Entry-code fingerprints record an explicit serialization format. Selection replay refuses unknown formats and retains the historical comparison path.

Why it matters

Keeps evaluation and selection observations tied to the entry code that produced them while preserving uncertainty.

Implemented

Pinned evaluation-input and forward-selection receipt modules. Tracker integration and natural runtime adoption are outside this local test population.

Implementation status

IMPLEMENTED_NOT_RUNTIME_VERIFIED

Observed

The supplied local test record contains 8 passed cases out of 8. Natural runtime adoption is not established.

Environment / scope

Isolated Python stdlib modules with synthetic pure callables Evaluation entry-code identity and selected replay counterexamples; excludes tracker integration and natural runtime

Evidence ID

evo-67b239088702e7c706f9

Source commit

4e9700fdfb8a9dcfc6049d74b0157437d19af3fc

Original observation date

2026-10-09T11:47:53.594795+00:00

Canonical record SHA-256

67b239088702e7c706f9ddaaf755b260fb77e65074934f9cfd3db60491d61958

Remaining limitations

No natural runtime or live adoption observed. Entry-code fingerprints do not attest imported dependencies or globals. Pre/post equality does not rule out change-and-restore races. Selection replay does not reproduce statistics, queue effects or execution authority. The pipeline validates recorded identity and consistency; producer authenticity and implementation meaning require human review.

Run artifact SHA-256

6d0a3fbe23089d0750dbc334bacd39e798f2d0a7f26481655b1bcd71e93380e0

Public source and test records →

Archive file SHA-256 →

Unevaluated inputs no longer count as clean evidence

IMPLEMENTED NOT RUNTIME VERIFIED

What changed

Freshness rates count only explicitly evaluated states. Soak readiness requires a recognized comparison-record kind instead of accepting any JSON object.

Why it matters

Prevents missing evaluation from being reported as a clean measurement or as evidence that a comparison ran.

Implemented

Receipt quality calculation, displayed measurement scope and comparison-observation recognition at the pinned source commit. Original input rows, schemas and readiness thresholds are preserved.

Implementation status

IMPLEMENTED_NOT_RUNTIME_VERIFIED

Observed

Source inspection only; natural runtime is not established.

Environment / scope

Pinned source inspection of receipt quality and comparison-observation functions build_receipt, render and soak_maturity only; operating scan adoption is outside this record

Evidence ID

evo-4a2d40d3a7638c025c39

Source commit

8eb4eee4118d8d037db06a1941708e509d6aa0a0

Original observation date

2026-10-22T11:46:26.993Z

Canonical record SHA-256

4a2d40d3a7638c025c3930c8a4a7504aeb1567f44a493cd9b1d47662e5c31e64

Remaining limitations

No natural operating scan adoption or current collector freshness was verified. Recognizing a comparison kind does not authenticate its producer or payload. This correction does not restore older ledger records, establish live trading coverage or enable external anchoring. The pipeline validates recorded identity and consistency; producer authenticity and implementation meaning require human review.

Public source and test records →

Archive file SHA-256 →

Menu names and canonical URLs

Use these actual links when a menu label differs from the URL. Menu-labelled aliases redirect to the same page.

Canonical page