/method
GARPedia treats method as a renderer-time concern. Where an underlying record was admitted, reviewed, and promoted through the GARP SDK, the public renderer surfaces the rules and posture under which the record was rendered, in plain view, alongside the canonical body and the audit chain. The method pages below are the institutional explainers for the three dimensions of that surfacing: when a record is publication- eligible, how projection records compress and what they declare lost, and how structural density and transparency posture appear on each record page.
Each record's MethodPanel renders a per-record summary; this surface explains the moving parts in one place so the per-record summary stays short. The reverse-wiki page below is the conceptual frame for the rest: it explains why the page is a projection of an admitted record rather than an editable store, and the other pages describe specific dimensions of that projection.
/method/ecosystem-method-map
Where GARPedia sits in the GARP ecosystem: the operating claim that GARP separates AI assistance from institutional record admission, the existing spine of named surfaces and their roles, the custody/render/operator owner triad behind every public projection, and the one FSI proof path GARPedia represents. No new spine, no model-truth claim, no public admission mutation.
/method/reverse-wiki
What a reverse wiki is as a read surface: knowledge that is admitted, projected, and agent-readable rather than editable in place, the custody, render, and operator owner triad, and the boundaries this surface does not claim past.
/method/publication-eligibility
What it means for a record to be publication-eligible at render time, which fields participate in the check, and why eligibility is a deterministic check rather than an approval workflow.
/method/projection-records
What a projection is, how compression and known-loss fields are recorded, and why reversibility to the source record is preserved as an explicit field rather than assumed.
/method/structural-density
How the renderer surfaces structural density, why discovery posture is a metadata field rather than an indexer configuration, and how the no-hidden-ranking grammar applies on a public read surface that does not run search or retrieval.
/method/counterpose-bridge
What the Counterpose-to-GARPedia eligibility bridge is, what the artifact carries, how eligible and blocked artifacts differ, a compact registry over the synthetic fixtures, and how the bridge differs from the separate static path that republishes captured Counterpose editorial.
/method/projection-bundles
What a public-safe projection bundle is as a read surface: the record and page-model references, the custody, render, and operator owner triad, the public/private boundary, the readiness posture, and how the eligible and blocked synthetic fixtures differ.
/method/closing-the-loop
The synthetic path from an external agent session through tool-call disposition, connector receipt consistency, an AgentOutcomeObject, the CandidateClaim bridge, scenario_id correlation, and Workbench scenario traversal to the GARPedia public projection boundary. GARP separates AI assistance from institutional record admission: submitted means routed to the candidate/admission seam, not admitted.
/method/trace-context-bridge
Public-safe comparator for the trace-context-can-propose, substrate-decides boundary: trace context can propose a bridge candidate; the substrate decides what becomes a governed record. Names the SDK, local, Workbench, ops, arcs-amnesiac, and GARPedia owner split without rendering private trace payload, running MCP traffic, or claiming admission.
/method/amnesiac-spine
Public-safe method explainer for the Amnesiac memory spine demo: canonical artifacts in arcs-amnesiac, the product-facing showcase page, the direct static viewer path, artifact-hash pinning, and the GARPedia explanation boundary. It does not embed the viewer, run retrieval, call a model, admit records, render private corpus material, or claim a receipt chain.
/method/workspace-memory-index
Public-safe comparator for consumer memory versus substrate-admitted memory: consumer memory stores what the agent says, while GARP stores what the substrate admits. Names the SDK, local, Workbench, ops, arcs-amnesiac, and GARPedia owner split without rendering private workspace memory or claiming admission.
/method/projection-readiness
The public-safe reporting posture for whether a projection path is ready, blocked, held, unavailable, or not_authorized, plus the malformed diagnostic posture for an untrusted response or descriptor. Names the owner triad: garp-local owns the read-model substrate, garp-workbench owns operator rendering and cockpit display, and garpedia_org owns the public explanation and projection grammar. Projection readiness is not admission, does not verify model output, does not lift renderer authority, does not authorize publication by itself, and does not mutate public admission state.
/method/reverse-wiki-function-inventory
A custody/render/operator map of the named reverse-wiki functions. Each row assigns custody owner, render owner, operator owner, status, blockers, next action, and the exact public claim allowed and forbidden for that function. This inventory names what each reverse-wiki function does and what it does not claim. It is not a roadmap. It is a custody/render/operator map of the current product surface.
/method/context-io-governor
Public-safe explainer for the Context I/O Governor: an authority layer for governed context, not just a second brain or memory UI. It governs the context lifecycle — intake, routing, derivation, packet compilation, projection, and refusal boundaries — over a finite window where hidden cuts would otherwise be invisible. It records routing states — blocked, redirected, allowed_inline, allowed_derivation, requires_operator_review — with byte accounting, under security_boundary_claim: none. The MVP loop is now closed and guarded: the garp-sdk producer emits live-sink-shaped records, garp-local projects them as origin=live, the garp-workbench inspector surfaces the projection, and a garp-ops conformance gate guards cross-repo name/enum/projection alignment. The disposition is an exposure/disposition report: routing is not truth, inclusion is not admission, exclusion is not falsity, truncation is not falsity or irrelevance, and packet compilation is not a canonical receipt. origin=live is not a production-readiness claim, the conformance gate verifies alignment only, the Workbench is an inspector not the authority boundary, and storage is not custody.
/method/mcp-receipt-pack
Public-safe explainer for how an external, vendor-neutral SRS receipt pack is verified, worked from the vendor-neutral MCP audit-trail receipt pack (garp-receipt-conformance PR #7, commit 3e2fe99, packs/mcp-audit-trail/v0.1/). It walks the four explicit inputs — input bytes, expected receipt bytes, the canonical SRS envelope schema (pinned digest e866eabf…d6b61), and byte-for-byte expected validator output — and the pack-local check.sh that regenerates the receipt byte-identically with a deterministic adapter, confirms the receipt binds the input sha256, validates the valid fixture (exit 0), and rejects the invalid drift fixture (exit 1, TOP_LEVEL_BODY_VERDICT). Verification is structural and cryptographic only: it does not prove truth, admit a record, certify compliance, or assert live integration. The envelope holds Option A — no top-level receipt_class, receipt_type provenance, and boundary_type audit_trail_boundary as a pack-local descriptive value under the open-string boundary_type posture settled in PR #8 (commit 72e3a18), not a canonical boundary_type; body under extensions.garp.body, decision_ref never a top-level verdict. PR #9 (commit bf5ca67) is the first vendor-specific instantiation — the Bedrock/OpenAI explicit-file pack at packs/bedrock-openai-audit/v0.1/ — reusing the proven shape and not verifying model output; future AWS/Microsoft AGT packs should clone that pattern, not invent new receipt shapes.
GARPedia does not adjudicate disputes, run review or publication approval workflows, host operator controls, or execute search and retrieval on this surface. Adjudication and governed action live in the GARP Workbench (operator) and in the underlying GARP SDK. The method pages here describe how render time appears to a reader, not how upstream governance decisions were made.
/method/mcp-record-custody-gateway
Public-safe explainer for the refs-only Gateway custody inspection stack. It separates custody posture from MCP execution, connector execution, record admission, receipt persistence, model-output verification, protocol modification, and MCP authority grant.