Architecture discovery guides for practical decisions.
Download an example before you begin. Each guide explains the situation, practical next steps, tooling relevance and what to bring to an architecture discussion.
Fictional examples. These are authored guides, not generated customer results, approved architectures or proof of ETS/device capabilities. All three PDFs are two pages. Markdown provides an editable text alternative.
How to use these guides
Choose the scenario closest to your workflow.
Replace example details with your confirmed facts; keep unknowns visible.
Review the actions with the suggested owners before selecting tooling.
Bring only sanitized examples to a discussion. No meeting or sales-contact request is needed to download a guide.
Sample discovery report 01 / Existing approval process
Validate the tools you already have
Determine whether an existing change-management process can support a bounded approval claim without buying new tooling.
ETS: Potentially relevant. The declared gap and independent reviewer justify a scoped development evaluation. No ETS release or capability has been verified in this example.
Edge: Not indicated on the supplied facts. A software-only integration should be evaluated first.
ETS: Insufficient information. Evidence-gap and independent-verification needs are unresolved. Define those before proposing an ETS integration.
Edge: Potentially relevant because a disconnected physical boundary is declared. No device is selected, and no hardware capability is assumed.
Preparing your own report
Gather your goal, workflow, actors, consequences of failure, existing tools, evidence claim, intended verifier and operating constraints. You can leave answers unknown. These guides help you prepare for discovery; a qualified architect must validate requirements and design decisions.