Navigate

Quick find

Navigate NeuroForge

Esc

Start typing to search public pages and evidence.

    Projections and diligence

    Resource outlook

    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.

    On this page

    Currency and next evidence gate

    Decision signals

    Key metrics and controls

    Each value is mapped directly from the recorded summary artifact and retains its experimental, historical, or control context.

    2

    Projection scenarios

    Planning scenarios, not measured deployments.

    7.2%

    Lowest projected active share

    Derived from stated architecture assumptions.

    13.8×

    Largest projected bandwidth ratio

    Projected active versus same-size dense weight stream.

    3,124,890M

    Largest stored-parameter scenario

    Projection envelope only.

    Source-linked visual evidence

    Readable at a glance. Inspectable in detail.

    Charts are generated from normalized source fields. Every visualization includes its exact values in an accessible table.

    Projection

    Projected active parameter share

    Share of stored parameters projected to be active in each published scenario.

    Finding: Both scenarios assume a minority active share; this remains an architecture projection, not an observed runtime result.

    Projected active parameter shareShare of stored parameters projected to be active in each published scenario. Both scenarios assume a minority active share; this remains an architecture projection, not an observed runtime result.0.02.75.48.110.8%Projected active shareProjection AProjection A10.0Projection BProjection B7.2
    View source values
    Projected active parameter share; values in %
    GroupProjected active share
    Projection A10.0 %
    Projection B7.2 %

    Projection

    Projected weight stream

    Projected active weight stream compared with the same-size dense stream.

    Finding: The projection estimates materially smaller active streams under its published assumptions.

    Projected weight streamProjected active weight stream compared with the same-size dense stream. The projection estimates materially smaller active streams under its published assumptions.0.01,571.63,143.14,714.76,286.2GiBProjected activeSame-size denseProjection AProjection A150.61,500.6Projection BProjection B420.65,820.6
    View source values
    Projected weight stream; values in GiB
    GroupProjected activeSame-size dense
    Projection A150.6 GiB1,500.6 GiB
    Projection B420.6 GiB5,820.6 GiB

    Method

    How to interpret this pack

    1. Values are calculated from the public resource-audit projection envelope.
    2. The scenarios do not measure model quality, training memory, serving latency, or token throughput.
    Read the complete evidence method

    Claim boundaries

    All values are projections, not measured deployment results, and depend on the published assumptions.

    • Projection math only; measured scale-ladder evidence and resource-audit projections must remain separate.
    • Anonymous projection envelopes only; raw architecture inputs, scenario names, source paths, command names, script names, and mechanism knobs are not published.
    • Parameter counts are normalized to M.
    • Active-weight stream estimates are single-user decode projection signals, not throughput, training-memory, model-quality, production-readiness, or external reproduction claims.
    • Global training, scoped residency, and optimizer-state estimates remain separate claims.

    Inspection and reuse

    Downloads and provenance

    Source data

    Machine-readable summary

    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 JSON

    Provenance

    Build and evidence receipt

    Use the public build receipt to compare the deployed site source, evidence digest, claim posture, and inference release state.

    Open build receipt

    Continue reviewing

    Related evidence

    measuredpartial
    Historical
    Observed
    The scale matrix exposes a concrete engineering checkpoint with explicit dimensions and receipts.
    Supports
    Active parameters, evaluation loss, memory peak, and throughput-ratio results at the approved scale point.
    Does not support
    A single bounded scale matrix does not prove performance superiority across hardware or workloads.
    Next decisive evidence
    Repeat the matrix under one frozen current profile and matched control before current-stack use.

    Decision relevance: research · engineering

    Review evidence
    controlreviewed
    Refresh required
    Observed
    Diligence artifacts and boundary controls are explicitly inventoried rather than implied.
    Supports
    Artifact coverage, claim posture, clean-room controls, security review, and controlled gates.
    Does not support
    Readiness for diligence is not a declaration that all product, legal, or release risks are closed.
    Next decisive evidence
    Rebuild diligence coverage from the next clean approved evidence release and retain every unresolved gate.

    Decision relevance: diligence · investment · governance

    Review evidence