Developer docs

Build with continuity, not just storage.

PRMR Memory Core is plug-in continuity infrastructure. Companies connect PRMR to their AI system or workflow using an API key, client ID, vault, and namespace, then send messy event histories into PRMR.

PRMR turns those histories into smaller continuity packets, reconstructed state, public-safe explanations, least-harm action boundaries, usage logs, reports, and dashboard visibility.

Storage remembers data. PRMR remembers change.

PRMR gives AI systems a continuity layer outside the model. It can make limited context feel wider by giving systems smaller, cleaner continuity packets instead of raw history dumps; it does not increase a model's official context window.

Current evidence combines internal/local tests and controlled hosted API smoke. External validation and production hardening are separate future milestones.

What PRMR is not

A continuity layer, not a replacement for your stack.

not an AI model

not a database replacement

not a vector database replacement

not an official model context-window expansion

not a final decision engine

not production-certified

not bank, compliance, legal, or external security approved

Basic integration flow

From messy history to continuity packet.

Raw events -> PRMR continuity packet -> reconstructed state -> explanation/report -> dashboard visibility.

01Create a client record

02Issue an operator-approved API key

03Create a vault and namespace

04Send scoped messy events

05Generate a continuity packet

06Reconstruct current state

07Request a public-safe explanation or report

08View usage, blocked requests, reports, and memory health in the dashboard

Example use cases

Continuity where context decays.

AI assistant and agent memory continuity

Customer support/user-history continuity

SaaS user-history continuity

Education progress continuity

Legal/research case continuity

Fraud/risk sandbox evaluation

Healthcare/admin case history continuity

Game studio lore/canon continuity

Robotics/agent state history

Enterprise decision logs

Project management memory

Public report preview JSON

{
  "report_id": "rep_demo_001",
  "public_safe": true,
  "summary": "Continuity packet generated for controlled alpha review.",
  "owner_access": "allowed",
  "boundary": "Synthetic/local controlled-alpha evidence only."
}

Local demo integration

V0.55 local demo architecture.

01Browser /demo

02Next.js server-side proxy

03local Python PRMR bridge

04V0.52.1 sandbox / V0.53.1 synthetic fixtures

05public-safe JSON

06frontend cards

This is local-only demo wiring, not production architecture. Browser code calls proxy routes and receives public-safe output only.

Open Local Demo Request Alpha Access

Safety and boundaries

Keep public surfaces public-safe.

Synthetic/demo data only for current local demo

No real sensitive data unless explicitly approved

No final punitive decisions

Restricted diagnostic reports remain server-side

Browser never receives raw credentials

External validation and production hardening are future milestones

Future hosted API notes

Future work, not current claims.

A future hosted service would require separate backend work, security hardening, operational policy, and external review. These items are future milestones, not V0.72.1 implementation claims.

hosted backendclient accountsvaults and namespacescredential issuingusage logsrate limitsdashboardbillingexternal security review

Endpoint reference

Controlled-alpha API shape

These endpoints come from the V0.52.0 alpha contract. They describe the intended controlled-alpha API shape, not a hosted production service.

POST /v1/events/ingest

Public-safe examples

Accept scoped events and store them under a client, vault, and namespace.

Sample request

{
  "client_id": "client_alpha",
  "vault_id": "alpha_vault",
  "namespace": "default",
  "events": [
    {
      "event_id": "evt_demo_001",
      "entity_id": "agent_demo_001",
      "entity_type": "agent_memory",
      "timestamp": "2026-06-20T15:01:00Z",
      "event_type": "state_change",
      "state_before": "new workspace session",
      "state_after": "project preference recorded",
      "signal_type": "preference_origin",
      "status": "active",
      "trust_level": "trusted"
    }
  ],
  "metadata": {
    "dataset_type": "synthetic"
  }
}

Sample response

{
  "ok": true,
  "accepted_event_count": 1,
  "client_id": "client_alpha",
  "vault_id": "alpha_vault",
  "namespace": "default"
}

Use synthetic or explicitly approved datasets only.

POST /v1/continuity/packet

Public-safe examples

Turn scoped event history into a compact continuity packet.

Sample request

{
  "client_id": "client_alpha",
  "vault_id": "alpha_vault",
  "namespace": "default",
  "entity_id": "agent_demo_001"
}

Sample response

