Projection scenarios
Planning scenarios, not measured deployments.
Projections and diligence
Projected active share, stored parameters, decode bandwidth, optimizer state, and weight-stream requirements.
Recorded finding: The outlook turns architecture assumptions into inspectable resource scenarios for planning.
Decision signals
Each value is mapped directly from the recorded summary artifact and retains its experimental, historical, or control context.
Planning scenarios, not measured deployments.
Derived from stated architecture assumptions.
Projected active versus same-size dense weight stream.
Projection envelope only.
Source-linked visual evidence
Charts are generated from normalized source fields. Every visualization includes its exact values in an accessible table.
Projection
Projected active weight stream compared with the same-size dense stream.
Finding: The projection estimates materially smaller active streams under its published assumptions.
| Group | Projected active | Same-size dense |
|---|---|---|
| Projection A | 150.6 GiB | 1,500.6 GiB |
| Projection B | 420.6 GiB | 5,820.6 GiB |
Method
All values are projections, not measured deployment results, and depend on the published assumptions.
Inspection and reuse
Source data
The recorded JSON artifact is staged from the governed public evidence pack during the build. Its currency notice determines whether it may be read as current.
Open source JSONProvenance
Use the public build receipt to compare the deployed site source, evidence digest, claim posture, and inference release state.
Open build receiptContinue reviewing
Decision relevance: research · engineering
Review evidenceDecision relevance: diligence · investment · governance
Review evidence