Worked example · Asteria
From a 1,024-GPU brief to an architecture package.
See what you would be committing to: the selected design, delivery scope and decisions still to close. Asteria is a worked architecture scenario; it is not a customer deployment.
01
The brief
Know what the bid asks you to deliver.
The RFP asks for 1,024 B300 GPUs, Spectrum-X networking and 8 PiB of usable storage. The proposal selects 128 HGX B300 nodes and WEKA. Storage performance, facilities and orderable equipment still need validation before you can commit to delivery.
02
The package
Start with the decision. Then inspect the evidence.
1. Read the eight-page proposal
See the proposed scope, architecture basis and open decisions. Use the three-page RFP to check what the buyer actually asked for.
2. Challenge the architecture
The executive brief explains the selected design and indicative BOM. The security report identifies 13 high and 3 medium findings for engineering review.
3. Understand the delivery work
The delivery plan lists 285 tasks and 12 gates. Use it to discuss dependencies and ownership. The walkthrough shows the recorded steps behind the outputs.
03
PDFs
The documents behind the example.
The selected design is HGX B300, Spectrum-X and WEKA. Detailed engineering remains open. Read the design notes below.
Start with the proposal or explore the supporting reports in the document library. Get all six PDFs to review with your team.
- Get PDF →
PDF · Asteria worked example
Project proposal
Start here · 8 pages. See the proposed scope, selected design, delivery phases and decisions to close before committing.
- Get PDF →
PDF · Asteria worked example
Executive architecture brief
14 pages. Review the HGX B300, Spectrum-X and WEKA basis, indicative BOM and approval conditions.
- Get PDF →
PDF · Asteria worked example
Project delivery plan
49 pages. Trace 285 tasks, dependencies and 12 gates. This planning framework has no committed dates or named delivery team.
04
Design notes
What remains open in this example.
The pack establishes one selected architecture and a consistent security count. Approval with conditions covers high-level architecture only. It does not authorise procurement or installation.
Read the open decisions and source notes
The WEKA proposal uses 67 planning backends and calculates 8.104 PiB usable capacity. Vendor sizing, throughput, power and orderable SKUs remain unqualified. Listed vendor alternatives are candidates, not approved substitutions.
The security report contains 16 findings: 13 high and 3 medium. Selected security zones and governed crossings are not supplied. These findings guide the security architect; they do not demonstrate tested controls.
The delivery plan has 14 phases, 285 tasks and 12 gates. Dates, durations and a named delivery team are not supplied. Treat it as a planning framework, not a committed programme.
The reports identify REV-000003 and BASELINE-000001. Their issue date says “Date not recorded”; the executive brief separately records a review timestamp of 12 September 2026. The RFP and proposal use the Asteria scenario name; the recorded validation project is REM VAL-02-HGX-SX-WEKA for Conformance Engineering 02.
The full 79-page architecture is held for discussion on a call. The source documents are preserved; only the supplied RFP was converted from Word to PDF.
05
Your bid
Which decisions are still open in your bid?
Use the example to list the requirements, assumptions and delivery questions your team needs to close. Bring that list to a design review.
Explore the $5,000 design review