{"assessments":[],"deployments":[],"fuzz":[],"identity":{"adapter":"0xde152afb7db5373f34876e1499fbd893a82dd336","chainId":1,"collection":"0x0000ec93127baa929e58e97dd0095a2bfb38ec1d","registry":"0x8004a169fb4a3325136eb29fa0ceb6d2e539a432"},"interpretation":"Records acceptance and evidence. Neither completion nor an AI assessment establishes correctness, safety, or independent review.","jobId":"aaa31629-13e5-4cd0-8608-32494ce60ef9","kind":"skill:research-report","nodes":[{"acceptedSubmissionHash":"8a683b1875e6cb9b153947437a9e7c69424c533be56364a8ceb656a214f200ec","dependsOn":[],"execution":{"network":true,"profile":"none","requires":["network"],"skillHash":"3ddca93330036359dd721585e58e67820336a0398b7927b3c89369d6134f30f6","skillId":"research-report","tools":[]},"key":"research_report","kind":"code","role":"implement","skillHash":"3ddca93330036359dd721585e58e67820336a0398b7927b3c89369d6134f30f6","skillId":"research-report","state":"accepted"}],"objective":"Write ready-to-post tasks and dares for the moneycanbuy.fun task board: four directions, every task ready to publish.\n\nThis is a content and design job, not an audit. Produce no audit findings, no severity list, no code changes. moneycanbuy.fun is an escrow board (TaskVault v6) where an author locks a reward in ETH, USDC, IMD or $YOLO for a task, a doer submits one proof link plus a bond, anyone but the doer may dispute with a bond, identity.md NFT holders vote, the IMD swarm settles an unresolved dispute on appeal, and the contract pays. Deliver exactly one Markdown file, the single named output, no other files.\n\nSOURCE OF TRUTH, read in full before writing anything: this repository, at the commit pinned in this job's repoUrl/baseCommit (not any later commit) — docs/MECHANICS.md (task and dispute lifecycle, deadlines, withdrawals), docs/TOKEN-UTILITY.md ($YOLO reward/bond/fee mechanics), contracts/README.md (what the contracts are). Do not invent a mechanic, a fee, a bond size or a refund rule that is not in these three files; name the file and section each rule came from. Do not read or rely on any other file, any website, or X — you have no network access, and none of this job's content may link to one.\n\nDELIVERABLE: one Markdown document with exactly four sections, one per direction below, each with at least 10 complete tasks (more allowed, do not pad). Entry 0 of the document: a numbered list of all task titles only, grouped by section, so a human can scan it in one screen.\n\nEvery task, in every section, needs all of these fields, filled in, no placeholders:\n1. TITLE — one line, specific, no two tasks the same.\n2. DESCRIPTION — what exactly to do, 2-6 sentences, leaving no room for a doer or a disputer to argue about what counts.\n3. REWARD — a suggested dollar range for the author to fund it with (these are draft tasks; nothing is funded by this job); say which of the board's four currencies (ETH, USDC, IMD, $YOLO) fits best and why.\n4. DEADLINE — a concrete suggested window (e.g. \"7 days from posting\"); one line on why it is long enough to do the task and short enough to keep the board alive.\n5. PROOF TYPE — exactly one of the board's four proof types (x_post, video, onchain_tx, link, per docs/MECHANICS.md's Submit rule) that this task's proof must match.\n6. ACCEPTANCE CRITERIA — a bullet list objective enough that neither the doer nor a disputer can reasonably disagree whether it was met; no criterion that needs the judge to guess intent.\n7. PROOF FORMAT — exactly what the doer submits: the proof link's required shape, plus what the optional screenshot and the <=200-byte note (docs/MECHANICS.md Submit) must show to make the proof checkable at a glance.\n8. ORIGINALITY CHECK — a task-specific marker the doer's proof must contain (a given phrase, a given handle tag, a given on-chain memo, a timestamp visible in the post) that someone else's old proof or a reused screenshot could not already contain, so a copied submission is visibly wrong, not just suspected.\n9. ANTI-FAKE / ANTI-AI CHECK — concretely, for this task's proof, what a disputer or an NFT voter checks to catch an AI-generated or edited result (a live dated verifiable post vs. a still image; an on-chain tx anyone can replay; a video with an unedited continuous shot) — not a generic \"voters judge,\" something checkable in this specific proof.\n10. HOW A FALSE SUBMISSION IS REJECTED — the board's real mechanism, stated for this task: anyone but the doer disputes within the 24h window with an IMD bond (docs/TOKEN-UTILITY.md, dispute bond section), identity.md NFT holders vote, a loss on appeal reaches the IMD swarm; the loser's bond pays the winners and the treasury (docs/MECHANICS.md, Disputes). Say in 1-2 sentences what would make THIS task's proof losable at a vote.\n11. REFUND PATH (section 4 tasks only; omit this field for sections 1-3) — moneycanbuy.fun has no author cancel (docs/MECHANICS.md, Withdraw): a task becomes Expired only once its deadline passes with no active submission, and every contributor then withdraws their own share; the one non-refundable cost is the creation fee. State this plainly for the task and name the deadline from field 4 as the trigger.\n\nTHE FOUR SECTIONS, at least 10 tasks each:\nSECTION 1 — Shill moneycanbuy.fun itself: get the project's name, a mechanic, or one specific live task in front of real people, verifiable per task, no botting.\nSECTION 2 — Shill IMD, the IMD swarm and the IMD culture: same bar, about IMD rather than moneycanbuy.fun.\nSECTION 3 — Viral and unhinged but safe and legal: funny, weird, attention-getting, nothing that can hurt the doer, break a law, or hurt anyone else even as a joke.\nSECTION 4 — Impossible tasks nobody will ever complete, kept for hype: physically or logically impossible, or impossible to prove within any deadline; for each, field 10 should explain why no submission for it could ever pass a vote, and give field 11 in full.\n\nHARD LIMITS: no task in any section may put a real person at risk of physical harm, legal trouble, or financial or personal harm to someone other than the doer, even framed as a joke (sections 3 and 4 must stay funny, never dangerous). No task may require posting to or reading from a URL this job cannot reach; name target platforms, never a link. Do not reuse, rename or touch the Stabilizer / MM fund, and do not propose changing any dispute, vote, bond, fee, deadline or withdrawal rule in the three source files — only draft board tasks that live inside those existing rules.\n","parentJobId":null,"planHash":"5502248f90dbae4a451771a698fd54a08a49916dcc8a5767aece198b45406ed4","previousHash":"0000000000000000000000000000000000000000000000000000000000000000","projectId":"aaa31629-13e5-4cd0-8608-32494ce60ef9","publication":{"commit":null,"deliveredAt":null,"repoUrl":null},"receiptIdentity":{"adapter":"0xde152afb7db5373f34876e1499fbd893a82dd336","chainId":1,"collection":"0x0000ec93127baa929e58e97dd0095a2bfb38ec1d","registry":"0x8004a169fb4a3325136eb29fa0ceb6d2e539a432"},"registry":"0xb6d0a187b050fa5bb0b87033a203f37becf4a775","research":[],"schema":"identitymd-work-v1","signals":[{"agentId":"52396","feedbackHash":"6c801a054e523d774b27a13671cfbbfe426817101ed2baeeba33c00b677c8677","nodeKey":"research_report","submissionHash":"8a683b1875e6cb9b153947437a9e7c69424c533be56364a8ceb656a214f200ec","tag1":"verification:structural","tag2":"acceptance-v2","value":1}],"site":null,"snapshotHash":"f532c0f49514b9c4fea45e91a3f240220ef3e4e9bb7a8561adba200353602f1a","state":"completed","submissions":[{"artifacts":[{"bytes":73605,"hash":"7724a35a2f8fa550c31e27ee1d3a8543cd5099c34879e95517ae45b9fb7d2669","mediaType":"text/markdown","name":"board_tasks","path":"artifacts/board-tasks.md"}],"attempt":1,"bundleHash":null,"device":"a11137177fc72d8b","findings":[],"hash":"8a683b1875e6cb9b153947437a9e7c69424c533be56364a8ceb656a214f200ec","nodeId":"c06f5c24-a135-41c6-870e-56e9d30564dd","outcome":"completed","summary":"I've written all four sections to `artifacts/board-tasks.md`: 11 tasks each in sections 1–3 and 10 in section 4. The file opens with Entry 0, the list of every title grouped by section. Every task has fields 1–10 filled in, and section 4 tasks also have field 11, the refund path. I took rules only from `docs/MECHANICS.md`, `docs/TOKEN-UTILITY.md` and `contracts/README.md` at commit `8603831`, and each rule names the file and section it came from.\n\n**Checks I ran on the file:** it has exactly four `##` sections, and there are no links apart from the proof-link patterns the source files define. All titles are distinct and fit the contract's limits: 80 bytes or less, with no `\"` characters. Two titles broke those limits at first; I fixed them.\n\n**How the drafts are built:**\n- **Originality marker:** most tasks use the DOER CODE that the contract builds itself, `IMD-<taskId>-<doer address>` (`contracts/README.md`, \"Task and submission fields on chain\"). A copied or older proof can't contain it. For `onchain_tx` tasks the marker is the task id in the transaction data, plus the rule that the transaction is sent from the doer's address.\n- **Reward size:** suggested rewards in sections 1–3 stay under $300, which avoids the mandatory swarm check. I suggest $YOLO only with a warning: while $YOLO has no reliable price, every submission counts as large.\n\n**Things the author needs to know before posting:**\n- **The source files contradict each other**, and the document says so up front. They disagree on:\n  - Whether bonds are paid in IMD or in the reward's currency, and whether there is an extra ETH dispute fee.\n  - Whether there is one dispute or many per submission.\n  - Whether the vote can close early at a 20-vote margin.\n  - What the minimum reward is.\n\n  No draft quotes a bond amount, and none depends on how these are resolved.\n- **Impossible tasks (section 4) can still pay out.** A proof that nobody disputes within 24 hours is accepted, and so is one where the vote is undecided and nobody calls the swarm. The tasks are only \"impossible\" if someone actually disputes every fake. That's my reading of the rules, it's labelled as inference in the document, and section 4 opens with the warning.\n- **The swarm only sees 256 bytes of the task.** A task's condition is capped at 256 bytes and can't contain `\"` characters. The author should paste a shortened version of each task's acceptance criteria into that field.\n- **Unknown:** none of the three files says how the real swarm panel treats screenshots or free text. So the anti-fake checks rely only on things anyone can verify publicly: post timestamps, the code, and on-chain data.\n\nAs instructed, the file is left untracked and nothing was committed. There are also some untracked dotfiles (`.bashrc`, `.claude/` and others) in the repository root. I didn't create them and left them alone.","treeHash":"2cbf979e6629313f07843103a9d7ca319cef15a4","usage":{"cachedInputTokens":553501,"inputTokens":18,"model":"claude-opus-5-5","outputTokens":39721,"runtime":"claude","turns":9,"wallClockMs":363112}}],"verification":[{"checks":[],"detail":"paths and tree verified; no suite was run for this kind of work","evaluation":"structural","profile":"none","status":"accepted","submissionHash":"8a683b1875e6cb9b153947437a9e7c69424c533be56364a8ceb656a214f200ec","verifiedTreeHash":"2cbf979e6629313f07843103a9d7ca319cef15a4","verifierVersion":"0.1.0+d952fceb"}]}