$ADAM — official X: https://x.com/IaMaDamIMD — continue the ADAM project from the parent job (single job, do NOT ask clarifying questions — pick sane defaults and document them). Keep everything already built and accepted (plain ERC-20 "ADAM", staking Distributor, hook, Treasury, anti-snipe, 90/10 split). Token name and symbol stay "ADAM". All distributions are pull-based: users claim themselves, nobody pushes tokens.

1. NFT holder claims with daily unlock

• New contract NFTClaim holding 11% of ADAM supply, funded in the deploy script:
  • IMD NFT 0x0000ec93127baa929e58e97dd0095a2bfb38ec1d: 10% of supply (100,000,000 ADAM).
  • Swarm Pepe 0x999ce0ce8c5f7661e0c74a568ffe27ceb9177bdb: 1% of supply (10,000,000 ADAM).
• Per NFT, not per wallet: each tokenId gets an equal share (collection allocation / collection size, read onchain at build, fixed immutably at deploy). The current ownerOf(tokenId) claims its unlocked share; claimed amounts tracked per tokenId. Batch claim for many tokenIds in one tx.
• Unlock: 10 equal daily tranches per tokenId — 10% of its share at launch, +10% every 24h, full after day 9 (= 1% of supply/day for IMD NFTs, 0.1%/day for Swarm Pepe).
• claimAndStake(tokenIds) claims and stakes into the Distributor in one tx; plain claim too.
• burnUnclaimed() after full unlock + 30 days → dead address (covers burned/never-claimed tokenIds).
• No owner withdraw, no parameter changes, reentrancy guard. NFTClaim earns no rewards.

2. Three reward assets, split by the IMD swarm oracle ("buy what's down")

• Reward assets for stakers:
  • $IMD 0xD34a99Bc0f67aE1bbd63C660e6d0b0dd03E263B7 (existing ETH/IMD v4 pool)
  • $PNKSTR 0xc50673edb3a7b94e8cad8a7d4e0cd68864e33edf (existing ETH/PNKSTR v4 pool, 10% hook tax already measured)
  • $IMDSTR 0x80271ce20184e38f4afe90d4ca134304d197aca2 (TokenWorks NFTStrategy proxy, impl 0x7fb856425f164929f023055e8bc40e980b362f61, v4 hook 0x66b05c8eeca9329f7a2332c02ce3855cfab72444; find PoolKey onchain, measure hook tax on fork)
• Holder share (90%) split across the three by a daily signed IMD oracle report (imd.fun/docs/#oracle) from a heartbeat job: imdBps, pnkstrBps, imdstrBps (sum 10000) + short reason. Policy: favor what is down over 24h, unless liquidity/risk signals say otherwise.
• Contract: verify signature + freshness (≤ 26h), clamp each to 1500–7000 bps, missing/stale/invalid → equal thirds. Bounds immutable, owner cannot override. Emit SplitUpdated(imdBps, pnkstrBps, imdstrBps, reportId, reasonHash, source).
• If verifying the IMD oracle report onchain is not feasible, say so and fall back to onchain daily snapshots of the three pool prices with the same rule.
• Deliver the heartbeat job spec/prompt (inputs + output format).
• Keep existing per-leg limits, slippage floors, failure rerouting — extend to three legs.

3. IMDSTR transfer lock

• VERIFIED: IMDSTR wallet→wallet transfer() reverts InvalidTransfer() (0x2f352531); PoolManager is NOT a distributor.
• Implement buy-on-claim: IMDSTR share accrues per staker in ETH; on claim the Distributor swaps that ETH → IMDSTR via its v4 pool with take() directly to the claimer (claimer-supplied slippage).
• Support a one-time switch to direct distribution if the IMDSTR owner whitelists our Distributor via setDistributor.
• Fork test: buy-on-claim delivers IMDSTR to an EOA; direct transfer reverts without whitelist.

4. Keeper bounty

• process() pays the caller 0.5% of the ETH processed in that call (constant max), so bots call it hourly.

5. X / discoverability

• https://x.com/IaMaDamIMD in NatSpec header of every contract (@custom:x), ERC-7572 contractURI() on Distributor/Treasury (token stays plain), README top.

Deliverables

1. Updated Foundry repo + deploy script (11% to NFTClaim; NOT broadcast — deployer signs manually).
2. Unit + fuzz + fork tests for everything above.
3. Short self-audit with fixes applied.
4. Updated README (claim flows, unlock schedule, oracle split, links). Out of scope: website.