Chapter 25 — The Tangibles Product Manager

8 references

#	Reference	Links	Status
1	See Chapter 0, "Hardware Needs Digital Augmentation, Now" – the new synthesis of systems engineering and product management.	—	— Cross-reference
2	See "Product Management Frameworks for Tangibles: What Actually Works When Atoms Meet Bits" (companion article) – the Commitment Stack framework.	—	— Cross-reference
3	See Chapter 18, "Connected AND Secured? Think Again" – the Jeep Cherokee architecture failure and the $1 billion recall.	—	— Cross-reference
4	Electrum. GitHub repository. Open-source toolkit for hardware-software boundary mapping, drawing on Ben Einstein's Bolt framework and EVT/DVT/PVT process. github.com	Source	🟡 No archive
5	See Chapter 8, "The Connectivity Watershed" – FOTA architecture, dual partitions, the Rule of Ten.	—	— Cross-reference
6	See Chapter 18, "After It Ships" section – ETSI provision 3 (secure update mechanism), defined support periods, CRA reporting obligations.	—	— Cross-reference
7	See Chapter 9, "The Data Payload" – telemetry, edge AI, and the sense-decide-act loop.	—	— Cross-reference
8	Alex Guskov, "[PLACEHOLDER – post title]," IoT-Apps.com, [PLACEHOLDER – date]. [PLACEHOLDER – permalink] – a twenty-question checklist for qualifying an IoT project before any architecture exists; archive a snapshot for the companion references page. Items 1–6 (problem, success metric, operational impact, failure cost, ROI timeline) map to the validation work of Arc III and the business-model math of Chapter 20; the deployment-context items (pilot vs. full rollout, single vs. multi-site, indoor/outdoor, stationary vs. moving assets) inform the archetype choice in this chapter. iot-apps.com	Source	🟡 No archive

Found a broken link or outdated source?

Report on GitHub • Email report