Transparent maintenance

Hack review log.

Brali keeps review history visible. A protocol can be revised, challenged, refuted, restored, or retired without erasing what changed.

830 entries

Active

Published without a later explicit lifecycle conclusion.

143 entries

Reviewed

An editorial or evidence review is recorded and no later event changes that conclusion.

0 entries

Watch

Still usable, but a known uncertainty or fast-changing area deserves monitoring.

0 entries

Needs review

The current conclusion should be re-checked before it is treated as fresh.

0 entries

Contested

Material evidence or reasoning challenges the current recommendation and the issue is unresolved.

0 entries

Refuted

The central recommendation is no longer supported strongly enough to present as current guidance.

0 entries

Retired

Kept for provenance, but no longer maintained as an active recommendation.

Recent review activity

How to read this ledger

The current status is derived from source provenance plus append-only lifecycle events. Existing editorial curation is exposed as legacy review provenance; new changes are recorded in data/hack-review-events.json.

Personal observations can trigger investigation but cannot change an evidence conclusion on their own. A material challenge or refutation requires traceable references.

Machine-readable review data Submit a challenge