Critique

What kind of response helps?

A strong response names the pressure point: the assumption that fails, the tradition or literature it misreads, the empirical bridge that does not hold, or the disconfirmation condition the site has not yet made explicit.

Submission is not subscription. This site uses no cookies and no cross-site tracking; the only measurement is Vercel’s cookieless, aggregate web analytics. Contact details are optional and are used only for follow-up if you explicitly allow it. Nothing is quoted publicly on /responses unless you opt in.

The optional sharpening tool sends only your draft objection to a server-side LLM endpoint and stores no conversation memory. It is there to help you make your critique sharper, not to answer for the theory.

Changelog

This is a git-backed changelog. Each released version records what changed, why, and the objection(s) that prompted the change — linked to the objections ledger so any revision can be traced back to the critique that caused it. Because the source is kept under version control, every change is a diff that can be inspected line by line.

v2.0 — 15 July 2026

The contact release — the first version of this framework caused by its critics rather than chosen by its author. A blind pilot round of four AI readers (distinct model weights, one vendor; commissioned by this project and logged in the reception ledger with provenance stated) met objection 11's pre-registered flip threshold: three of four read the dynamic term as a hidden engine after the guardrail, and the round located the first flip condition already tripped in the site's own prose. The published clause fired, and v2.0 is its execution. What changed: the canonical dynamic term is renamed — resolution becomes cohering, chosen to claim less (a coherence-event is a coherence, and coherence is not contact) — with the rename record kept on the page; the causal "alters the conditions" wording is withdrawn from the definition; objection 13's reply is withdrawn entirely, restoring the strongest structuralist objection to full strength (v1.5 had quietly used the dynamic layer as a metaphysical realizer — its guardrail's exact failure mode); a fourth flip condition adds the fold-side sensor objection 6 lacked; and the spine question v1.5 left open is closed, answered no, with the record preserved. What did not change: every strong-tier claim, every confidence number, every tier. v2.0 is a contraction, not a growth — the framework claims less than v1.6 did, on the record, because readers were right. Also in this release: the site becomes two firewalled programmes. The container programme goes public with its own machine layer (container.json), its own pre-theoretical claims (C1–C4), eight drawer conditions including a staleness clause, and a non-transfer rule with a deliberately uncomfortable asymmetry: its results may wound the framework's claims and can never establish them — the single pre-registered exception, Study B bearing on S1's weak reading (supporting, never establishing, symmetric in both directions), is published in container.json. Its origin corpus — a working note that was adversarially red-teamed before publication, shrank under the attack, and shipped with the wreckage attached — is published in full.

v1.6 — 1 July 2026

The evidence layer. This release changes no metaphysical claim, adds no term, and moves no tier. What it adds is discipline machinery for a framework that now has data. The claim graph gains an evidence block carrying Study 1 — graded honestly as a pilot with an unsettled effect size — under an explicit non-transfer clause, stated in claims.json and on the AI-reader page: results from the research arm evidence the coherence-is-not-contact discipline only, and transfer nothing to the fold, resolution (since renamed 'cohering'), or any graded claim, unless a result tests a prediction derived from that claim specifically. The open hinges become failable: objection 11 now publishes the concrete conditions under which it flips to failing, with review dates, and objection 6 carries the same discipline. The reception ledger opens with its honest zero, the critique form gains structured target/failure-mode/origin fields, and a standing results ledger reports every pre-registered prediction — including the null. The Study 1 presentation was put under its own knife: confidence intervals added, the under-powered AUC contrast publicly walked back, and a measurement confound disclosed with the re-run that settles it specified.

v1.5 — June 2026

The dynamic layer. This release adds resolution (renamed "cohering" in v2.0), temporary conditioned coherence, as a dynamic term the structural v1.0 lacked — and it does change graded claims. Two medium claims (M4, M5) enter the claims ledger, and the two speculative claims (P1, P2) are re-read from static identities into process form. The working paper gains Part VIII, and the reification of the new term is logged as objection 11, open. The speculative-tier invariant is preserved: switch it off and every strong and medium claim, the dynamic layer included, still stands.

This proceeded ahead of external critique, by choice, and thereby superseded the original critique-driven v1.1 plan: with no engagement yet to wait on, the layer was published as the most honest current statement of the proposal rather than held back. Truth is not the same as certainty: the layer is committed and graded, not asserted as settled.

v1.0 — 28 May 2026

Initial public release of the working paper, Aperture Framework, research agenda, objections ledger, and design doctrine. This is the baseline against which later diffs are recorded; there are no prior versions.

Site updates since v1.0

The version number tracks the claims, not the site. v1.5 changed graded claims; v1.6 deliberately did not.

15 July 2026 (evening). The reception loop, actually closed this time — a correction this ledger owes its readers. From the critique form's 1 July launch until today, the form and the sharpening tool were broken in production: a runtime misconfiguration (storage credentials injected under a different name than the code read) meant every submission attempt returned an error. Found when the author tried his own form; fixed and verified with a successful test submission today. The consequence, stated plainly: the ledger's zero unsolicited entries between 1 and 15 July measured a closed door, not an indifferent world — silence over that window is uninformative, and any inference drawn from it, including in our own deliberations, is retracted to that extent. The failure class is worth naming: production configuration is state no drift test can see, a known blind spot of the honesty machinery, now covered by an ops runbook and post-deploy checklist.

