The collector binder now says when a scan is scoped rather than a lifetime record. Unknown custody is shown as unknown, not a fabricated zero. Tax exports refuse incomplete scans instead of inventing a lifetime IRS file.
Comparable sales exclude operator and lending wallets
In review. Comparable sales now exclude operator-wallet and lending-protocol transfers, and the sales history labels those prints. When a screening source is unavailable, the report withholds the fair-value point, range, and deltas and says Insufficient data — screening source unavailable instead of guessing a floor number.
Wallet sessions and payments stay steady through brief drops
Wallet sessions now stay signed in through brief network drops, wallet reconnects are faster, and gated purchase buttons stay readable instead of dimming.
Failed reports name a Sentry event when no request id exists
In review. If a fax report cannot load and there is no request id to quote, the error page now shows the Sentry event id when one exists, or says no reference is available — see Sentry event. It no longer prints Error reference: unknown with no guidance. Display only; no scoring or pricing change.
Closed-launch notes stay readable on gated methodology and glossary citations
While the product is still closed, gated methodology and glossary citation surfaces show a closed-launch note, methodology links stay reachable as notes instead of dead ends, and the launch state matches across pages. Payments stay closed until public launch.
Report pages stay private; errors show a quotable reference
In review. Fax report pages are private and not stored in public caches. A temporary load failure says the report is unavailable, offers Try again, and shows an error reference you can quote. Footer nav and legal links stay reachable. The sitemap is built from the live token catalog and asks crawlers to retry when that source is down. Display and reliability only; no scoring or pricing change.
Fair value leads with a range; the point estimate is secondary
In review. Where same-token sale dispersion exceeds the 15% point-accuracy bar, the report leads with a defensible fair-value range and demotes the single point to an indicative secondary figure; with insufficient coverage it says Insufficient data instead of a number. The homepage sample certificate stays withheld until real coverage supports a figure. Display and copy only; the pricing model is unchanged.
Lineage tool: dog pairing restored and Koda/Otherdeed art shown
In review. The lineage tool restores the 9,602 indexed BAKC companions from the chain-derived pairing index. Koda and Otherdeed slots now pass through token art and use visibly labelled representative art when token art is unavailable. Otherdeed lookup failures render as degraded, not absent, and lineage index reads have a two-second query deadline. Display and data-truth fix only; no scoring or pricing change.
In review. A /dmca page presents ApeFax's counsel-delivery DMCA draft from the checked-in source: scope, notice requirements, contacts, counter-notices, and repeat-infringer policy. Contacts use the same constants as Terms and Privacy. Tests pin the source hash, section order, and contact sourcing. The draft is awaiting counsel's one pass. Legal copy only; no product behaviour changed.
Rarity rank is labelled as the OpenSea-published rank everywhere it appears
In review. Every rarity rank on ApeFax now names its source: it is the rank OpenSea publishes for the collection, not one ApeFax computes. Rank is a separate axis and never changes the grade; if OpenSea publishes none, the cert shows it as unavailable and the integrity score records a low-severity flag with a fixed deduction. No scoring, pricing or rank computation changed.
Locked report previews keep the exact integrity score private. Reports with insufficient verified history now show an unverified state without a numerical score across report, tool, account, certificate, and verdict surfaces. No scoring methodology or tier threshold changed.
Fair Value and Calculators can again resolve the public BAYC teaser and locked viewer data while launch remains closed. Refresh, history, payments, minting, and paid report data remain unavailable until their existing launch gates are approved.
Applied 2026-07-22. The View-refund ledger and revocation machinery are live — every future refund is recorded immutably, bound to its exact source payment, verified on-chain, and refunded access is revoked everywhere. No refund has yet been issued; refunds remain founder-executed under our operating procedures; the Terms govern when a credit or refund may be requested. This is the machinery, not a policy change.
Health reporting is now truthful under degraded conditions
Deployed 2026-07-21. Handled degraded states on the freshness health surface now return a readable JSON body — previously they could surface as opaque gateway errors. Import-time failures remain a disclosed residual. Monitoring and the data-pipeline gates now classify from payload content. This is monitoring and operations honesty; no scoring or pricing change.
Payment-support links now carry report context, refund and renewal wording matches current behavior, and privacy copy accurately states SIWE, IP, telemetry, retention, and data-rights handling. Deployment, mailbox proof, operator rehearsals, counsel review, and an atomic refund writer remain pending.
ApeFax now records only normalized aggregate product events and LCP, INP, and CLS, never raw search text or dynamic identifiers. Critical routes, writer and evidence freshness, deployment identity, and fair-value quarantine now feed one daily health digest; production delivery remains pending.
Launch recovery and incident controls clear code gates
Signed backup, independent-copy verification, preview restore, edge checks, monitoring delivery, and incident-response controls now pass candidate code gates. Release remains pending until the production backup, isolated restore, edge, Sentry-to-Discord, custody, and founder approval receipts are complete.
Launch capacity and abuse controls clear code gates
Collections now use 30-minute static regeneration, public API inputs and rate budgets fail closed, OG errors cannot be cached publicly, and entitled trending responses are cache-separated. The exact implementation passed a bounded 286-request local smoke; live edge, proxy, deployment, and monitoring proof remains pending.
Launch email delivery controls prepared for release
Signup receipts, the founder-controlled launch announcement, preference handling, bounce and complaint suppression, and replay-safe batch delivery now pass the candidate gates. Delivery remains disabled until the founder-owned production proof is complete; no launch email has been sent.
Launch surfaces now fail closed on unsupported claims
Public launch, pricing, account, roadmap, methodology, email, and fair-value surfaces now share canonical state and commercial terms. Sample fair values and unverified operator data are withheld, while minting and the numeric model remain closed.
Founder launch copy now follows canonical product state
The Founder section no longer promises an expired July 4 opening or a broad discount on every transaction. Price, capacity, credit terms, early access, and availability now follow the canonical product state; the pass remains closed pending review, deployment, and founder approval.
Trait floors now distinguish warming, unavailable, and truly unlisted states. Collection modules disclose live, partial, or planned availability; Trade Value names its selected basis; Explore rejects incomplete value scans; and non-serving fair-value views show receipt-verified evidence only.
Launch verification and rollback controls hardened
Release identity now uses the full source commit, launch checks verify one declared gate state without mutating production, and the operator packet defines exact cutover, rollback, monitoring, and incident evidence steps.
The root route now changes from the intake gate to the full homepage only when the public launch gates open together. View Unlock copy follows that same state, minting remains closed through external review, and expired launch-date and unsupported sample-band claims are removed.
The methodology page now exposes dated grade weights, the four-trait sale waterfall, comparable-evidence coverage tiers, custody digests, and the prospective activation gate. It publishes no median-error claim until contract v3 earns one.
ApeFax now publishes product changes in an append-only ledger with plain-language summaries, rollout status, and an immutable pull request or commit receipt. An RSS feed carries the same verified record.
When model-backed fair value has not passed its evidence gates, ApeFax withholds the number and shows receipt-verified comparable ranges instead. Numeric fair value remains off and certificate minting remains closed.
Terms and product copy now match implemented calibrated ranges, Treasury SDN screening, degraded screening behavior, and the refund path. Counsel review remains scheduled after launch under the recorded waiver.
Same-source holder counts and movement are implemented behind migration 076 and the daily includeHolders rollout. This remains in review until both production steps are applied and verified.
Collection volume, sale windows, tape dates, trait last-sale rows, and premium-floor inputs now read from screened sources and expose honest missing states instead of substituting contaminated data.
Public trending responses no longer include score fields without entitlement. Market discovery remains available while paid report intelligence stays private.
Collections desk gets a fast, leak-safe public shell
The collections desk now serves a fast public shell while paid forensic analysis stays isolated behind its entitlement boundary. Behavioral leak tests cover the split.