1 | Task and usage pattern
Describe whether the principal task is content production, data processing, model workloads or enterprise software. Record users, concurrency patterns, operating windows and output objectives. Keep unconfirmed demand separate instead of masking gaps with false precision.
2 | Existing resources and missing conditions
Record existing sites, systems, networks, teams and partner capabilities separately. Treat available, to validate and to add as condition states rather than achieved project outcomes.
3 | Site and infrastructure
Include power, cooling, connectivity, service access and the deployment environment. Appropriate specialists need to assess the detail; a concept facility on a website does not replace engineering material.
4 | Comparable pathways
Use the same demand and assumptions for each pathway. Describe resource scope, service relationships, questions to validate and next steps. Figures based on different conditions are not directly comparable.
5 | Project and partner relationships
Clarify what the customer, adviser, technology provider and project partner contribute. Mandates and formal disclosures retain their original sources and are not redefined by concept copy.
6 | The first delivery
Produce a one-page demand summary, conditions register, possible pathways and action table. Each action identifies the required input and owner role so the project can move beyond discussion.