15 July 2026 (later). The physics-side genealogy, sourced. The container diagnosis's physics half gains its canonical owners in the academic edition — Jammer (with Einstein's foreword naming "space as a container of all material objects" as one contingent concept), Earman, Leibniz–Clarke — and specific credit to Traxler (2017), whose transcendent/immanent re-carving of the history of space is the nearest published neighbour to this proposal's physics arm, under this site's own keyword (a coincidence, disclosed). Her two pushbacks are recorded rather than smoothed: quantum practice read as still container-shaped, and complementarity rather than retirement as the verdict. S2's owner line updated; an adjacent-reading note added — deliberately not a Positions entry, because a single-article author is cited for her move, not ranked with the position-holders.

15 July 2026. First reader contact, and the machinery fired. A v2.0 promotion of resolution (since renamed "cohering") from layer to spine was under consideration; rather than promote on internal momentum, the promotion criteria were amended in the open (record on the repository) and tested the same day with a pilot reader round — four AI readers with distinct weights but a single vendor, given only these public pages, briefed to attack. The round answered the promotion question no, and found more: three of four readers reported the engine-reading of resolution after the guardrail, meeting objection 11's third flip-condition threshold at pilot tier, and the round located a leak on the objections page itself — objection 13's reply deploying resolution as a realizer. Objection 11's status is updated accordingly, rename evaluation is open (candidates: coherence-event, cohering), a fourth flip condition adds the fold-side sensor objection 6 lacked, and one vocabulary collision (the companion study using "resolution" in the plain closure sense) is corrected. Provenance stated plainly: the readers were commissioned by this project and share a vendor, which is why the hinge was placed under review rather than failed. Superseded the same day: v2.0 (above) executed the rename and the objection-13 withdrawal.

2 July 2026. The front-door release. The homepage hero is redesigned to enact the thesis rather than illustrate it, and no graded claim changes. The old hero image was a view from outside — a fold pinned to Cartesian axes in an illustration slot, on a page that says there is no outside from which the view is delivered. Now, on a desktop, the prepared figure frame stands empty ("Fig. 1 — the self-referential fold.") while the fold itself rides the reader's own pointer, labelled where you are; carried to the frame's middle, the border dissolves, and a click commits: there is no box; there's just what's happening. On a phone, the hero is one typeset sheet that scrolling turns through itself — recto outward · world, verso inward · awareness — one structure, two orientations, performed rather than asserted. Readers with reduced motion get designed still states, not frozen animations. The social sharing card is redrawn to match.

2 July 2026. The register release. After pressure-testing against Strawson and illusionism, and a full-site review: the canonical summaries are rewritten diagnosis-first, with the identification stated as a priced wager; the claims ledger gains falsifier, owner, and author-assigned confidence fields (numbers live in claims.json only); four objections are added — illusionism, the realization objection, the order of certainty, and the status of "exactly two"; the working paper's Part I gains the production-presupposes-containment argument; the academic edition restates the diagnosis as a candidate solution to Chalmers' meta-problem; the research agenda gains Study 5, the dissociation study; the readings page becomes Positions; and one claim's wording is corrected within its tier — S2 no longer names fundamental physics as the leading arm of convergent pressure, matching the academic edition's Section 4. Overclaiming metadata, an unhedged agent-facing page, and a "pre-registered" label with no registration artifact were also corrected.

10 June 2026. Scholarly strengthening. The paper states the formal status of the "exactly two orientations" claim against the mathematics of self-reference (Lawvere, Scott, the eigenform tradition): characteristic, argued, not yet demonstrated. The academic edition adds the measurement problem as a second, cautioned point of contact on the physics side, and places reflexive monism (Velmans) as the nearest neighbour by name. Readings gains Dōgen's "Uji" (Being-Time), with the sharpest counter-argument on the page.

31 May 2026. The academic layer and critique infrastructure: academic edition, interactive claim map, readings on a fixed template, status triage on the objections ledger, structured data and discovery files.

Reception ledger

The public record of where the argument was pressed, what held, and what had to change — not a gallery of endorsements. Each published entry names its target (a claim id, an edge, or an objection), the failure mode claimed, the critique in its strongest form, and what it changed. Publication is a git commit, so every entry is a dated, inspectable diff. Nothing appears without the respondent's consent; anonymised summaries are used on request. The machine-readable version is reception.json.

Standing commitment. If a critique causes a revision, the changelog cites it, attributed only with consent. A critique that is right gets the change; a critique that is wrong gets a written reply; neither is quietly dropped.

Provenance, stated because it matters: the first four entries are the July 2026 pilot reader round — four AI readers with distinct model weights but a single vendor, commissioned by this project, given only the served pages, briefed to attack. They are logged because they caused revisions (the ledger would be drifting if the changelog cited critiques the ledger did not carry), and they are marked as what they are. Unsolicited critique, human or machine, enters through the same schema; the agent-facing layer invites it, and the form records origin. Expert outreach has still not been sent.

Publication policy, and what a revision looks like

Responses are selected for public posting when they press a substantive point: a conceptual break, a missing distinction, an empirical or scholarly correction, a sharper objection, or a disconfirmation condition that should constrain the next claims release. Nothing is quoted publicly unless the respondent opts in.

A claims revision is triggered by at least three independent critiques converging on the same structural issue. (The original plan reserved this trigger for a v1.1; v1.5 preempted it by shipping ahead of critique. v2.0 then became exactly such a release: the July 2026 reader round's critiques converged on the dynamic term and its uses, and the changelog cites them.) Possible forms: a tightened or weakened claim; a new objection with a written reply and a clear status; a new disconfirmation condition in the research agenda; or a removed passage that was doing more confusing than clarifying work. Each revision is released with a version number, a changelog entry, and — because the source lives in git — an inspectable diff.