iGEM Implementation Wiki
Translate a project from laboratory result to a bounded use scenario. Make readiness, dependencies, risks, and reusable artifacts explicit instead of presenting a concept as deployable.
For precedent research or substantial implementation work, read the curated findings in references/benchmark-corpus.md and the compact reviewed-page index. Read the full official award ledger only when verifying or listing winners and nominees. Verify consequential details live.
For an end-to-end use case, prototype handoff, or deployment claim, adapt assets/templates/readiness-matrix.md.
Establish the implementation case
Name the intended user, beneficiary, setting, input, output, operating workflow, performance requirement, infrastructure, training, maintenance, cost, regulation, access, containment, and end-of-life path. Map each requirement to current evidence, an assumption, or future validation.
Route by artifact
- Implementation: end-to-end use scenario, readiness, validation path, constraints, and adoption.
- Safety and Security: hazards, threat or misuse cases, exposure paths, risk controls, residual risk, monitoring, and governance.
- Hardware: user need, requirements, design alternatives, schematics or CAD, bill of materials, build, tests, iteration, operating guide, and files.
- Software: user task, architecture, installation, inputs and outputs, examples, testing, limitations, repository, license, standards compatibility, external integration, and reproducible run path.
- Entrepreneurship: unmet need, customer and beneficiary, alternatives, value proposition, market evidence, regulatory and reimbursement path, business model, cost, risk, and milestones.
- Contribution: a clearly packaged part, dataset, protocol, model, design, software tool, or lesson that another team can reuse.
Match claims to readiness
Distinguish concept, simulated design, benchtop prototype, tested subsystem, integrated prototype, field-relevant validation, and deployable product. Show quantitative requirements beside achieved values where possible. Record failure modes and residual risks; a mitigation list without verification is still a proposal.
Verify artifacts
Test code installation or a representative run when authorized. Check CAD, schematics, BOM, firmware, datasets, licenses, manuals, emergency behavior, and repository links. Render workflows and technical tables on mobile. Do not claim open source, low cost, safe, scalable, accessible, or sustainable without inspectable support and a defined boundary.
For current Best Software eligibility, verify the live rules. In the 2026 snapshot, software must use an OSI-approved open-source license and be hosted in the dedicated iGEM GitLab repository; a GitHub link alone is not sufficient. Check any Software & AI Village restriction before recommending the award.
1---2name: igem-implementation-wiki3description: Plan, write, implement, or audit iGEM Implementation, Safety and Security, Entrepreneurship, Hardware, Software, and Contribution pages. Use for real-world deployment paths, risk controls, user workflows, device or software evidence, business feasibility, or reusable artifacts; use wet-lab or Model skills for their underlying scientific analyses.4---56# iGEM Implementation Wiki78Translate a project from laboratory result to a bounded use scenario. Make readiness, dependencies, risks, and reusable artifacts explicit instead of presenting a concept as deployable.910For precedent research or substantial implementation work, read the curated findings in [references/benchmark-corpus.md](references/benchmark-corpus.md) and the compact [reviewed-page index](references/generated/reviewed-pages.md). Read the full [official award ledger](references/generated/award-ledger.md) only when verifying or listing winners and nominees. Verify consequential details live.1112For an end-to-end use case, prototype handoff, or deployment claim, adapt [assets/templates/readiness-matrix.md](assets/templates/readiness-matrix.md).1314## Establish the implementation case1516Name the intended user, beneficiary, setting, input, output, operating workflow, performance requirement, infrastructure, training, maintenance, cost, regulation, access, containment, and end-of-life path. Map each requirement to current evidence, an assumption, or future validation.1718## Route by artifact1920- **Implementation:** end-to-end use scenario, readiness, validation path, constraints, and adoption.21- **Safety and Security:** hazards, threat or misuse cases, exposure paths, risk controls, residual risk, monitoring, and governance.22- **Hardware:** user need, requirements, design alternatives, schematics or CAD, bill of materials, build, tests, iteration, operating guide, and files.23- **Software:** user task, architecture, installation, inputs and outputs, examples, testing, limitations, repository, license, standards compatibility, external integration, and reproducible run path.24- **Entrepreneurship:** unmet need, customer and beneficiary, alternatives, value proposition, market evidence, regulatory and reimbursement path, business model, cost, risk, and milestones.25- **Contribution:** a clearly packaged part, dataset, protocol, model, design, software tool, or lesson that another team can reuse.2627## Match claims to readiness2829Distinguish concept, simulated design, benchtop prototype, tested subsystem, integrated prototype, field-relevant validation, and deployable product. Show quantitative requirements beside achieved values where possible. Record failure modes and residual risks; a mitigation list without verification is still a proposal.3031## Verify artifacts3233Test code installation or a representative run when authorized. Check CAD, schematics, BOM, firmware, datasets, licenses, manuals, emergency behavior, and repository links. Render workflows and technical tables on mobile. Do not claim open source, low cost, safe, scalable, accessible, or sustainable without inspectable support and a defined boundary.3435For current Best Software eligibility, verify the live rules. In the 2026 snapshot, software must use an OSI-approved open-source license and be hosted in the dedicated iGEM GitLab repository; a GitHub link alone is not sufficient. Check any Software & AI Village restriction before recommending the award.
TravisBoston16