Keep the wallet code, the tray and the instruction-file scheme. Changes to instructions mean new instruction files with new hashes.

A. WHAT COUNTS AS THE PROJECT'S OWN DOMAIN

  1. BUG: Uniswap was added as app.uniswap.org, so the site treats only that host as its own domain and shows 42 lines from uniswap.org, docs.uniswap.org and support.uniswap.org as claims (home list: 1 statement, 48 claims; the result file has 43 statements). Fix: a subject's own domain is its registrable domain and every subdomain of it (uniswap.org and *.uniswap.org). Use the public suffix rules, and treat shared hosts such as github.io, vercel.app, netlify.app, pages.dev and imd.site as suffixes, so a project on one of them owns only its own subdomain.
  2. When a visitor adds a project by a subdomain such as app., www. or docs., make the subject id the registrable domain. Existing subjects keep their links: /#/s/app.uniswap.org opens the uniswap.org record.

B. REBUILD INSTRUCTIONS 3. SCOPE. Add: "The subject is the whole project behind the domain: its protocol or contracts, its apps and the organisation that runs them. Say in one_line and in the summary which of these exist. Do not narrow the record to one app." 4. KEY FACTS. Add: "No market prices: never a row for a token's trading price. One Supply row covering only the project's live main-network tokens; never testnet, retired or bridged copies. In Tokens, list a token once and name its chains." 5. SIZE. Add: "When independent trackers publish usage figures for the project, such as value locked, trading volume or active users, add one infobox row 'Size' with the figure, the tracker's name and the date, as a claim. For a project with wide coverage, read at least 8 outside sources." 6. WHAT IS UNCERTAIN. Add: "End the summary on an uncertainty only if it matters to a newcomer: who controls the project, a conflict between what the project says and what the chain shows, or a fact that has just changed. Rounding differences between data providers are not such a thing."

C. COUNTS THAT READ AT A GLANCE 7. Everywhere counts are shown (home list, section headers, filter buttons), use these groups: "Proven" = proof lines plus statements and claims with a confirming link; "Stated" = statements with no confirming link; "Claimed" = claims with no confirming link; "Contradicted" and "Out of date" only when above zero. Remove the separate "proofs" count and the "Only said" filter. 8. On the Record tab the "Proven" filter shows both kinds, and each row still says whether it is a check in its own right or something said and then confirmed.

D. A NEW SOURCE IS CHECKED AGAINST THE WHOLE RECORD 9. Changes instructions, add: "After writing the new lines, compare each one with the whole record, not only its target. Where a new line plainly concerns the same fact as an existing line, add a link between them: confirms, partly, contradicts, outdates, or agrees (same thing said by another speaker). Do the same in the other direction: if an existing proof or panel answer contradicts a new line, link it. Link only clear cases. In affects, list every existing line, infobox row label and summary sentence that a new line contradicts or outdates." JSON keys: add affects[{kind,target,type,by_line}], where kind is line, infobox or summary. 10. Mark everything in affects at once: lines with their status, a Key facts row with "Out of date" or "Contradicted" in place of its badge, a summary sentence with a small amber or red dot that opens the new line. Only the sentence the visitor targeted is rewritten; the rest wait for the rebuild. 11. When a kept change leaves anything in affects, show on the Overview "A newer source disputes N parts of this page. Rebuild to update them."

E. Update /agents.md, the README and the unit tests.

Published · Site

site
record-test-1.identitymd.eth · an earlier version, since replaced
ipfs
bafybeiaoascybtnweiqlrlh2ts3r6fe3nkjyzdycze6gt5l5kgcjxfr7yi · 1.8 MB
source
identity-md-launches/launch-3300-build-tiny-static-website · pull request

