- <your name here>
- Expand and refine applications list
- Brainstorm spinoff applications of component technologies (i.e., identify and define immediate payoffs)
- Design short and medium term experiments and goals
- Identify and prioritize grand challenges'
- Outline ideal writing plan
Modest amounts of genetically encoded memory would be incredibly useful. For example, the equivalent of an 8-bit counter (allowing counting up to 256) would revolutionize the study of aging and cancer. As exciting, solving the practical challenges associated with implementing genetically-encoded memory requires considering and answering incredibly interesting puzzles associated with variation and reliability in the behavior of cellular and molecular systems.
- For example, replace "counting of bud scars" (not the bud scars themselves) in yeast, with engineered yeast that remember and report their own age (e.g., via fluorescent reporters). See PMID 18616424. Might need a 5- or 6-bit counter to really impact yeast research. Could collect enough cells to support many experiments, and new (for aging) kinds of experiments (e.g., RNA arrays, etc.).
- See PMID 17875664 for an early example.
- Could apply same counter to drive transducer / controller that was maintaining "young" gene expression levels
- Automatically record lineages as opposed to manual measurement (e.g., PMID 838129)
- Directed Evolution
(note, split applications into (a) consumer and (b) derivative)
- Big picture
- Reliably holds state
- Controllable state change
- Then, degenerates into many application-specific requirements
- What are the applications for memory and logic in biological systems?
- How do naturally evolved mechanisms break down between combinatorial and sequential logic?
- Need a chart listing all mechanisms with associated cellular applications, requirements, timescale ...
- Yeast (5- or 6-bit counters)
- Worm (4- or 5-bit counters for development? Need to double check depth of worm's developmental lineage)
- Human (4- or 5-bit counters for development? Again, need to check depth of lineage; also, may need more for "cancer" related questions)
- Note that should add bacteria and plants to this list, but haven't spec'd out applications yet (moss?)
- What are the available / best physical mechanisms to store state?
- How is state written?
- How is state read?
- How long do the read and write steps take?
- How much energy is used to change or maintain state?
- What determines spontaneous switching rates?
- What device or system architecture(s) enable memory?
- How are physical mechanics linked to architecture (e.g., do all mechanisms work for all architectures)
- Can the mechanics of writing, storing, and reading be translated across species and kingdoms, w/o need to organism specific factors?
- Writing Mechanisms
- Storage Mechanisms
- Epigenetic, DNA
- Epigenetic, extra-DNA, molecular levels (e.g., Gardner et al. latch)
- Location (e.g., cytoplasm vs. nuclear)
- Noncovalent (e.g., protein-protein interactions)
- Covalent (e.g., post-translational modification)
- Reading Mechanisms
- DNA Methylation and Demethylation
- Error prone DNAp
- DSB & repair
- Timekeeping (James Ferrell)
- Feedback loops (James Ferrell)
- Past Examples
- Electrical (Lu)
- (starting reference on computer data storage, URL)
- Mechanical (DE)
- Fluidic (Ton)
- (starting reference on fluidic logic, URL)
- Biological (Jerome)
- Performance Characteristics
- Spontaneous Switching Rate
- Device Architecture
- (note challenge -- are all device architectures the same, independent of substrate, or not?)
Infinite monkey group meeting 31 Oct 2008