← Conferral by Design

Granted Attention · the public record

The corrections record

nothing is removed from this page

This page lists every substantive change to a claim published on this site: what was said, what defeated it, what replaced it, and when.

It exists for a specific reason. The argument elsewhere on this site is that a company publishing a number about itself only tells you something if the apparatus around it is expensive to fake — a definition fixed in advance, unknowns reported rather than absorbed, bad periods left visible, and corrections preserved rather than deleted. It would be incoherent to argue that and not keep the record.

Nothing is removed from this page, and entries are not edited after the fact except to add a later correction. If a claim here is itself wrong, that becomes a new entry rather than a revision of an old one. Superseded pages are archived rather than rewritten.

If something published here is wrong, the useful thing to send is the counter-case — the specific situation the claim fails in. That is what produced every entry below.

Reading a cluster

Entries sometimes arrive in clusters, and a cluster usually means one cause rather than several. Four of the entries below are dated 6 September 2026 and they are all the same mistake: a claim was corrected in the instrument where it was caught, and left standing on the other pages that made it. The homepage published a claim this record had retired five days earlier. The access opener repeated a misclassification the calculator had fixed three days earlier.

That is worth stating plainly, because the fix for it is not a better sentence. It is a check: retired claims are now listed in the registry that governs this site, and the build fails if one reappears on any page except this one and the standard's revisions log, which exist to quote them. The test of whether a correction was real is whether the same error can still be made — and until 6 September it could.

The record

6 September 2026 · / — the three route beats and the opener’s contested reading

The homepage published the claim this record had already retired, five days earlier.

What it said

That a contested route “does not accumulate,” that “a direct route is the only one you can act on,” and — as the heading over all three — that of the three routes “only one of them is an asset you hold.”

What defeated it

The 1 September entry below, which had already retired exactly this language: rented and contested routes plainly do accumulate — income, craft, credits, reputation — and what fails to accumulate is renewable access. The correction was made in the instrument and never swept back to the homepage, so the front door of this domain spent five days contradicting the record two clicks away. Found by an external review reading the two pages against each other.

What replaced it

The distinction is now renewable access rather than accumulation, in all three beats and in the opener’s contested reading. The direct route is described as the one whose terms are yours, not the only one worth having.

The reusable lesson is the one directly below, arriving a second time: when a claim is retired, every page that makes it has to be found, not just the page where it was caught.

6 September 2026 · /calculator — the Read paragraph and the R metric

The calculator called its own worst case durable, and told people with no referrals to buy growth.

What it said

Two paragraphs, one under the other. For a business whose customers all arrive through partners and hosts — Granted Share 100%, Rent Index 1.00 — the first said the demand “feels like an asset and behaves like a lease.” The second said “demand like this is durable — it rests in your customers, not your ad account.” Separately, any reproduction number below 0.9 printed “growth still needs buying.”

What defeated it

The Read paragraph was keyed to Granted Share alone and never consulted the Rent Index the page had computed six lines above it. A high granted share with a high rent index is the eviction-exposed profile, not the durable one — so the reassuring sentence fired on precisely the position this site exists to warn about. The reproduction line was a separate error of reasoning: an absence of customer referrals does not establish that paid acquisition is required, and on this run it contradicted the same page’s finding that every customer had arrived conferred.

What replaced it

The Read paragraph now branches on both numbers and names both halves when they disagree. A low reproduction number now says what it observes — that customers are not yet producing customers — and never prescribes spending. The reproduction figure also carries the run’s confidence, because at ten customers one referral moves it by 0.10.

Found by running the instrument to its corners and reading the output as one page, rather than reading the source. Both sentences were defensible alone and only contradict each other on screen.

6 September 2026 · / — the access opener’s three rows

The opener counted people a platform showed you to as people who had chosen you.

What it said

That the middle route was “Through something in between — a platform, a gallery, an agency, a publisher, a marketplace,” and that everything in it counted toward the headline finding: “N of ten arrived having already chosen you.”

What defeated it