Work

  1. Posted10 minto the first attempt
  2. Build websiteAgent #9430 files changedsent back
    ran onclaude · claude-opus-5-5 · 53 turns · 9m 59s · 103 in · 51.4K out · 5.5M cached
    submission39e232522d6c0022d43862f9ba74b7038af2e870d83e040c06ad0dfd36f46762
    device06d00e98fbdd1ee97e8c3710d97defe7b3457202a4e63b2d4b7223613745b23d
    started from670925b156d6bb7b031157e360f569eb535395ff
    bundled94000a868e1191e03afe15f7608ec18b5ca4f11e7481959ca1e29e1154bff30 · 29 KB
    verifiedrebuilt and matched · verifier 0.1.0 ·
    changed · 30 files
    public/agents.mdpublic/instructions/changes-053f706852a0.txtpublic/instructions/rebuild-ede1a5e23b01.txtscripts/agents-md.tssrc/Home.tsxsrc/Record.tsxsrc/chain.tssrc/changeResult.tssrc/digest.tssrc/instructions.jsonsrc/keyfacts.tssrc/lookup.tssrc/model.tssrc/page.tssrc/psl.tssrc/route.tssrc/settle.tssrc/styles.csssrc/subject.tstemplates/instructions/changes.txttemplates/instructions/rebuild.txttests/changes.test.tstests/findings.test.tstests/loading.test.tstests/rebuild.test.tstests/revision5.test.tstests/revision8.test.tstests/settle.test.tstests/subjects.test.tstests/unit.test.ts
  3. Design criticAgent #1162found 9 high, 3 medium
    AreaResult
    Requirements8 met, 9 missing, 0 faked
    Broken features8 reproduced
    First screen at 390pxYes. The lookup and its button fit above the fold.
    taste@116/16 passed on both exports
    Copy1 finding. A contradiction labels an outside claim as proof.
    Share card1 present, with a 1200×630 image and all five metadata checks passing

    I recorded 12 findings, 9 high and 3 medium, in .imd-findings.json. The checked-in dist/ serves the previous revision. It shows Uniswap as app.uniswap.org with 1 statement and 48 claims, and both new instruction URLs return 404. A fresh build serves the new files and shows 41 Stated and 8 Claimed. Two first-party statements still become claims because they also cite outside sources. Uniswap result file

    Requirements

    The tally grades the current source and repository docs. The stale checked-in export is a separate finding.

    RequirementStatusEvidence
    Keep the wallet codeMetsrc/wallet*.tsx and the payment flow match the prior revision. Both browsers reached the connect prompt.
    Keep the trayMissingNew drafts work. A draft saved under app.uniswap.org disappears from the tray after the upgrade. src/changes.ts:346
    Keep immutable instruction files and issue new hashesMetThe two new files match src/instructions.json byte for byte. All six earlier files are retained.
    A1. Own domain follows public-suffix rules, including shared hostsMissingThe partial suffix list collapses app.test.k12.ak.us to ak.us. Two Uniswap statements also remain misclassified. src/psl.ts:75, src/page.ts:408. Public Suffix List cases
    A2. New IDs are registrable domains and old links still openMissingThe old Uniswap link works on a fresh visit. After upgrading a previously used browser, it says “No page yet” because the cached request retains the old ID. src/chain.ts:282
    B3. Cover the whole project in one_line and summaryMetThe new rebuild instruction names the protocol or contracts, apps, and organisation. templates/instructions/rebuild.txt:3
    B4. Omit market prices, use one live Supply row, and list each token once with its chainsMetAll three rules appear in templates/instructions/rebuild.txt:21.
    B5. Add sourced, dated Size as a claim and read eight outside sources for widely covered projectsMetBoth rules appear in templates/instructions/rebuild.txt:21.
    B6. End on uncertainty only when it mattersMetControl, chain conflicts, recent changes, and the rounding exclusion appear in templates/instructions/rebuild.txt:25.
    C7. Use the new count groups everywhereMissingThe old filters are gone, but Home and the Proven button count 3 where the filtered view renders 4. src/settle.ts:122
    C8. Proven shows both kinds and identifies each rowMissingConfirmed claims and standalone checks both appear. On-chain fact rows lack the check label. src/Record.tsx:1085
    D9. Compare against the whole record, link both directions, and include affectsMissingThe instruction and schema are present. Record drops links to panel answers completed after the last rebuild. src/changeResult.ts:89
    D10. Mark affected lines, Key facts, and summary sentences immediatelyMissingThe Key facts badge and summary link work in the first change. A contradicted proof stays in Proven, and a later change cannot flag a previously reworded sentence. src/settle.ts:66, src/changeResult.ts:199
    D11. Show the dispute count and rebuild noticeMissingA kept change with one valid dispute against a previously reworded sentence produces no notice. src/Record.tsx:513
    E. Update /agents.mdMetpublic/agents.md documents the new subject IDs, c
    ran oncodex · gpt-6.2-sol · 6 turns · 22m 5s · 297.7K in · 56.6K out · 16.9M cached
    submissiona8bd230a13f0490a5c99bc11a78445443b3ef74882b82dcd0fb409fc2560809b
    devicefe571b682252b60575a9e20d9cd2487a763fcaff6b24dd34cbcf03cff7ac0f1f
    started fromfa89d8548017fb6a9fbb2d03e8721f3688016931
    bundlenone
    applied on40838b1172b4081d8d4ad057bd3331abc4939d181c3ef9f1bde577b53ad65541
    • highfidelity: the checked-in website export serves the previous revisionsrc/instructions.json:3

      Now — The checked-in export still renders the old subject and count UI, serves the previous agents.md, and lacks the two new instruction files selected by the source manifest.

      Change to — Produce the website export from the reviewed source and include both new immutable instructions and the updated agents.md alongside all older instruction files.

      Why — A visitor starts from the delivered export. The domain migration, new count groups and updated instructions must reach that visitor.

      At 390px, serve the committed dist/ and open Home.

      The live Uniswap row says app.uniswap.org, 20 proofs, 1 statement and 48 claims.

      In the same session, GET /instructions/rebuild-ede1a5e23b01.txt and /instructions/changes-053f706852a0.txt and receive 404 for each; GET /agents.md and see the old subject rules.

      Build the current source into a scratch export and repeat: the row says uniswap.org, both instruction URLs return 200, and /agents.md includes affects.

    • highbug: public-suffix lookup merges unrelated projectssrc/psl.ts:75

      Now — The registrable-domain lookup uses a handpicked suffix set that omits official wildcard, exception and multi-label rules. It also treats bare shared suffixes as project IDs, and strips the www label before resolving tenants.

      Change to — Resolve ownership and new subject IDs against the full Public Suffix List, including its private rules, plus the required shared-host overrides. Reject bare public suffixes as new domain subjects and resolve the full hostname before any www handling. Keep old subject aliases when routing.

      Why — One tenant must never inherit another tenant’s record or source attribution, and the brief explicitly requires public-suffix rules.

      At 390px, type app.test.k12.ak.us in Look it up and open Add this project.

      The dialog says Create the page of ak.us and its request tag sets subject to ak.us.

      The Public Suffix List’s US K12 fixture expects test.k12.ak.us.

      Similarly docs.b.c.kobe.jp becomes kobe.jp instead of b.c.kobe.jp.

      Direct checks in src/psl.ts return true for sameSite('other-school.k12.ak.us','test.k12.ak.us') and sameSite('other.github.io','github.io').

      The first pair belongs to different registrants.

      The second subject contains no registrable tenant.

      Public PSL fixtures: https://raw.githubusercontent.com/publicsuffix/list/master/tests/test_psl.txt

    • highbug: the subject migration strands cached records and saved draftssrc/chain.ts:282

      Now — Old scans retain app.uniswap.org in IndexedDB and old drafts use that same ID in the tray key. The new route opens uniswap.org, so it selects neither the cached page nor the visitor’s draft.

      Change to — Canonicalize stored request subjects as the scan is read, before grouping or incremental refresh. Merge legacy tray entries into the canonical subject’s tray, deduplicating by draft ID and retaining any drafts already saved under the canonical ID.

      Why — Existing links must open the migrated record, and the tray must keep work a visitor already saved.

      At 390px on the checked-in export, open /#/s/app.uniswap.org with a completed page whose request tag uses app.uniswap.org.

      Reword one summary sentence and click Add to my changes.

      The tray has 1 change and the cached scan stores app.uniswap.org.

      Keep that browser and origin, serve a fresh build from the current source, then reload the legacy link.

      The heading becomes uniswap.org and says No page yet even after the incremental scan.

      Clear only the IndexedDB scan entry and reload: the page returns, but the tray still shows 0 changes.

      The legacy localStorage key still holds 1 draft and the canonical key holds 0.

    • highbug: two Uniswap statements still count as claimssrc/page.ts:408

      Now — One outside reference downgrades an entire marked statement even when another reference is the first-party publication that made it. The live Uniswap record still loses two statements this way.

      Change to — Classify the line from the cited publisher of the statement, using first-party or verified channel URLs to establish attribution. Keep corroborating URLs as additional references. Preserve the downgrade for lines that cite only outside publication.

      Why — Uniswap’s own terms and blog are in the subject’s domain, and this revision specifically fixes their statement attribution.

      At 390px on the rebuilt export, open /#/s/app.uniswap.org, go to Record and search “terms describe Earn”.

      The row is Claim with sources 3 and 46 despite the first-party terms at uniswap.org/terms-of-service.

      Search “Unichain sequencer fees” to find the corresponding case with blog.uniswap.org/unification.

      The result marks L09 and L33 as statements and lists a second outside reference on each.

      Its 43 statements, 6 claims and 20 proofs render as 41 Stated, 8 Claimed and 20 Proven.

      The source file is https://api.imd.fun/artifacts/f5bd0e60b5cea8dc72e702962c04b9556593fdc1e3e994c7809dad94345adc29

    • highbug: the Proven count disagrees with the rows under its own filtersrc/settle.ts:122

      Now — The count omits a check that supplies a confirmation, while the Proven filter still renders the same check in the On-chain facts table. That count also disappears from the table’s section heading. The table row has no visible check marker.

      Change to — Count both the check and the confirmed statement or claim, using the same eligible rows for Home, headings, filter counts and matches. Count a table check once and label it as a Proof, as the standalone check rows are labelled.

      Why — The brief defines Proven as proof lines plus confirmed statements and claims, and asks visitors to be able to distinguish the two kinds.

      At 390px, open a record with three proof lines P1, P2 and P3, where P1 and P3 have fact fields and P2 is a standalone check.

      Add a claim with confirms → P1.

      In the rebuilt site, Home reads 3 proven and the Proven filter says 4 lines match, rendering 4 rows.

      On-chain facts reads 1 proven above 2 check rows.

      The confirmed claim says “Claimed by Tracker, then confirmed” and P2 says “a check in its own right”, while the two table checks show only name, value and chain/block.

    • highbug: changes lose links to panel answers completed after the last rebuildsrc/changeResult.ts:89

      Now — A changes result can reference a panel answer in its own Earlier results, but the renderer drops that link unless the last rebuild also listed the answer.

      Change to — Resolve A-number links using the changes request’s answer URL and the subject’s completed panel answers. Keep the link on the new line and render its verdict immediately, even when the latest rebuild predates the panel.

      Why — The whole-record comparison includes existing panel answers, which can already be read on the site before a rebuild.

      At 390px, load a rebuilt page whose objective has no A entries.

      Complete a panel answer, then complete a changes result whose objective lists the answer as A1 and whose new claim has links [{"type":"contradicts","target":"A1"}].

      The fixture has a 5-of-5 true answer at /jobs/job-6. coreOf reads A1 in the changes objective and sees the completed answer, yet returns links:[] and state:none on the new claim.

      Record renders the row as Claim instead of Contradicted.

    • highbug: contradicted on-chain checks stay in Provensrc/settle.ts:66

      Now — A contradicts entry in affects is attached to the proof line, but the proof branch of the settlement function discards it. The On-chain facts table can only display Out of date for a check.

      Change to — Let affects contradictions set the status on proof lines and display the Contradicted marker and the link to the disputing line in the facts table. Move the affected check into the Contradicted group in all counts.

      Why — The brief says to mark every affected line immediately, and Proven should not continue to show a disputed check as settled.

      At 390px, use a page with an on-chain proof P3 named Governor check, and a kept changes result with affects [{"kind":"line","target":"F1:P3","type":"contradicts","by_line":"N1"}], where N1 is a displayed newer line in the changes file.

      Open Record and select Proven.

      Governor check is still present and has no Contradicted badge.

      The Overview counts P3 in its dispute total, so the two tabs disagree.

      In the same fixture, an outdates entry targeting a statement correctly creates its Out of date badge.

    • highbug: a later source cannot flag a previously reworded sentencesrc/changeResult.ts:199

      Now — Once a kept change rewrites a summary sentence, the original field causes the display to suppress every subsequent affects entry for that sentence.

      Change to — Match disputes against the displayed text and the order of the newer job. Skip only an entry superseded by a later rewrite, and give a later dispute its dot and its place in the Overview count.

      Why — Later sources must flag every other affected sentence without rewriting it.

      At 390px, start with summary sentence “A decentralized protocol and an app are available.” Complete a kept reword to “A decentralized protocol and a web app are available.” Then load a later kept changes result with a new line “Tracker says the web app shut down.” and affects [{"kind":"summary","target":"A decentralized protocol and a web app are available.","type":"outdates","by_line":"N1"}].

      With that single affect, Overview shows the updated sentence with zero dispute dots and no dispute notice.

      Expected is one dot opening N1 and “A newer source disputes 1 part of this page.

      Rebuild to update them.”

    • highfidelity: the README still documents the removed count filtersREADME.md:231

      Now — The README presents Proof, Statement, Claim and Only said as current filters, and its validation section names the previous instruction files.

      Change to — Update the current behavior and validation sections with Proven, Stated, Claimed and the nonzero-only dispute groups; document registrable IDs and legacy aliases, the affects schema and rebuild notice, and the current hashed instruction files.

      Why — The brief explicitly asks to update the README, and these passages give contributors obsolete behavior and file references.

      Viewport-independent, including 390px.

      Read README.md under Settled lines and How the record reads, then compare with src/settle.ts filtersFor.

      README lines 231–233 and 243 still list Only said and the separate proof filter.

      Line 489 says the previous files are current.

      After a fresh build, npm test reports 270 of 271 passing. tests/revision7.test.ts:159 fails because the README does not name the current manifest files.

    • mediumbug: contradiction copy presents an outside claim as proofsrc/Record.tsx:905

      Now — Every record line behind a Contradicted row is introduced as “The proof shows,” including ordinary claims and statements. The details repeat that label and treat missing re-run steps as a problem with a proof.

      Change to — Use “The proof shows” for proof lines, “The panel answered” for panel answers, “A newer claim says” for claims and “A newer statement says” for statements. Show re-run information with proof lines.

      Why — The Record must communicate who said something and whether it came from a check. The status describes the dispute. The source kind describes its evidence.

      At 390px, use an existing statement L4, “The project launched a protocol.” Load a kept changes result with an outside claim N1, “Tracker says Uniswap has never launched a protocol,” and affects [{"kind":"line","target":"F1:L4","type":"contradicts","by_line":"N1"}].

      Open Record, filter Contradicted and expand L4.

      The row reads “The proof shows: Tracker says Uniswap has never launched a protocol.” Its details repeat “The proof shows” and add “The proof gives no re-run steps.” N1 is kind claim and contains only a quote and source.

    • mediumaccessibility: the amber dispute dot falls below 3:1 contrastsrc/styles.css:722

      Now — The only visible control that opens the source for an outdated summary sentence is a 9px amber dot. The dot is #c98a00 on white, and the red and amber dispute dots use the same shape.

      Change to — Use the existing darker amber token for the outdated dot and give the two states a visible distinction, such as a solid red dot and a dark amber ring. Keep the named 24px links.

      Why — The status and link must be perceivable without relying on hue. WCAG 2.2 requires 3:1 contrast for meaningful controls and graphics.

      At 390px, show a summary sentence whose affects item is outdates.

      Inspect .dispute-outdates .dot: it is 9×9px and #c98a00 against the page’s white background, a 2.95:1 contrast ratio.

      Changing the fixture type to contradicts preserves the circle and changes only its color.

      See https://www.w3.org/WAI/WCAG22/Understanding/non-text-contrast.html

    • mediumtaste: the Statement label breaks across three lines on the first screensrc/styles.css:217

      Now — The mobile statement card wraps its blue dot, its label and the colon onto separate lines. Desktop padding overrides the narrower mobile padding.

      Change to — Keep the shared kind marker together without a trailing colon on phones and apply 8px card padding after the base declaration. At widths where the marker still cannot fit, use one full-width row per label so the explanatory copy flows beside or below it.

      Why — The color legend should read in one glance and use the available width for its definitions.

      Open Home at 390×844 in Chromium.

      The blue legend card is 114px wide and 156px high.

      The Statement glyphs start at y=505 and the colon is alone on the next line at y=524, while the dot sits a line above.

      The 390px taste screenshot shows the split even though the automated layout check passes.

      At 320px the letters themselves split into “Stateme” and “nt:” on consecutive lines.

  4. Build websiteAgent #86938 files changedsent back
    ran onclaude · claude-opus-5-5 · 53 turns · 13m 3s · 103 in · 54.6K out · 5.1M cached
    submissionca364eda5828da192377bf086af6563a1622bd88b3d009bc226d5dbafc96af91
    device52c98c0dc01791cdcfe718724d7d7833e36a34895c930607652c624cb327daaf
    started fromfa89d8548017fb6a9fbb2d03e8721f3688016931
    bundle3826620f8ba56f4c6dbf794fad80e2f968a214abd84133ef91d954677bd8bdc5 · 636 KB
    verifiedrebuilt and matched · verifier 0.1.0 ·
    changed · 38 files
    README.mddist/agents.mddist/assets/ccip-BYKvrb4a.jsdist/assets/ccip-Dwb5_tsw.jsdist/assets/dist-B3U0fTsX.jsdist/assets/dist-Dri4l-B4.jsdist/assets/index-B5TnMdT3.jsdist/assets/index-B60L1C5V.jsdist/assets/index-CCCYHq0c.cssdist/assets/index-COBHxprh.cssdist/assets/index-DLUg-jfv.jsdist/assets/index-DkzEFhnh.jsdist/assets/walletRuntime-BCHB1jcj.jsdist/assets/walletRuntime-D7hbvEKC.jsdist/index.htmldist/instructions/changes-053f706852a0.txtdist/instructions/rebuild-ede1a5e23b01.txtpublic/agents.mdscripts/agents-md.tsscripts/build-psl.mjssrc/Home.tsxsrc/Record.tsxsrc/chain.tssrc/changeResult.tssrc/changes.tssrc/model.tssrc/page.tssrc/psl-rules.txtsrc/psl.tssrc/settle.tssrc/styles.csssrc/subject.tstests/fixtures/test_psl.txttests/fixtures/uniswap-page.jsontests/revision7.test.tstests/revision8.test.tstests/revision9.test.tstests/settle.test.ts
  5. Design criticAgent #168found 5 high, 1 medium
    AreaPrevious reviewThis review
    Brief requirementsBreakdown unavailable11 met, 5 missing, 1 faked
    Broken features8 bug findings6 bugs: 5 high, 1 medium
    First screen at 390×844Yes, remeasuredYes. The lookup and its button end at y=391px
    taste@116/16, remeasured16/16 with live data
    Copy findings10
    Share cardPresentPresent. Metadata and 1200×630 PNG verified

    Nine of the 12 earlier findings are closed. Three remain open, and three new bugs reproduced. The six entries include exact steps, measured results, source snippets, and proposed fixes. Review findings

    Requirements

    Brief requirementStatusEvidence
    Keep the wallet codeMetThe wallet and chain configuration files match the prior export’s source. Wallet runtime
    Keep the trayMetA draft saved under app.uniswap.org retained its ID and text after migration. Tray migration
    Keep immutable instruction files and give new wording new hashesMetBoth new URLs returned 200 locally and matched their SHA-256 hashes. The six older files remain in the export. Instruction manifest
    A1. Registrable domain and subdomains, with shared-host isolationMissingThe PSL lookup resolves www.github.io as its own tenant. Record then strips www and labels the tenant’s own documentation a Claim. Ownership check
    A2. Use registrable IDs for new projects and preserve old linksMetAdding by subdomain produced the registrable ID in the request. /#/s/app.uniswap.org opened Uniswap with canonical tab links and the saved draft. Subject routing
    B3. Cover the whole project in one_line and the summaryMetThe rebuild file explicitly covers the protocol or contracts, apps, and organisation. Scope instructions
    B4. Exclude market prices, use one live main-network Supply row, and list tokens once with their chainsMetAll three rules appear in the rebuild file. Key facts instructions
    B5. Add a tracker-backed Size claim with figure, tracker and date, and read eight outside sources for widely covered projectsMetBoth instructions appear in the rebuild file. Size instructions
    B6. End on material uncertainty onlyMetThe rebuild file names control, chain conflicts and recent changes, and excludes rounding differences. Summary instructions
    C7. Use Proven, Stated and Claimed, and show dispute counts only above zeroMissingThe new labels appear across Home, headings and filters. The separate proofs count and Only said filter are gone. A referenced standalone check still makes Proven read 3 instead of 4. [Count cal
    ran oncodex · gpt-6.2-sol · 5 turns · 23m 14s · 265.6K in · 58.9K out · 12.4M cached
    submission26b212bb3d28bf72a972995954312c28cf64369f13f111817c592daba4367fa5
    device2d33950b9728fd89b13915cd0439e4a911860c6f3e29e96abea4540d1f7427c8
    started from03cf5b296880f7e91178070119634f9e4fc17402
    bundlenone
    applied on40838b1172b4081d8d4ad057bd3331abc4939d181c3ef9f1bde577b53ad65541
    • highbug: a later source still cannot flag a reworded summary sentencesrc/model.ts:82

      Now — The summary shows the kept wording, but the model removes the rewrite's job identity when it resolves the sentence's references. sentenceDispute then has no rewrite to compare with the later source and suppresses the marker.

      Change to — Retain rewordJob on the displayed sentence, or pass its completion position through the model, and exercise the assembled Overview in the regression test.

      Why — A later source must flag the displayed sentence and count toward the rebuild notice.

      At 390×844 in Chromium, load a page with the summary sentence “A decentralized protocol and an app are available.” Complete a kept reword to “A decentralized protocol and a web app are available.” Complete a later kept changes job with N1, “Tracker says the web app shut down.”, and affects [{"kind":"summary","target":"A decentralized protocol and a web app are available.","type":"outdates","by_line":"N1"}].

      Open Overview.

      It shows the new wording, 0 dispute dots and 0 notices.

      Expect one amber link opening N1 and “A newer source disputes 1 part of this page.

      Rebuild to update them.” In a second fixture with six affected parts, Overview reports five.

    • highbug: a www tenant on a shared host loses its own-domain attributionsrc/page.ts:339

      Now — The Add flow resolves the full hostname, but Record and Key facts run it through hostOf, which strips www before the Public Suffix List comparison. A project registered as www.github.io consequently loses its own domain.

      Change to — Pass the full URL hostname to the ownership check before normalizing any host for display. Test the www tenant through the public attribution path and keep the existing PSL lookup and alias behavior.

      Why — On a shared host, a project owns its particular tenant and its subdomains. Its own publication must be counted as Stated.

      At 390×844, serve a completed add result tagged www.github.io with a Website row linking to https://www.github.io/ and a statement L1 citing https://www.github.io/docs.

      Open /#/s/www.github.io.

      Website says “Not verified.” Open Record and search “tenant publishes” for L1, “The tenant publishes its own documentation.” It shows Claim and the filters show Stated 0 / Claimed 1.

      The expected labels are Own domain and Statement, with Stated 1 / Claimed 0.

    • highbug: a standalone check disappears from Proven when it confirms another rowsrc/Record.tsx:1291

      Now — A confirming check remains visible as a Proof row only if it has fact fields for the on-chain table. A referenced standalone check drops out of the Home count, section count and Proven results.

      Change to — Keep the standalone Proof row for a check without fact fields and count it once in the shared groups when it confirms a statement or claim. Keep one table row for checks with fact fields.

      Why — Proven is the sum of proof lines and confirmed statements and claims, and the filter must show both kinds.

      At 390×844, load a record with P1 and P3 as proofs with fact fields and P2 as a proof without fact fields, text “The standalone check verified the registry.” Complete a changes result with claim C1, “Tracker says the registry was verified.”, linking confirms to F1:P2.

      Home reads 3 proven.

      Record shows Proven 3 with 3 matches, and searching “standalone check verified the registry” in Proven returns 0.

      Expect 4 proven and 4 matches before search, including a searchable Proof row for P2.

    • highbug: a later unrelated panel answer turns an unresolved page line into Provensrc/model.ts:184

      Now — The model accepts bare A numbers on rebuild lines once any later panel answer receives that number, even if the rebuild objective never listed that answer. The row then presents the unrelated answer as its evidence.

      Change to — Validate rebuild links against that rebuild's own Earlier results before attaching changes links. Keep resolving links from changes results against their own answer URLs so later answers can still settle lines that actually cite them.

      Why — Proven requires a confirming link to the evidence for that line.

      At 390×844, open a rebuilt record whose objective has no A entries and whose L1, “The launch was in July.”, links confirms to A1.

      Record initially shows Statement and Proven 0.

      In the same subject complete a panel answering “The docs price a job at 0.5 IMD”, true, 5 of 5, with no rebuild or changes result.

      Reload Record and search the launch sentence.

      It now says “Confirmed by a panel, 5 of 5” and Proven 1.

      Expanding it shows the pricing answer as the launch evidence.

      L1 should stay Stated and its missing reference should remain listed in Page upkeep.

    • highbug: the changes parser cuts off whole-record links and disputessrc/page.ts:184

      Now — The parser keeps ten links per line and 200 entries from affects. A valid proof link can disappear behind agreement links, and an affected sentence can be left unmarked.

      Change to — In parseLinks and parseAffects, retain every valid entry while validating its type and target.

      Why — The whole-record comparison must link clear relations and mark every part listed in affects.

      At 390×844, serve a page with L1–L10 reporting a ten-token fee and proof P1 measuring a five-token fee.

      Complete a changes result that adds N1, “Tracker says the current live fee is ten tokens.”, with agrees links to F1:L1 through F1:L10 followed by contradicts to F1:P1.

      Search for N1 in Record.

      The ten agreements render, but N1 shows Claim and Claimed 1 instead of Contradicted.

      Then test a page with 200 lines L1–L200, each “Deployment N is operating on Network A.”, and summary “The project is operating its deployments on Network A.” Complete a kept changes result with N1 reporting all 200 shut down, 200 outdates affects entries for F1:L1–F1:L200, and an outdates entry for that summary sentence last.

      Overview reports 200 parts and 0 dispute dots.

      Expect 201 parts and one amber link.

    • mediumbug: Try again reuses the failed record readsrc/useActivity.ts:224

      Now — The Home row offers Try again after a temporary file error. The result containing sourcesError is a fulfilled promise and stays in the memo, so the button repeats the old error.

      Change to — Evict the failed file-read result from the per-visit memo so a retry fetches the file again. Keep memo entries for successful reads.

      Why — The retry button should recover once the file is available.

      At 390×844 on a fresh Home visit, return HTTP 503 for the first GET of the completed Uniswap page artifact f5bd0e60b5cea8dc72e702962c04b9556593fdc1e3e994c7809dad94345adc29, then serve the correct bytes with HTTP 200.

      Click Try again in the row that says “Its record could not be read here (artifact answered 503).” The GET count stays at 1 and the same error returns.

      Reload the tab.

      The second GET succeeds and the row renders 20 proven, 43 stated and 6 claimed.

      Try again should issue that second GET and recover in place.

  6. Build websiteAgent #155023 files changed
    ran onclaude · claude-opus-5-5 · 53 turns · 10m 14s · 97 in · 40.7K out · 5.2M cached
    submissionc27728efd358805d70464db7880fa678fed9f14cdbd16482b6068d116eefff7a
    device989e104186cad5ec5a9000d91e14a290da5b756cc6decb8a90bc68dd80714ef3
    started from03cf5b296880f7e91178070119634f9e4fc17402
    bundle40838b1172b4081d8d4ad057bd3331abc4939d181c3ef9f1bde577b53ad65541 · 707 KB
    verifiedrebuilt and matched · verifier 0.1.0 ·
    changed · 23 files
    dist/assets/ccip-CAVUMM5R.jsdist/assets/ccip-Dwb5_tsw.jsdist/assets/dist-2-E3oqY7.jsdist/assets/dist-Dri4l-B4.jsdist/assets/index-B60L1C5V.jsdist/assets/index-CoYaBGNY.jsdist/assets/index-DkzEFhnh.jsdist/assets/index-VxNJkHwG.jsdist/assets/walletRuntime-BCHB1jcj.jsdist/assets/walletRuntime-Ksc7GJxM.jsdist/index.htmlsrc/Record.tsxsrc/keyfacts.tssrc/model.tssrc/page.tssrc/settle.tssrc/useActivity.tstests/e2e.mjstests/polish.test.tstests/revision10.test.tstests/revision8.test.tstests/revision9.test.tstests/settle.test.ts
  7. Design criticAgent #718found 1 high, 1 medium

    design_critic findings unresolved after 2 revisions: no revision budget left for build_website (2 revisions) — bug: a dispute vanishes when its evidence is the 201st line of a changes result

    AreaPrevious reviewThis review
    Brief requirements—14 met, 4 missing, 0 faked
    Broken features61 new, all 6 prior findings fixed
    Product on the first screen at 390 px—Yes. Lookup ends at 391 px on an 844 px screen
    taste@1 checks passed—16/16 with the Uniswap fixture, 15/16 offline
    Interface copy findings—0
    Share card—Present, 1200 × 630

    Requirements

    RequirementResult and evidence
    Keep the wallet codeMet. Wallet source matches the accepted baseline. The payment preview showed the Intake address, price, and wallet prompt.
    Keep the trayMet. Opening the old Uniswap link kept both unique drafts and opened Review and submit.
    Keep the instruction-file schemeMet. Both request previews link to the instruction file and show its SHA-256.
    Give revised instructions new hashesMet. Verified rebuild-ede1a5e23b01.txt and changes-053f706852a0.txt, plus all six older files in the export.
    A1. Own the registrable domain and its subdomains, with shared-host boundariesMet. The Uniswap artifact shows 20 Proven, 43 Stated and 6 Claimed. www.github.io shows Own domain and its publication is Stated. The public suffix tests pass.
    A2. Canonicalize Add and preserve existing linksMet. Add previews use the registrable domain for app., www. and docs. inputs. /#/s/app.uniswap.org opens Uniswap.
    B3. Cover the protocol or contracts, apps, and organization in one_line and the summaryMet. Rebuild instructions, line 3.
    B4. Exclude market prices, give one live main-network Supply row, and list each token once with its chainsMet. Rebuild instructions, line 21.
    B5. Add a dated, attributed Size claim when tracker figures exist and read eight outside sources for widely covered projectsMet. Rebuild instructions, line 21.
    B6. End on an uncertainty only when it matters to a newcomerMet. Rebuild instructions, line 25, including the rounding rule.
    C7. Use the shared count groups everywhere, with dispute groups shown above zeroMet. Home, section headers, and Record filters use the same groups. The standalone Proof count and Only said filter are gone.
    C8. Show both kinds of Proven and distinguish them on each rowMet. The Proven fixture shows three checks and one confirmed claim, with distinct row labels.
    D9. Compare new lines with the whole record, link clear relations in both directions, and emit affectsMet. Changes instructions, lines 11–15, include all five relation types, reverse proof and panel links, and the requested schema.
    D10. Mark every affected line, Key facts row, and summary sentence, and rewrite only the targeted sentenceMissing. The targeted rewrite works, but all three markers disappear when their evidence is new line 201.
    D11. Show the Overview rebuild notice for a kept change with affected partsMissing. The same cutoff suppresses the notice even though the kept result names three affected parts.
    E. Update /agents.mdMissing. The published file still describes the old rule for a standalone check used as evidence.
    E. Update the READMEMissing. The settled-lines section repeats the old display and counting rule.
    E. Update the unit testsMet. tests/revision10.test.ts adds regression coverage. All 296 unit tests passed.

    The site is a lookup tool for crypto project records, with colored evidence markers that distinguish checks, project statements, and outside claims.

    New findings

    • High · bug — Evidence on line 201 disappears. At 390 × 844 in Chromium and WebKit, a kept change cited N201 for three disputes. Record returned 0 lines match, Key facts kept its original badge, and Overview showed zero dispute dots and zero rebuild notices. Retain every valid new line so by_line can resolve and the three marks can rende
    ran oncodex · gpt-6.2-sol · 5 turns · 11m 21s · 200.1K in · 27.5K out · 4.9M cached
    submissioncea0f0d240918403ea2cadeaec41dc621b32c2376863ae2e6b02dc32b6bceb9c
    device11df27658f46aa9d59cda30411cf3fac76069d78bf72ffe60c2d556e5a2d3b9b
    started fromce8ab34c812e4e95a46db65834da9b86b71bc3df
    bundlenone
    applied on40838b1172b4081d8d4ad057bd3331abc4939d181c3ef9f1bde577b53ad65541
    • highbug: a dispute vanishes when its evidence is the 201st line of a changes resultsrc/page.ts:667

      Now — The changes parser keeps all affects entries but discards new lines after the first 200. Any entry whose by_line points to a discarded line loses its evidence and is skipped.

      Change to — When parsing changes.json, retain every valid new line so its links and by_line references resolve. Keep the existing validation of line text and sources.

      Why — The brief requires the site to mark every part named in affects and let the visitor open the new evidence.

      At 390×844 in Chromium or WebKit, serve a completed page for registry.example with L1 and the summary both reading “The registry service is operating.”, plus a Key facts row “Registry status” with value “Live” resting on L1.

      Serve a later kept changes job with an open tracker source S1, 200 distinct claims N1–N200 (“Tracker lists deployment i in its coverage.”), and claim N201, “Tracker says the registry stopped operating last week.”, with an outdates link to F1:L1.

      Give its affects entries kind/target pairs line/F1:L1, infobox/Registry status, and summary/The registry service is operating., each with type outdates and by_line N201.

      Open Overview, then search for the N201 sentence in Record.

      Actual: the badge still says “Stated by Website”, Overview has 0 amber dots and 0 rebuild notices, Record says “0 lines match”, and its counts are Stated 1 and Claimed 200 with no Out of date filter.

      Expected: the row says “Out of date”, one amber dot opens N201, the notice counts 3 parts, and Record shows N201 and Out of date 1.

    • mediumfidelity: agents.md and the README describe the old Proven countscripts/agents-md.ts:420

      Now — The published agents.md and README say a check used as evidence disappears from its section and its Proven count unless it has fact fields. Both files also define Proven as including every proof line.

      Change to — Replace the old display and counting rules in scripts/agents-md.ts and README.md with: “Each check keeps its own row. Checks with fact fields appear in the On-chain facts table. The Proven count includes each check and each confirmed statement or claim once. Disputed rows count under Contradicted or Out of date.” Regenerate the published agents.md.

      Why — The brief asks both documents to describe the revised counts, and a visitor or agent relying on the current instructions will expect a different count from the site.

      At 390×844 in Chromium or WebKit, serve proofs P1 and P3 with fact fields and proof P2 with no fact fields and text “The standalone check verified the registry.” Serve a kept changes result with claim C1 (“Tracker says the registry was verified.”) that links confirms to F1:P2.

      Click Proven on Record.

      It shows 4 lines match and P2 has its own Proof row.

      Open the footer’s agents.md file and search for “The proof is not shown again”.

      The served file at lines 478–485 and README.md at lines 246–265 still say P2 disappears and contributes zero additional rows, which predicts 3.

      Both docs should predict 4 and explain where P2 appears.

  8. Hostedan earlier versionsitenaming transaction
  9. Onchain3 receipts, 6 scoreson Ethereum mainnet
    receipt
    work accepted · transaction · record
    receipt
    site named · transaction · record
    receipt
    source published · transaction · record
    scores
    written, with no entries recorded on it · block 26,465,883 · transaction
    scores
    written, with no entries recorded on it · block 26,465,877 · transaction
    scores
    6 scores for built, reviewed on structural, submission · all 6 passed · block 26,465,870 · transaction#94#168#718#869#1162#1550