PROOFLANEOPERATOR SURFACE

Prooflane Operator

Quick-start operator surface.

Drafted Apr 8, 2026

START HEREOpen the active decision, verify the current state, and complete the next valid action.
HUMAN WORKFLOWPropose decision, then accept decision, then record decision, then verify the record.
SURFACE MAPInbox shows what changed. Decision pages show the next workflow write. Record pages show durable truth. System links the same chain across surfaces.
CHANGEDPROPOSED
MEANINGDecision created but not approved.
WHAT NOWAccept this decision.
OPEN INBOXCREATE DECISIONVERIFY RECORDS

Open the active decision, verify the current state, and complete the next valid action.

Decisions, records, inbox, and operator are different views of the same workflow.

OPERATOR DIRECTIVE CONSOLEASSIST MODE ONLINE
MISSIONKeep the business moving with verified truth. Every action should end in a record you can inspect and verify.
QUICK COMMANDS1) Open Inbox, 2) Resolve critical attention, 3) Create next decision, 4) Verify latest record.
CHANGEDACCEPTED
MEANINGDecision approved but not final.
WHAT NOWMove from inbox to decisions to records without skipping the next valid surface.
RUN COMMAND 1RUN COMMAND 4
FOUNDER PATHCHECKING
WAITChecking whether the app is ready.
OPEN INBOXOPEN SYSTEMCREATE DECISIONOPEN RECORDS

This surface is an operator guide, not a separate product. Use it to move through inbox, decisions, records, and system without guessing what comes next.

In Prooflane, the MCP layer should expose your existing backend contract: actors, policies, decisions, acceptances, records, record verification, and desk navigation.

The assistant persona is not “news brief me.” It is “show me what is real, who authorized it, and whether the record verifies.”

  1. i.

    Architecture

    Microphone or console input -> STT -> LLM operator prompt -> Prooflane MCP server -> existing Next API routes and record utilities.

    The voice layer is optional. The MCP layer is the actual product surface.

  2. ii.

    Tool Surface

    Core tools: `list_actors`, `list_policies`, `list_decisions`, `get_record`, `verify_record`, `accept_decision`, `create_record`, `list_record_edges`, `open_prooflane_desk`.

    Every tool should map to a real Prooflane action already modeled in the repo, not a demo-only side capability.

  3. iii.

    Behavior

    The operator should stay concise, apply Mentor/Opposing/Delulu as prompt modes when useful, and refuse to collapse proposal, acceptance, and recordation into one ambiguous step.

    If a user asks “did this actually happen?”, the default path is: find the record, inspect the acceptance chain, verify the hash, and then answer.

  4. iv.

    Repo Fit

    This repo already contains the canonical Prooflane backend. The right first deliverable is a Prooflane MCP package that wraps the current `app/api/*` surface and `lib/records.ts`, not a blind copy of the Friday demo.

    The implementation spec lives in `docs/prooflane-operator-v1.md`.

PROOFLANEPROGRAMSSYSTEMRECORDSMEMORANDUM