Skip to content

Latest commit

 

History

History
320 lines (243 loc) · 12.5 KB

File metadata and controls

320 lines (243 loc) · 12.5 KB

Wetware Engineering Banner

License Lint Status Spec Version Bilingual Stars

Decouple biological capabilities from organisms into reusable modules,
reconstruct living systems with software engineering paradigms.

AboutQuick StartDocsConceptsRoadmapContribute


🧬 What is Wetware Engineering?

Wetware Engineering is an interdisciplinary framework that applies software engineering paradigms to biological system construction.

💡 This is not "running biology as software", but rebuilding life systems using programming paradigms.

Key Innovations:

🧩 Bio-Component Organs, tissues, actuators as composable modules
🔌 Bio-Interface Standardized connections for plug-and-play
📝 Bio-DSL Domain-specific language for system composition
⚙️ Bio-Runtime Resource scheduling and monitoring system
┌────────────────────────────┐
│   Traditional Biology      │
│   ────────────────────     │
│   🔬 Monolithic organisms  │
│   📝 Ad-hoc protocols      │
│   🔄 Manual integration    │
│   📊 Implicit dependencies │
└────────────────────────────┘
            ⬇️
┌────────────────────────────┐
│   Wetware Engineering      │
│   ────────────────────     │
│   🧩 Modular components    │
│   📋 Standard interfaces   │
│   ⚡ Plug-and-play         │
│   📦 Managed dependencies  │
└────────────────────────────┘

🚀 Quick Start

# Clone the repository
git clone https://github.com/tukuaiai/wetware-engineering.git
cd wetware-engineering

# Explore documentation
ls i18n/en/    # English docs
ls i18n/zh/    # 中文文档
💻 Try Bio-DSL Example
// Define components
COMPONENT muscle FROM "muscle-actuator-human-skeletal@^2.3"
COMPONENT sensor FROM "piezo-force-sensor@~1.1"
COMPONENT controller FROM "neural-organoid-spinal@>=0.8"

// Connect components
CONNECT sensor.output TO controller.input
CONNECT controller.output TO muscle.stimulation

// Runtime configuration
RUNTIME {
  perfusion: { temperature: 37°C, flow_rate: 0.5 mL/min },
  control: { mode: "closed_loop" }
}

📚 Documentation

📖 Wetware Engineering Core

Document EN 中文 Description
Quick Start 📄 📄 5-minute introduction
Plain Language 📄 📄 Zero-barrier explanation
Core Concepts 📄 📄 Complete introduction
Manifesto 📄 📄 Vision & principles
Technical Spec 📄 📄 Bio-Component Spec & DSL

🧠 Immortality Project

📁 Core Documents — Architecture, 27 Elements, Technical Blueprint
Document EN 中文
Overview 📄 📄
Human 3.0 Architecture 📄 📄
Architecture (Academic) 📄 📄
27 Elements 📄 📄
27 Elements (Academic) 📄 📄
Technical Blueprint 📄 📄
Blueprint (Academic) 📄 📄
🎭 Philosophy — Emotion Modeling, Experience Machine
Document EN 中文
Emotion Modeling 📄 📄
Emotion Modeling (Academic) 📄 📄
Experience Machine 📄 📄
Experience Machine (Academic) 📄 📄
📢 Guides — Social Media, Outreach
Document EN 中文
Human 3.0 Social Media 📄 📄
Social Media (Academic) 📄 📄

📄 Academic Paper

Resource Link
📥 Preprint PDF (13 pages) Download
📝 LaTeX Source View
📖 Markdown Draft Read

🎯 Core Concepts

Component-Interface-Runtime

┌─────────────────────────────────┐
│      WETWARE ENGINEERING        │
├──────────┬──────────┬───────────┤
│COMPONENT │INTERFACE │  RUNTIME  │
│(Module)  │  (API)   │(Orchestr.)│
├──────────┼──────────┼───────────┤
│◆ Actuator│◆ Power   │◆ Schedule │
│◆ Sensor  │◆ Signal  │◆ Resource │
│◆ Process │◆ Isolate │◆ Monitor  │
│◆ Metabol │◆ Mechani │◆ Fault    │
└──────────┴──────────┴───────────┘

Software ↔ Wetware Mapping

Software Wetware Example
Package Manager Bio-Registry Discovery
Semver Bio-Versioning muscle@2.3.1
API Contract Bio-Interface I/O spec
Unit Test Viability Test Verification
Container Perfusion Life support

📁 Project Structure

wetware-engineering/
├── 📄 README.md              # You are here
├── 📄 AGENTS.md              # AI Agent guide
├── 📄 CONTRIBUTING.md        # Contribution guide
├── 📄 LICENSE                # CC BY-SA 4.0
│
├── 🌐 i18n/
│   ├── en/                   # English documentation
│   └── zh/                   # 中文文档
│
├── 📝 paper/arxiv/           # Academic paper (13 pages)
│
└── ⚙️ .github/workflows/     # CI/CD

🗺️ Roadmap

Status Milestone
Core concept definition
Bio-Component Spec v0.1
Bio-DSL syntax draft
Bilingual documentation (EN/中文)
Academic paper preprint
🚧 arXiv submission
📋 Reference implementation (Python/TypeScript)
📋 Bio-DSL parser
📋 Component registry prototype

🤝 Contributing

We welcome contributions! See CONTRIBUTING.md for details.

git clone https://github.com/YOUR_USERNAME/wetware-engineering.git
git checkout -b feature/your-feature
git commit -m "feat: add something awesome"
git push origin feature/your-feature

❓ FAQ

What's the difference between Wetware Engineering and Synthetic Biology?

Synthetic biology operates at the gene/molecular level (e.g., BioBricks), while Wetware Engineering operates at the organ/system level. They are complementary: synthetic biology defines component internals, Wetware Engineering defines how components combine.

Can Bio-DSL actually run?

Currently Bio-DSL is a conceptual specification with no runtime implementation. Its value lies in providing a standardized system description language, laying the foundation for future toolchains.

What are the practical applications?

Short-term: Conceptual framework & standard specifications
Mid-term: Toolchain development
Long-term: Reusable, composable biological systems engineering


🔗 Links & Resources

GitHub ORCID ZRead


📄 License

This project is licensed under CC BY-SA 4.0 — Free to share and adapt with attribution.


Built with ❤️ for the future of biological engineering