# IMD discovery proposal — batch aced95e5-44a1-4e70-9eaa-0efaf332aad5

One worker's catalog proposal, not consensus. Source text was treated as untrusted data.

## Question
Which project do the three supplied evidence records belong to, in what role, and how should that project be described?

## Verified facts (public URLs fetched 2026-10-05, all HTTP 200)
- **Job b2246df4** (`https://api.imd.fun/jobs/b2246df4-...`): state `completed`. Its objective requests a minimal Counter contract for Ethereum mainnet: a count starting at zero, a permissionless `increment()` that emits an event, a `count()` read, no owner/admin/fees/funds/token, a Foundry test suite, and an independent security review before deployment. The job's project ID equals the candidate key `imd-b2246df4-...`.
- **Launch ed8f29a4** (`https://api.imd.fun/launches/ed8f29a4-...`): launch #734, kind `evm_contracts`, chain ID 1, status `admitted`. Its job list explicitly attaches job b2246df4. Its source repository is `identity-md-launches/launch-734-counter-minimal-counter-contract` (the GitHub page responds). Its admission checks report an accepted independent review, reproducible bytecode for one contract, and no token or pool.
- **Publication listing** (`https://api.imd.fun/publications?type=contracts...`): contains an entry for launch ed8f29a4 with the same Counter title, status `admitted`, and an empty artifacts list.

## Inferences
- The job is the work that built the Counter project. The launch lists this job as attached, and the job's objective is the build specification. The supplied data labels the job's role `researches`. I did not use that label because the job objective describes building the contract, not studying it.
- The launch and publication both describe the same project, which is a single contract.

## Uncertainty / unanswered
- Deployment to mainnet is **not confirmed**. The launch is `admitted`, and its artifact count is 0. The project should be described as an intended mainnet deployment, not as live.
- The sources don't say who created the project or who requested it (`requester` and `paidBy` are null).
- I did not review the contract source code myself. Statements about its behavior come from the job objective and the launch manifest.

## Discovery JSON
BEGIN_DISCOVERY_JSON
{"schemaVersion":1,"batchId":"aced95e5-44a1-4e70-9eaa-0efaf332aad5","inputHash":"d0c0e21f61aedee4ca6bfef5cc09625dc27702a3229e6436be967f05dcc7adcd","assignments":[{"requestId":"job:b2246df4-9856-41c0-b573-e6f0b67f5897","targetProjectKey":"imd-b2246df4-9856-41c0-b573-e6f0b67f5897","status":"supported","role":"builds","reason":"The job's project ID matches the candidate key, and launch #734 explicitly lists this job as attached. The job objective is the Counter build specification, so the role is builds. The supplied 'researches' label was not used.","evidenceIds":["job:b2246df4-9856-41c0-b573-e6f0b67f5897","launch:ed8f29a4-7f6e-4bd4-9c26-864645e90334"]},{"requestId":"launch:ed8f29a4-7f6e-4bd4-9c26-864645e90334","targetProjectKey":"imd-b2246df4-9856-41c0-b573-e6f0b67f5897","status":"supported","role":"builds","reason":"Launch #734 (Ethereum mainnet contracts launch, status admitted) attaches job b2246df4. Its source repository is the project-specific launch-734-counter repo.","evidenceIds":["launch:ed8f29a4-7f6e-4bd4-9c26-864645e90334","job:b2246df4-9856-41c0-b573-e6f0b67f5897"]},{"requestId":"publication:launch:ed8f29a4-7f6e-4bd4-9c26-864645e90334","targetProjectKey":"imd-b2246df4-9856-41c0-b573-e6f0b67f5897","status":"supported","role":"builds","reason":"The public contracts publication entry is keyed to launch ed8f29a4 and has the same Counter title. That launch explicitly attaches the project's job.","evidenceIds":["publication:launch:ed8f29a4-7f6e-4bd4-9c26-864645e90334","launch:ed8f29a4-7f6e-4bd4-9c26-864645e90334"]}],"projects":[{"projectKey":"imd-b2246df4-9856-41c0-b573-e6f0b67f5897","name":"Counter","nameType":"explicit","summary":"A minimal counter smart contract intended for Ethereum mainnet. Anyone can increment a shared count, which starts at zero; each increment emits an event, and the count can be read. It has no token, owner, admin functions, fees or held funds. Latest meaningful change: the build job completed, and launch #734 was admitted after an independent review and reproducible-bytecode checks. Mainnet deployment is not yet confirmed (no deployed artifacts are listed).","category":"other","evidenceIds":["job:b2246df4-9856-41c0-b573-e6f0b67f5897","launch:ed8f29a4-7f6e-4bd4-9c26-864645e90334","publication:launch:ed8f29a4-7f6e-4bd4-9c26-864645e90334"]}],"unresolved":[]}
END_DISCOVERY_JSON