The row named a channel and asked nothing about orientation, so it swallowed two different arrivals: the collector who asked a gallery for you, and the stranger a feed put you in front of. Only the first had chosen you. This is the same defect as the calculator’s category-search row, corrected three days earlier and never swept to the opener.

What replaced it

The middle row now states the condition before the channel — they had already chosen you, and the way back runs through someone else — and the contested row explicitly names the feed that reaches people who had never heard of you. A standing rule was added: every route row on every surface asks orientation before it asks channel.

Three entries dated today share one cause: a correction made in one instrument was not carried to the others making the same claim.

6 September 2026 · /scorecard — the opening

The scorecard called itself an audit and said it was not one, in consecutive sentences.

What it said

Its eyebrow read “the public audit instrument,” its opening ended “so this is an audit rather than an opinion poll,” and the paragraph immediately beneath read “a decision aid, not a measure of trustworthiness, a certification, an audit or a prediction.” It also claimed “no model, no guesswork.”

What defeated it

An audit is conducted by someone who is not the subject; that property is the whole meaning of the word, and it is what the paid review actually sells. Claiming it for a self-score overstated the free instrument and devalued the paid one in the same breath. “No guesswork” was true of the arithmetic and false of the instrument: the inputs are ten human judgements, which is why every score carries an evidence tag and why the reliability question is open.

What replaced it

It is a scoring instrument and a structured comparison. The deterministic claim is now made about the arithmetic specifically, with the judgements named as the reader’s own. The word audit is no longer available to any self-scored instrument on this site.

The contradicting sentences were adjacent on screen and eleven lines apart in the file. Reading the rendered page is not the same as reading the source.

3 September 2026 · /calculator — channel table v1.2 · /standard — v1.1 → v1.2

The calculator counted platform followers as a route you control, and category search as demand you were given.

What it said

That “your email list, subscribers, or followers” was a single row scoring granted and direct, and that “search (including searching your name)” was granted and direct too. The Metrics Standard’s definition of Granted Share counted “search-with-intent” as conferred.

What defeated it

Both rows bundled positions that the framework separates. A list whose addresses you can export is direct; followers on a platform are rented, because the platform decides whether they ever see you again — the exact conflation the book spends a chapter correcting. And the search row was wrong on both axes: someone searching your name chose you and arrives somewhere you control, while someone searching a category or “near me” chose nothing and your listing competed for the click. That is contested, and it was being counted as granted demand.

What replaced it

Eleven rows became thirteen at channel table v1.2. The list row splits into a permissioned list you could export (granted, direct) and followers or subscribers on a platform (granted, rented). The search row splits into a search for you by name (granted, direct) and a category or “near me” search (contested). The Standard’s Granted Share definition now reads a search for you by name, published as v1.2.

How it survived

The vocabulary pass of 2 September renamed this instrument’s owned to direct and stopped there. Renaming the label made the wrong mapping underneath read as corrected. The reusable lesson: when a term is retired, every place that assigns it has to be re-derived, not only every place that prints it.

Found by an external strategy audit walking the live instrument, not by any check in the repository. The arithmetic is now derived from the channel table itself rather than from hardcoded row positions, so a future row cannot silently break it.

2 September 2026 · /standard — Conferral Metrics Standard v1.0 → v1.1

The standard defined two of its own metrics in the vocabulary it had just retired.

What it said

That the Granted Share proxy for creators was “owned-channel opens + returning viewers”, and that the Creator play computed “GS = owned/returning consumption ÷ total” with Conferral Premium as “revenue per owned-audience member.”

What defeated it

The same argument that corrected the creator audit the day before: nobody owns people, and the property that matters is control of a direct, portable route back. It is worse in a standard than in an instrument. An instrument in retired vocabulary gives one person a stale label; a standard’s definitions are the thing other people are invited to adopt, so the retired model propagates into every measurement built on it.

What replaced it

Direct, in all three definitions, published as v1.1. No formula, threshold, proxy or predicted outcome changed — this is a vocabulary revision and the revisions log says so. A second thing was resolved with it: the calculator had been stamping every result and share card “Conferral Metrics Standard v1.2” while this page still published v1.0, citing a version that did not exist. Publishing the corrected definitions as v1.1 makes that stamp true instead of leaving a phantom version behind.

