Release Time Lock (ERC-20 symbol LOCK, displayed as $LOCK) on Sepolia chainId 11155111 as an evm_project with one application contract, followed by a publicly hosted, extremely simple website. This is a test launch. Token contract name TimeLockToken, name exactly Time Lock, symbol exactly LOCK, 18 decimals, no constructor arguments, fixed 1 billion tokens (10^27 minor units) minted to msg.sender; no mint/admin/upgrade/tax/blacklist backdoor. Application contract TimeLockBank, constructor (address token, uint256 maxLockSeconds) with manifest arguments $token and 31536000, adminless, no owner. deposit(uint256 amount, uint64 unlockAt) creates a numbered lock owned by the caller; require amount > 0, unlockAt > block.timestamp and unlockAt <= block.timestamp + maxLockSeconds. withdraw(uint256 lockId) releases the full amount only to the lock owner once block.timestamp >= unlockAt, once. extend(uint256 lockId, uint64 newUnlockAt) only by the owner, only later than the current unlockAt and within the cap from now. Views: lock(lockId), locksOf(address) returning ids, totalLocked. Events for deposit, extend, withdraw. SafeERC20, no fees, no admin, no pause, no early exit. Constructors take only static words; no post-deploy initialization, no constructor ETH. Solidity with OpenZeppelin, reproducible offline Foundry build with bytecode_hash=none. Tests: early withdraw reverts, double withdraw reverts, non-owner withdraw/extend reverts, extend cannot shorten, cap enforced on deposit and extend, zero amount reverts, exact-boundary unlock works, fuzz deposits/withdrawals conserve tokens (balance == totalLocked). Independent review covers token, application contract, tests and generated launch.json.

Pinned current Sepolia policy v5: 2% rewards this launch's accepted contributors by existing scoring, 8% equally among unique wallets with accepted work in preceding 12 hours, overlap combined into one leaf, 80% LP, 10% treasury, one-hour unlock. The control plane freezes allocations; workers must never invent recipients or choose economic policy. Native ETH pool, fee 3000, tickSpacing 60, policy opening fully diluted valuation 20 ETH for all 1 billion tokens. Policy derives effective price; manifest initialPrice is retained for provenance but overridden by policy. Token-only liquidity, no ETH funding. No mainnet transactions.

After verified deployment, build a minimal React/Vite/TypeScript page with RainbowKit wallet connection, wagmi/viem, and no custom styling (plain browser defaults; RainbowKit's required stock CSS is fine). Offer switch to Sepolia; disable writes when disconnected or on the wrong chain. Show pending, confirmed, rejected-signature and reverted states for every transaction and re-read state after each receipt. Token spends use an exact-amount approve step before the action when allowance is short. Title Time Lock, display $LOCK and Sepolia. One plain sentence: lock LOCK tokens until a date you choose; nobody can withdraw them early. Show wallet LOCK balance and total locked. Deposit form with amount and a date-time input (validated against the 365-day cap). Table of the wallet's locks with amount, unlock time, live countdown and status; Withdraw enabled only when unlocked and not withdrawn; Extend with a later date.

Use actual .imd/reads/deployment.json for token/app addresses, chain, source and ABIs, and build output imd-deployment.json as mandated by the workflow; no invented addresses. Injected wallets must work without operator credentials; do not invent a WalletConnect project ID. Keep web source/package/lock/build config in web/, relative-base static export in root dist/, docs in docs/. Export implementation-derived ABIs and verify canonical ABI hashes against the handoff. Build, typecheck and exercise real browser interactions without broadcasting from worker keys; publish actual evidence and state limitations. A failed RPC read is an error state, never zero. User authorizes normal configured GitHub/IPFS hosting and Sepolia deployment through existing services, not worker access to secrets or direct worker broadcasts. Finish only after source publication, verified deployment, website publication and reachability validation. All contract and workflow steps, including manifest, independent review and frontend, require the premium inference tier with approved highest-capability Claude or Codex models. No downgrade to runtime defaults or economy models.