{
  "ok": true,
  "packet": {
    "packet_id": "pkt_demo_001",
    "entity_id": "agent_demo_001",
    "current_state": "agent can continue with current project preference",
    "active_signals": ["continuity_ready"],
    "stale_signals": ["outdated_setup_note"],
    "continuity_summary": "Current state preserves active and stale signals for review."
  }
}

A packet is review support, not an automated final decision.

POST /v1/memory/reconstruct

Public-safe examples

Reconstruct useful current state from a continuity packet.

Sample request

{
  "client_id": "client_alpha",
  "vault_id": "alpha_vault",
  "namespace": "default",
  "packet_id": "pkt_demo_001"
}

Sample response

{
  "ok": true,
  "reconstruction_match": true,
  "reconstructable_state": {
    "current_state": "agent can continue with current project preference",
    "active_signals": ["continuity_ready"],
    "stale_signals": ["outdated_setup_note"]
  }
}

Reconstruction verifies continuity state; it does not certify real-world truth.

POST /v1/explain

Public-safe examples

Create a public-safe explanation for review.

Sample request

{
  "client_id": "client_alpha",
  "vault_id": "alpha_vault",
  "namespace": "default",
  "packet_id": "pkt_demo_001",
  "audience": "customer_safe"
}

Sample response

{
  "ok": true,
  "explanation": {
    "summary": "We noticed activity that may need review before continuing.",
    "customer_next_step": "Please confirm whether you recognize the change.",
    "review_boundary": "This is a review step, not a final conclusion."
  }
}

Public-safe explanations avoid restricted diagnostics and certainty-heavy language.

POST /v1/actions/least-harm

Public-safe examples

Return a proportionate next-step boundary.

Sample request

{
  "client_id": "client_alpha",
  "vault_id": "alpha_vault",
  "namespace": "default",
  "packet_id": "pkt_demo_001"
}

Sample response

{
  "ok": true,
  "recommended_action": "request_evidence",
  "allowed_actions": [
    "do_nothing",
    "warn",
    "request_evidence",
    "human_review",
    "keep_dormant"
  ],
  "not_final_decision": true
}

Least-harm output is review-oriented and does not perform final punitive action.

GET /v1/reports/{report_id}

Public-safe examples

Fetch a public-safe report preview when the caller owns the report scope.

Sample request

GET /v1/reports/rep_demo_001
Authorization: Bearer <redacted local alpha token>
X-PRMR-Client-ID: client_alpha
X-PRMR-Vault-ID: alpha_vault
X-PRMR-Namespace: default

Sample response

{
  "ok": true,
  "report": {
    "report_id": "rep_demo_001",
    "public_safe": true,
    "summary": "Continuity packet generated for controlled alpha review."
  }
}

Public report previews must not expose restricted diagnostics.

GET /v1/usage

Public-safe examples

Return scoped usage counts for the authenticated client and vault.

Sample request

GET /v1/usage
Authorization: Bearer <redacted local alpha token>
X-PRMR-Client-ID: client_alpha
X-PRMR-Vault-ID: alpha_vault
X-PRMR-Namespace: default

Sample response

{
  "ok": true,
  "usage": {
    "events_ingested": 4,
    "packets_generated": 1,
    "reports_created": 1,
    "reports_read": 1
  }
}

Usage output is scoped to the caller.

POST /v1/keys/rotate

Public-safe examples

Rotate an active local alpha credential.

Sample request

{
  "client_id": "client_alpha",
  "vault_id": "alpha_vault",
  "namespace": "default",
  "reason": "scheduled_rotation"
}

Sample response

{
  "ok": true,
  "rotated": true,
  "old_key_status": "revoked",
  "new_key_delivery": "show_once_or_out_of_band"
}

The browser should never receive raw credential material.

POST /v1/keys/revoke

Public-safe examples

Revoke an active local alpha credential.

Sample request

{
  "client_id": "client_alpha",
  "vault_id": "alpha_vault",
  "namespace": "default",
  "reason": "manual_revoke"
}

Sample response

{
  "ok": true,
  "revoked": true
}

Revoked credentials must not authorize future requests.

Internal/local evidence

Version timeline

V0.50 Whole Core Truth Gauntlet: PASS
V0.52.0 Alpha API Contract: PASS
V0.52.1 Alpha API Sandbox: PASS
V0.52.2 Sandbox Integrity Audit: PASS
V0.53.1 Demo Replay Pack: PASS
V0.55 Frontend-to-PRMR Local Demo Backend Connection: PASS
V0.72 Client Dashboard MVP: PASS
V0.72.1 Product Value Clarity + Site Utility Rewrite: current docs milestone