Skip to content
ADVANCING AI. FOR THE BENEFIT OF HUMANKIND.A Mainely Code research & engineering vision
NORTHSTARBY MAINELY CODE

NORTHSTAR/250-node qualification

E Pluribus Unum — Out of many, one.

The NORTHSTAR
250-Node Qualification Challenge.

A bounded proposal to qualify one Commander and up to 249 workers across local, private, and FRONTIER cloud infrastructure—with authority, evidence, recovery, and final publication intact.

Discuss hosting the qualification Download the qualification brief

Public R&D proposal · No affiliation, endorsement, or release claim implied.

The ask

A serious environment.
A reproducible test.

No customer data. No uncontrolled production access. No performance, partnership, or compatibility claim without evidence and mutual approval.

A node is a participant—not a hardware synonym.

A NORTHSTAR node is an admitted participant in a constellation. It may represent a native worker, model endpoint, bounded compute worker, or another qualified contributor. One machine may host more than one logical participant, and one participant may depend on managed infrastructure.

Constellation size is not simultaneous concurrency.

Mission budgets, deadlines, provider quotas, hardware limits, privacy boundaries, and safety policy independently bound active work.

YOU BRING

Racks, accelerators, and observability.

  • Isolated local, private, cloud, or hybrid capacity
  • Approved model and managed-inference access
  • Network visibility appropriate to the environment
  • A technical contact and bounded test window
WE BRING

NORTHSTAR and the acceptance framework.

  • The 250-node constellation design
  • Mission, authority, identity, and budget controls
  • Failure injection, rollback, and recovery procedures
  • Provenance and execution receipts
TOGETHER WE PROVE

What survives contact with reality.

  • Admission, scheduling, and local-to-cloud dispatch
  • Node loss, partitions, quota pressure, and cancellation
  • Evidence preservation and accountable synthesis
  • Reconciliation, rollback, and clean restart

Read the current public brief.

Four pages: architecture, node model, qualification ladder, evidence, partner responsibilities, and explicit limitations.

Download PDF

Control architecture

Different substrates.
One governed mission.

The operating-system and provider dataplanes do the real forwarding and computation. NORTHSTAR coordinates admitted work and evidence.

Qualification ladder

Scale only after
the previous stage earns it.

Each stage is labeled Planned, Locally implemented, Locally qualified, or Externally qualified. No percentage stands in for categorical evidence.

01

1 Commander + 3 workers

Identity, dispatch, evidence return, cancellation, and final publication.

CONTROLLED BASELINE
02

16 nodes

Mixed CPU/GPU capacity, model roles, budgets, worker loss, and heterogeneous scheduling.

HETEROGENEOUS CONSTELLATION
03

64 nodes

Network segments, quotas, node churn, degraded links, restart, and reconciliation.

INSTITUTIONAL SCALE
04

250 nodes

Control-plane pressure, failure-domain separation, sustained observability, publication integrity, and rollback.

INITIAL-RELEASE TARGET

Test plan

Failure is part of the qualification.

  • Admission, identity, provenance, rotation, and revocation
  • Heterogeneous scheduling and resource composition
  • Model/provider independence and correlated failures
  • Node churn, partitions, degraded links, and recovery
  • Rate limits, quotas, budgets, deadlines, and cancellation
  • Ambiguous outcomes, reconciliation, and rollback
  • Evidence volume, synthesis, and publication integrity

Partner value

A useful result—even when something breaks.

  • A documented 250-node evaluation and failure-injection plan
  • Environment-specific integration and capacity findings
  • Failure, recovery, and rollback analysis
  • Reproducible execution and provenance receipts
  • A limitations and unresolved-gates report
  • A joint technical summary only if mutually approved

Provider-neutral disclosure. Third-party company and product names are used only to identify potential interoperability and qualification environments. No affiliation, endorsement, access agreement, certification, or partnership is implied.

Discuss the environment

You bring the racks.
We bring the receipts.

Send a bounded description of the available environment. No credentials, private datasets, or sensitive architecture details are needed in the first message.

Email Mainely Code Review the evidence boundary
Organization: Available infrastructure: Approximate node / accelerator capacity: Private, cloud, or hybrid: Available frontier-model access: Preferred test window: Technical contact: