Quickstart

MSGF in three steps

Sign in once — your workspace generates IDE settings, extension download, and project mapping in one place.

  1. Step 1

    Start in shadow mode

    Start the 7-day shadow-mode trial to point an SDK at the MSGF gateway — no console seat required. Already invited? Sign in and open Workspace Projects to download Pulse Guard, copy the setup prompt, and add each app. Beta waitlist is for a console seat, not account creation.

  2. Step 2

    Install msgf-pulse-guard

    Download the extension for Cursor or VS Code, install from the .vsix, and paste the settings from your workspace.

  3. Step 3

    Map your repo & open the dashboard

    Register the folder you code in under Projects, then watch policy-domain health on your governance dashboard. Optional BYOK keys live in .msgf/keys/ (gemini.key, claude.key, optional xai.key for Grok). Pick routing presets on the dashboard under token cost.

    Compare pricing for managed Pro inference. Author and Education apps live under Other products.

Jump to policy-domain guide · Open workspace setup


Governance reference

How the six policy domains work

Each domain is an isolated context partition. The pipeline inspects, routes, and stores outcomes so prompts never mix projects. Use this guide when wiring ingest or reading dashboard health.

Execution pipeline

  1. SWEEP
  2. SHARD
  3. DEFEND
  4. CROSS-REF
  5. CONVERGE
  6. ARBITRATE
  7. PERSIST
P1

Static Ledger (Immutable Rules & Security)

What it does
Stores non-negotiable platform law: pledge versions, security constants, and HALT conditions. If a request violates legal or security policy, MSGF stops before models run.
In your product
Your app should collect explicit user consent (No-AI-Training pledge) once per account. MSGF records it in state_beats; Pulse returns 403 until pledge exists.
How to use it
Sign up → accept pledge on first dashboard visit. Do not bypass with client-only checkboxes — call MSGF after registration so DEFEND can enforce the same legal_version everywhere.
P2

Flow Sequence (Pipeline & Execution Order)

What it does
Orders the pipeline: preflight → shadow → dual-model consensus → optional human tie-breaker. Ensures gates run in the master directive sequence, not ad hoc in your BFF.
In your product
Route risky actions through POST /api/msgf/pulse (typing/HAL) and POST /api/msgf/ingest (code/docs). Your product supplies keystrokes or files; MSGF returns routing tier (GREEN / YELLOW / RED) and remediation hints.
How to use it
After mapping a project, send natural keystrokes via Pulse or ingest a repo slice. Watch dashboard stoplights — YELLOW may schedule heal-queue work; RED may require human arbitration.
P3

Entity Profiles (Identity, Roles & Stylometry)

What it does
Binds humans and tenants to entitlements: tier_id, credits, Stripe status, tenant silo. Pulse middleware checks p4_profiles before burning inference credits.
In your product
Each integrator gets a tenant silo from the license or session in the MSGF database. Map your app's org/user id to x-msgf-entity-id; keep billing in MSGF or mirror Stripe webhooks into p4_profiles.
How to use it
Mint a license (`msgf_live_…` / `msgf_test_…`) and send it as `x-msgf-key`. Tenant always comes from that license row — never set `x-msgf-tenant-id` as the source of truth.
P4

State Ledger (Runtime Telemetry & Active Memory)

What it does
Flight recorder for rhythm telemetry (dwell, flight, paste flags), session beats, and Redis hot slices. HAL scores and baseline training live here — not under P1.
In your product
Capture keystrokes in your editor, LMS, or HR monitor; normalize to p1-hal-standard and POST to Pulse. Optional: send chunked packets via msgf/hal-author-bridge (175 words, 10-word overlap).
How to use it
Install msgf-pulse-guard, paste workspace settings, type until baseline clears (202 → 200). Dashboard P4 turns green when recent HAL activity exists for your mapped project.
P5

Local Variables (Workspace Context Sharding)

What it does
Holds per-tenant configuration shards: project_origin tags, module context, and UI-scoped variables used to scope health views and ingest paths.
In your product
Register each repo or product surface in Projects with a stable project_origin. Health API and dashboard filter telemetry to those tags so one account can separate workstreams.
How to use it
Setup → Projects → add local path or GitHub repo. Re-use the same origin string in ingest metadata and IDE settings so SWEEP lineage maps to the right silo.
P6

Constraint Ledger (Vault vs. Hall Anomaly Isolation)

What it does
Vault stores successful patterns; Hall stores failures and constraints. Every ingest/Pulse cross-references genealogical bug_index (1.0 / 1.1 / 1.1.1) before persisting vectors.
In your product
Send coherent file paths and optional bug_index on ingest. Failed validations land in Hall; successes in Vault — heal-queue remediates Hall rows with BULK / INDIVIDUAL / SCHEDULED actions.
How to use it
Run ingest on a sample file after Pulse baseline. Open heal-queue from a pillar card when misalignments appear; use human arbitration when the circuit breaker trips.

Full engineering map: MSGF product overview · Open governance dashboard

Getting Started | MSGF