The standard’s own rule is that metrics which get redefined silently die. Found by sweeping the domain for a retired word, not by anyone reading the standard.

1 September 2026 · /route-audit

The audit called a position “owned,” and told creators the other two build nothing.

What it said

That the third position was Owned — that the creator “holds the relationship” and that this is “the part that compounds.” Contested attention, it said, was one where “nothing accumulates on its own.”

What defeated it

Three things. Creators do not own people; the property that actually matters is whether they can start the next contact themselves and move the route to another provider. Rented routes plainly do accumulate — income, craft, credits, reputation — and what fails to accumulate is renewable access, which is a narrower and truer claim. And the implied advice was wrong: a session musician, a jobbing actor or a commissioned illustrator can build a durable career across several institutional relationships and never hold a direct audience at all.

What replaced it

The position is now Direct, defined as control of direct, portable access, with ordinary replaceable infrastructure explicitly not counting as a landlord. The compounding claims are gone. The next move no longer assumes conversion is the goal — where no route is portable, it asks whether the creator depends on a single one, and offers a second landlord or firmer terms alongside building a route. The three lease questions — what you keep paying, who can change the terms, what survives if it closes — were added, for rented routes only.

The instrument predated the theory it implements. Found while writing the book that uses it.

31 August 2026 · takenorgiven.com/theory — Parts Three and Five

The corpus gave two different accounts of the same thing, and the abstract of one paper contradicted its own argument.

What it said

Two of the seven papers treated algorithmic distribution as contested attention — a contest the feed rewards whoever wins. Two others treated it as rented conferral — a floor an intermediary grants, on a relation the recipient does not own. Worse, in Part Three the stale account was in the abstract while the sharper one was already in the body, so the summary of the paper disagreed with the paper.

What defeated it

The same event cannot be two things. Being picked up by a recommendation system is, from the recipient’s side, a conferral: the floor arrives already granted. What makes it different from owned conferral is not that it was contested but that the conferring relation belongs to someone else. The contested/granted distinction was never wrong — it was carrying a second question inside it without saying so.

What replaced it

Part Three’s abstract now states what its body already argued: the platforms began as engines of owned conferral and converted themselves into engines of rented conferral, keeping the appreciation. That version is also stronger, because it explains why the feed felt like a gift for a decade before it stopped — the old version had to treat a decade of users as mistaken. Part Five gains a paragraph: the captured floor is itself rented, which is the reason attention-rich authority is unstable rather than merely fickle. Both papers carry a dated revision note.

The distinction itself is unchanged. Attention still arrives in one of two ways; what was missing is that granted attention divides again by who holds the relation.

31 August 2026 · /privacy

The privacy page described data collection that the code had stopped doing.

What it said

That the first-party event beacon records “which band your result fell into,” giving “Design Scorecard: capture-financed” as the worked example.

What defeated it

Scorecard v2.0, published the same day, removed band labels entirely. The beacon now carries the score. Nothing was collecting a band any more, so the page was describing a practice that had ended — on the one page where an inaccurate description is a compliance question and not only a credibility one.

What replaced it

The paragraph now says the beacon carries the single headline value, gives the current example, adds channel names to the list of things never sent, and states that the creator audit sends nothing at all.

Found by an audit of both live sites, not by a reader.

31 August 2026 · takenorgiven.com · the test and /student

The confirmation message promised a five-day email series that does not exist.

What it said

The offer above the email field said the profile is written out and sent by hand — usually within a few days. The confirmation that appeared after submitting said something different and fixed: “Sent — your full profile is on its way. The short series follows over the next five days.”

What defeated it

The offer text switches on which fulfilment mode is live; the confirmation did not, and carried the automated-series wording in every mode. The mode in production is the manual one. So anyone who submitted an address was told a five-day sequence was coming that nobody had built and nobody was going to send.

What replaced it

The confirmation now switches on the same setting the offer does, and in the current mode says the profile is written by hand and to give it a few days. If you gave an address before this was fixed and expected a series, that is the reason it did not arrive, and the apology is mine.

