Skip to content
Mainely Code
The Great NorthMainely Code Providence ArchitectureExploreArchitecture brief
The complete Mainely Code ecosystem

The Great North

A Mainely Code Providence Architecture

A connected system—not a single app. The Great North brings cognition, cloud experience, design, software engineering, first-party inference, trusted compute, identity, and proof together while preserving a clear job and authority for every system.

Responsibility by design

One concern. One authority.

Providence is designed to make powerful AI systems easier to understand, control, and audit by keeping cognition, policy, execution, trust, access, and product acceptance separate enough to challenge one another.

Executive cognition

Northstar

Plans, routes, arbitrates, preserves provenance, manages executive budgets, and owns final cognitive judgment.

Policy compilation

Prefrontal

Compiles what is permitted: models, tools, locality, fallback, retention, evidence, cancellation, and risk constraints.

First-party inference

Great North Provider

Owns model release identity, admission, scheduling, runtime lifecycle, streaming, usage, recovery, and inference evidence.

Trusted infrastructure

Network Fabric

Owns node identity, private reachability, eligibility, leases, network policy, effective state, and infrastructure evidence.

Cloud experience

Project Sasquatch

Owns the broad cloud command-center journey, conversations, routed capability access, account surfaces, and operator workflows.

Engineering acceptance

Mainely Code Buildroom

Owns bounded work orders, candidate diffs, tests, proof bundles, rollback, and verified PR or apply proposals.

Design acceptance

Orb-Weaver

Owns visual intake, maps, flows, components, style tokens, previews, and editable interface foundations.

Identity and access

Licensing Server

Owns canonical identity, subscription, entitlement, signed product access, assignment, revocation, and cross-product isolation.

No component gets to grade its own homework. Provider cannot weaken policy. Network trust cannot be invented. Licensing cannot be granted by a product. A product's acceptance standard cannot be declared by the inference system.

Providence architecture diagram
Architecture at a glance

Customer intent moves through explicit authority.

The route can span local, private-fabric, and hosted infrastructure without changing who is allowed to decide, execute, trust, authorize, or accept.

1

Product intent

Sasquatch, Buildroom, or Orb-Weaver defines the customer job and product-specific success contract.

2

Northstar and Prefrontal

Northstar builds the route; Prefrontal compiles the policy-bound execution plan.

3

Provider and Fabric

Provider executes the exact model release only on Fabric-approved compute under the admitted plan.

4

Receipt and product proof

Inference evidence returns to the consuming product, which decides whether the real customer outcome passed.

Deployment choice

Built for more than one place.

The same authority and evidence contract is designed to extend from a local machine to a trusted private fabric or governed hosted region.

Local

Local / edge

Private, local-first execution for workloads that benefit from endpoint control, lower latency, or limited connectivity.

Private

Trusted fabric

Customer, office, lab, or private-cloud nodes connected through signed identity, policy, leases, and evidence.

Hosted

Regional / sovereign

Dedicated, regional, or customer-owned paths designed around isolation, residency, audit, and operational control.

No silent relocation. Locality and residency belong in the governed plan. An available or cheaper region cannot silently override them.

Architecture vision brief

The Great North runs on Providence.

Download the public document for the complete visual overview, current direction, and release posture.

The Great North public architecture brief cover