Noetic Log 001 — Pranav Bhave

The finding class

This site presents itself as evidence-bound: claims carry markers, markers carry links, a ledger carries bindings. Two audits of the deployed site found the same defect class at two depths: the interface ran ahead of the verification architecture. Version 0.1 had stale project descriptions behind confident chips. Version 0.2 fixed the copy and built real machinery — and still asserted, in five places, mechanics it did not have. Interfaces are cheap. Enforcement is not. The gap between them is exactly where overclaiming lives, which is what makes it worth documenting on the site it happened to.

Pretense 1 — "rendered from the registry"

Said: The ledger page claimed it was rendered from claims.yaml.
True: The ledger was hand-written to match the registry; CI only checked that each claim ID appeared somewhere in the HTML. Mirroring, not generation.
Now: The ledger is generated by generate_ledger.py; CI regenerates it and fails on any drift. Editing the ledger by hand now breaks the build.

Pretense 2 — "bound to immutable commits"

Said: Claims were "bound" to commit SHAs.
True: The verifier checked that support URLs resolved (HTTP < 400). A resolving URL is liveness; it is not a binding — nothing compared the declared commit to the URL.
Now: The verifier requires the declared commit to appear inside the support URL, and the registry schema treats a commit without a matching URL as a failure.

Pretense 3 — "claims return for review when their evidence changes"

Said: The hero promised event-responsive claim governance.
True: One global 120-day timer existed. Time-based review is real but it is not evidence-responsiveness; the named triggers (kernel change, manifest rewrite) were prose.
Now: Triggers are typed and tagged. Executable triggers run in CI: the bound file is fetched at its bound revision and at the default branch head, and divergence fails the build — the kernel module for CC-001, the manifest for CC-002, the thesis for GA-001, the README for GV-001, and this site's own DESIGN.md by local hash. Triggers CI cannot execute (certification expiry, a private artifact going public) are labeled manual, visibly, instead of borrowing the executable ones' credibility.

Pretense 4 — attested-as-status

Said: The ledger correctly called "attested" a provenance state.
True: The schema then put attested in the same enum as untested/supported/contradicted — collapsing the exact distinction the site lectures about.
Now: Schema v0.2 separates visibility, provenance, support role, evidential status, and maturity. An owner-attested claim with no public artifact now reads what it is: owner-attested · publicly untested. That is less flattering and more true, which is the trade this site exists to make.

Pretense 5 — measured-sounding language for unmeasured things

Said: The design ledger claimed "CLS 0," "zero supply-chain surface," "no pipeline, nothing to break," and — after the first correction pass — still said the empty result card was "stamped inconclusive."
True: Layout shift was never instrumented; the supply-chain surface is small, not zero; a pipeline now deliberately exists; and the card had already been corrected to untested — the ledger describing it hadn't.
Now: All four corrected in DESIGN.md, and DESIGN.md itself is under a local-hash trigger: it can no longer change without the registry noticing.

Primary finding of field artifact P₀

Aesthetic coherence is an epistemic hazard: the better the evidence system looks, the less anyone checks whether it runs. The countermeasure that worked here was not more honesty in prose — v0.2's prose was already honest in intent — but moving every promise into a place where it can mechanically fail: a generator that drifts, a binding that mismatches, a trigger that fires, a hash that changes, a kernel that stops reproducing.

What v0.3 still does not do

The main page's prose and chips are hand-written; only the ledger is generated. A claim-component generator for every rendered surface remains future work.
Executable triggers watch single bound files. Semantics can change outside a watched file; those triggers stay manual and say so.
Continuous reproduction covers CC-001 — one claim, one kernel call. It is the template, not the coverage.
No field performance data exists and none is claimed; the site runs no analytics by design.
The central hypothesis — that claim-bound interfaces improve a reader's comprehension, calibration, or evidence-seeking — is untested. Untested, not inconclusive: no comparison against a conventional control version has been run. The null stands until it is.

The record improves by prosecution, not by polish. Findings against this site are welcome — bring the falsifier.