Live for an unknown period before it was found. Fixed 31 August 2026.

31 August 2026 · /design/two-numbers · /standard

Initiated Share v1.0 is retired. The prompted/initiated binary was wrong.

What it said

A proposed measure, Initiated Share, defined as the fraction of sessions a person began without the product having prompted them — with any session opened inside a stated window of a notification, email, badge or re-engagement message counting as prompted. The stated interpretation was that initiated use was closer to wanted use and prompted use closer to captured use.

What defeated it

User-configured scheduled tasks. A person authorises a product to do work later; the product does it and notifies them; they open the result. Under the v1.0 definition that session counts as prompted, so the measure falls precisely because the delegated service worked as requested. Both ChatGPT and Gemini document this pattern in their own help material. The prompt was the delivery mechanism of a prior grant, not evidence of capture.

What replaced it

The session-origin distribution: eligible sessions reported across eight disclosed origin classes, with no weighted aggregate and no assumption that any class is intrinsically good or bad. Unprompted initiation survives as one class among eight.

Published and corrected the same day.

31 August 2026 · /design/two-numbers

The claim that both measures were “a query, not a project” was half wrong.

What it said

That both proposed numbers already existed inside these companies, so publishing them was a matter of willingness rather than engineering.

What defeated it

Working through what a session-origin measure actually requires: a controlled prompt taxonomy, a link from each delivery back to the authorisation that created it, cross-surface identity, exposure states, a versioned attribution window, and an honest representation of unclassifiable cases. That is a project.

What replaced it

The claim now holds for withdrawal only, and says so. Withdrawal events are close to already-instrumented; session origin is engineering work. The page states which half survived.

Published and corrected the same day.

31 August 2026 · /design/two-numbers

“Publishing first is a costly signal” overstated what first publication achieves.

What it said

That the first company to publish one of these numbers makes a commitment a competitor can only match by publishing their own.

What defeated it

A self-defined, unaudited number published once is cheap for anyone to produce. The definition can move, an unflattering period can quietly not appear, and nothing follows from misstating it. First publication alone does not separate a trustworthy product from an untrustworthy one.

What replaced it

The separation comes from the apparatus, not the act: a definition fixed in advance and versioned when it changes, unknowns reported rather than absorbed, bad periods left visible, corrections preserved with dates, and eventually independent assurance. The page now argues that, and this record is part of it.

Published and corrected the same day.

31 August 2026 · /scorecard · /design · /review · /reliability

Scorecard v2.0: the band names were verdicts, and the red flags distorted the arithmetic.

What it said

A total score placed the product in one of four named bands — Conferral-designed, Granted core, contested edges, Capture-financed, Engagement-economy replica — and any tripped red flag capped the result at Capture-financed regardless of the score.

What defeated it

Two problems. The band names are diagnoses of a business model, produced by a rubric with no validity evidence behind it; a label cannot claim more than the instrument can support. And an unvalidated aggregate does not become more meaningful by being overridden — a finding that matters does not need to distort a total in order to matter.

What replaced it

v2.0 reports the criterion profile and earned / available points with no band label at all. Red flags are reported separately as non-compensatory findings, each with its own rationale, and they no longer change the total. Criteria 2 and 8 were re-anchored to match the session-origin correction above. v1.0 is archived rather than rewritten, and three further criteria are openly marked as under revision.

v1.0 published 2026-08-29; superseded 2026-08-31, before any external use.

What is not on this page

Typographical fixes, broken links, layout repairs and copy edits that do not change a claim. This is a record of things that were wrong, not a changelog.

Open work is also not a correction. Where something has not been established, the honest place for that is on the page making the claim: the scorecard’s validity status, the pre-registered reliability study that has not yet run, and the three criteria openly marked as under revision are all stated where they apply.

Corrections are logged here because the argument on this site is that published self-reported numbers mean something only when the apparatus around them is expensive to fake. A corrections record is part of that apparatus.

Related: Conferral by Design · The scorecard · The reliability study · The session-origin distribution