I am about to release a new electronic controller that combines embedded hardware with Python-driven firmware, a MySQL back-end, and fieldbus connectivity over Modbus. All of the engineering is on track; what I need now is a clear, authoritative set of documents that translate the design into language every stakeholder can act on. Your primary mission is to own the technical specification. You will study the current documentation, probe the firmware, and test so that every electrical characteristic, protocol register, and firmware feature is captured accurately. The finished work must speak fluently to three distinct audiences: • Engineers – deep component-level details, interface definitions, timing diagrams, code snippets, and compliance references. • End-users – installation notes, operating ranges, troubleshooting flowcharts, and safety notices. • Sales & Marketing – concise feature summaries, key performance numbers, and competitive talking points. I will give you full access to prototype units, source code, and existing design notes. Strong written English is essential; familiarity with Python, MySQL, and Modbus will let you verify behavior directly rather than rely solely on developer explanations. Deliverables 1. Master Technical and Design manual / Specification (living document in Word). 2. A two-page Product Brief distilled from the master spec for sales and marketing. Acceptance criteria: every functional block and interface is documented down to pin-out or API level; no section contains unanswered TBDs; language is consistent throughout; and the sales brief can be read and understood without the master spec in hand.