{"workflow":{"id":"494c12f3-b762-4088-8c87-a29716bad239","objective":"Company Operations & Contracts:\n\nGenesis Protocol is a community-driven utility token deployed on the Sepolia network. It utilizes a standard ERC-20 smart contract designed for seamless transfers, decentralized trading, and Web3 integration within the ecosystem.\n\nToken Specifications:\n\n    Token Name: GENESIS PROTOCOL\n\n    Token Symbol: GENESIS\n\n    Total Supply: 1,000,000,000\n\n    Decimals: 18\n\nWebsite Functionality (genesis-protocol):\n\nThe web application presents an interactive dashboard connected to Sepolia, featuring:\n\n    Real-time token metrics, total supply, and circulating supply tracking.\n\n    Interactive wallet connection for user token balances and network interaction.\n\n    Direct verification links to the contract on Sepolia Etherscan and liquidity pool status.","status":"completed","brief":"# Approved workflow\n\nCompany Operations & Contracts:\n\nGenesis Protocol is a community-driven utility token deployed on the Sepolia network. It utilizes a standard ERC-20 smart contract designed for seamless transfers, decentralized trading, and Web3 integration within the ecosystem.\n\nToken Specifications:\n\n    Token Name: GENESIS PROTOCOL\n\n    Token Symbol: GENESIS\n\n    Total Supply: 1,000,000,000\n\n    Decimals: 18\n\nWebsite Functionality (genesis-protocol):\n\nThe web application presents an interactive dashboard connected to Sepolia, featuring:\n\n    Real-time token metrics, total supply, and circulating supply tracking.\n\n    Interactive wallet connection for user token balances and network interaction.\n\n    Direct verification links to the contract on Sepolia Etherscan and liquidity pool status.\n\nThe requester chose this release: source code published to GitHub, website hosted on IPFS, contracts deployed on chain.\n\nCompany Operations & Contracts:\n\nGenesis Protocol is a community-driven utility token deployed on the Sepolia network. It utilizes a standard ERC-20 smart contract designed for seamless transfers, decentralized trading, and Web3 integration within the ecosystem.\n\nToken Specifications:\n\n    Token Name: GENESIS PROTOCOL\n\n    Token Symbol: GENESIS\n\n    Total Supply: 1,000,000,000\n\n    Decimals: 18\n\nWebsite Functionality (genesis-protocol):\n\nThe web application presents an interactive dashboard connected to Sepolia, featuring:\n\n    Real-time token metrics, total supply, and circulating supply tracking.\n\n    Interactive wallet connection for user token balances and network interaction.\n\n    Direct verification links to the contract on Sepolia Etherscan and liquidity pool status.\n","briefDigest":"d744783ea2d9b32daec5e813c9c0a7ecb362a59f908b52dd14786164a28a5766"},"planning":null,"id":"43d73a6c-2bc9-4bb0-8767-dabaa47154ed","state":"completed","template":"shape:chain","objective":"WORKFLOW FRONTEND STAGE CONTEXT: contracts are already deployed. This assignment produces the frontend source, committed static export and validation evidence within its write scope. Put frontend source, package.json, lockfiles and build configuration under web/, the static export at repository-root dist/, and documentation under docs/ or web/. A web/** scope also receives an explicit web/.gitignore allowance; directory globs exclude other dotfiles. Follow narrower assigned paths when supplied. Root configuration and lockfiles stay protected. Read .imd/reads/deployment.json, preserve deployed source, and obtain implementation-derived ABIs from docs/abi/<Contract>.json at the pinned source commit; verify their hashes against the handoff. Read .imd/reads/workflow.md for the complete approved requirements, including wallet connection, swap controls, observability and tests. Submit the source/export/evidence to complete this worker assignment. The publisher subsequently publishes source and hosts the export; published URLs and CIDs are not worker-completion prerequisites. This assignment does not publish the site or redeploy contracts.\n\nMANDATORY FRONTEND ACCEPTANCE: Emit dist/imd-deployment.json after the final static export. Its schema is {version:1,launchId,chainId,sourceCommit,attestationHash,contracts:[{name,address,abiHash,abiPath}],assets:[{path,sha256}]}, plus poolKey copied exactly from the deployment handoff when the handoff has one (currency0, currency1, fee, tickSpacing and hooks unchanged; validation refuses a site that leaves it out), plus network and optionally walletAddChain copied unchanged from .imd/reads/network.json when it exists; add no other top-level key. Copy launchId, chainId, deployed sourceCommit, attestationHash and the exact contract set/name/address/abiHash from the validated deployment handoff. Export each implementation-derived ABI as JSON; abiPath and asset paths are relative to dist/, never URLs or parent traversal. The frontend must load this same imd-deployment.json as its runtime deployment configuration and load the referenced ABI JSON; do not maintain a separate address/chain/ABI map that can disagree. After building, enumerate every exported file except imd-deployment.json, including index.html and all ABI JSON, and record each file's SHA-256 as lowercase hex. At most 128 assets and 8 MiB per file. The checker has a 64 MiB total HTTP response-body budget across immutable and named copies of assets/configuration plus RPC responses, so keep the export below half that budget with room for overhead. The manifest excludes itself to avoid a recursive hash. Rebuild the manifest after any export change and commit it with the export. Worker build/typecheck/browser/interaction validation remains required. After source delivery, IPFS pinning and site naming, the control plane checks the fixed CID and named entrypoint, all declared asset hashes, deployment configuration/ABI hashes against the attested handoff, and configured-RPC chain ID and nonempty contract code. It does not execute browser JavaScript or wallet swaps. Submit before these publication checks run; their success gates overall workflow completion.","blockedReason":null,"createdAt":"2026-10-05T21:53:33.855Z","updatedAt":"2026-10-05T22:17:59.680Z","paidBy":"0xbbf17c1376eb60bdb4a5821042e4ea1bc9aab21e","parentJobId":"71a65ccf-28c2-47f3-91ac-779631f8738d","project":{"id":"71a65ccf-28c2-47f3-91ac-779631f8738d","head":"43d73a6c-2bc9-4bb0-8767-dabaa47154ed","running":null,"versions":[{"jobId":"71a65ccf-28c2-47f3-91ac-779631f8738d","workflowId":"494c12f3-b762-4088-8c87-a29716bad239","objective":"Company Operations & Contracts:\n\nGenesis Protocol is a community-driven utility token deployed on the Sepolia network. It utilizes a standard ERC-20 smart contract designed for seamless transfers, decentralized trading, and Web3 integration within the ecosystem.\n\nToken Specifications:\n\n    Token Name: GENESIS PROTOCOL\n\n    Token Symbol: GENESIS\n\n    Total Supply: 1,000,000,000\n\n    Decimals: 18\n\nWebsite Functionality (genesis-protocol):\n\nThe web application presents an interactive dashboard connected to Sepolia, featuring:\n\n    Real-time token metrics, total supply, and circulating supply tracking.\n\n    Interactive wallet connection for user token balances and network interaction.\n\n    Direct verification links to the contract on Sepolia Etherscan and liquidity pool status.","baseCommit":"0243d7da4a4337ae8b16bcdf15bb4ead736fd68f","state":"completed","createdAt":"2026-10-05T21:25:40.047Z"}]},"deliver":true,"host":true,"site":{"id":"45422f77-4428-48a7-b77b-6e8a5dfc380a","jobId":"43d73a6c-2bc9-4bb0-8767-dabaa47154ed","kind":"launch","tokenId":null,"agentId":null,"url":"https://genesis.site.identitymd.eth.limo","status":"named","holdReason":null,"takenDownAt":null,"takenDownReason":null,"label":"genesis","cid":"bafybeigtwjn3hlcnydvyw4mt2iwbv7knpfssr3r2phyyzzln2edtw6q2eu","bytes":647131,"ensName":"genesis.site.identitymd.eth","txHash":"0xd8e7cfc7dcaafffa6163e6068326b5880cf617d42e60f2a08edcee8a819af645","blockNumber":26129173,"attempts":0,"failure":null,"pinnedAt":"2026-10-05T22:18:15.337Z","namedAt":"2026-10-05T22:31:27.100Z","supersededBy":null,"supersededAt":null,"createdAt":"2026-10-05T22:17:59.680Z","updatedAt":"2026-10-05T22:31:27.100Z"},"launch":{"requested":false,"kind":null,"id":null,"status":null,"chainId":null},"oracleRequestId":null,"delivery":{"repoUrl":"https://github.com/identity-md-launches/launch-735-workflow-frontend-stage-context","pullRequestUrl":"https://github.com/identity-md-launches/launch-735-workflow-frontend-stage-context/pull/1","commit":"f6d827e25407ac12b6e76a6b387f139ee1117cb4","deliveredAt":"2026-10-05T22:18:28.988Z","media":null},"media":null,"nodes":[{"key":"frontend_for_contract","role":"implement","state":"accepted","attempt":1,"revisions":0,"judgeRevisions":0,"dependsOn":[],"allowedPaths":["web/**","dist/**","docs/**","web/.gitignore"],"failureReason":null,"dispatchNote":null,"dispatchNoteAt":null,"updatedAt":"2026-10-05T22:17:59.680Z","verdict":{"status":"accepted","profile":"none","evaluation":"structural","rejectionCode":null,"detail":"paths and tree verified; no suite was run for this kind of work","verifierVersion":"0.1.0+f8d984f2","verifiedTreeHash":"94aa341fe2cac6ddbf13602e0bc99e5aba832300","at":"2026-10-05T22:17:59.691Z","failedChecks":[]},"seat":{"tokenId":"1342","agentId":"51418"},"live":null}],"reviews":[{"status":"sent","chainId":1,"txHash":"0xc4d144a930a76bf87acef3997a2c77131a9c1f6e95030b27792cb6610c58d101","blockNumber":26129114,"sentAt":"2026-10-05T22:19:48.769Z","entries":[{"nodeKey":"frontend_for_contract","agentId":"51418","value":1,"role":"verification:structural"}]}]}