Skip to main content
The proof engine lives in packages/core/src/proof/engine.ts.

​
Proof Creation

A proof is created whenever a quest is completed. The proof type depends on how the completion was initiated:
Completion PathProof Type
grindxp completeself-report
grindxp stopduration
Forge: timer sessionduration or multi-proof
Forge: git signalgit-commit
Forge: file watcherfile-change
Forge: process detectorprocess-check
Forge: calendar webhookcalendar-match
Manual with screenshotscreenshot
Companion AI analysisai-verify
Multiple signals combinedmulti-proof

​
Multi-Proof Aggregation

When the Forge detects multiple signal types for the same quest completion window, it upgrades to multi-proof automatically: 
const proofType = signals.length > 1 ? "multi-proof" : signalToProofType(signals[0]);
This is the highest-multiplier proof type (1.5x) and is earned by having your environment verify your work.

​
Proof Data

Each proof record stores the raw evidence: 
type ProofData = {
  type: ProofType;
  // for git-commit
  commitHash?: string;
  commitMessage?: string;
  repoPath?: string;
  // for file-change
  filePaths?: string[];
  // for duration
  startedAt?: number;
  stoppedAt?: number;
  durationSeconds?: number;
  // for process-check
  processName?: string;
  // for screenshot
  imagePath?: string;
  // for ai-verify
  verificationNote?: string;
  // for calendar-match
  calendarEventId?: string;
  // for multi-proof
  sources?: ProofType[];
};

​
Validation

validateProof(proof) checks that required fields are present for the given proof type. Invalid proofs fall back to self-report (1.0x) rather than rejecting the completion.

​
Multiplier Lookup

import { proofMultiplier } from "@grindxp/core/proof";

const multiplier = proofMultiplier("git-commit"); // → 1.3