Quickstart

MSGF in three steps

Step 1
Create your account
Sign up or sign in. Open Workspace to copy a ready-made .vscode/settings.json block tied to your session.
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.
Step 3
Map your repo & open the dashboard
Register the folder you code in under Projects, then watch pillar health on your governance dashboard. Optional BYOK keys live in .msgf/keys/ if you bring your own models.
Compare pricing for managed Pro inference. Author and Education apps live under Other products.

Jump to six-pillar guide · Open workspace setup

Governance reference

How the six pillars work

MSGF V3.0 defines what each pillar means; V3.2-ULTRA runs them through SWEEP → PERSIST. Use this guide when wiring Pulse, ingest, or reading your dashboard stoplights.

V3.2-ULTRA pipeline

SWEEP
SHARD
DEFEND
CROSS-REF
CONVERGE
ARBITRATE
PERSIST

P1DEFEND

Static Ledger

Immutable rules, legal versions, security HALT

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.

P2CONVERGE

Flow Sequence

Gate orchestration & deployment 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.

P3SHARD (identity)

Entity Profiles

Roles, tiers, tenant identity

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 (license key or session). Map your app's org/user id to x-msgf-entity-id and tenant headers; keep billing in MSGF or mirror Stripe webhooks into p4_profiles.
How to use it: Complete checkout or starter credits on sign-up. For API integrators, mint msgf_live_… and pass Authorization + x-msgf-tenant-id on every Pulse call.

P4SHARD

State Ledger

Session beats, HAL telemetry, hot slices

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.

P5SWEEP

Local Variables

Tenant UI shards & module context

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.

P6CROSS-REF / PERSIST

Constraint Ledger

Vault vs Hall, lineage 1.1.1

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

Create your account