LOG 002 / RESEARCH WORKFLOW / ACTIVE

GitHub

GitHub becomes the laboratory memory: firmware, schematics, experiment notes, issues, releases, and decisions live together so a signal can be traced back to the exact code and setup that created it.

GIT

Git records every meaningful source changeIssues track hypotheses, bugs, and experimentsReleases freeze known firmware versionsREADME files make tests repeatable

RESEARCH SIGNAL FLOWhypothesis → issue → branch → bench test → release → field note

MYCOTUNE USE CASES

◌ Tag the firmware version in every MycoTune recording

◌ Keep hardware pin maps next to acquisition code

◌ Attach test data and photos to experiment issues

◌ Use branches for risky signal-processing changes

NEXT BENCH STEPS

→ Create a MycoTune research repository structure

→ Add issue templates for bench experiments

→ Define firmware version and device ID fields

→ Publish a first reproducible acquisition release

PRIMARY RESEARCH SOURCE / GitHub repository documentation ↗