/examples

Examples

Intro

Each system below uses the GARP model documented at GARPedia, with implementation materials hosted at garp.tools. The systems differ in domain, profile, and admission boundary, while sharing the same underlying primitives: sources, captures, fragments, claims, candidates, evidence packs, review actions, records, governance state, audit events, and digests. The variation across them is configuration; the substrate is shared.

Counterpose

A standalone publication platform for contested knowledge, and the first public platform using governed analytical records as its underlying object model. Counterpose uses GARP records, source capture, review events, and publication boundaries to make analytical claims durable, inspectable, and contestable in public. GARPedia is a separate read-and-render surface that generalizes the public-reader grammar across profiles, so the surfaces named below appear in their full Counterpose form on counterpose.org and in a profile-neutral form across the GARPedia renderer.

Surfaces visible to a reader: governed article pages, source panels, claim lineage, dispute panels, revision history, digest and export packets, and publication boundary indicators that signal whether a page is currently in dispute, under revision, or stable.

GARP Rubric

A governed coursework triage system that routes grading work without silently grading students. Preserves the basis for every routing decision and keeps machine assistance separate from human grading authority, demonstrating that a non-publication profile can use the same primitives as Counterpose with a different admission boundary and a different review surface.

A synthetic external-consumer walkthrough at /examples/rubric-consumer shows a rubric-style product consuming GARPedia page-model and export-bundle fixtures without importing garp-rubric, calling a backend, or rendering real student material.

ARCS Anchor

A governed memory substrate for importing documents, linking entities, and preserving provenance through capture, hash, and derivation events. Operates as the capture layer beneath domain profiles and pairs with the ARCS record custody standard, providing the entry point through which sources, captures, and fragments become available to higher-level profiles.

Legal File System

A local case-file profile for claims, exhibits, timelines, and filing support. Treats every procedural artifact as a governed record with custody state, lineage, and review history, suitable for solo practitioners, in-house counsel, and matter-archive workflows that need provenance and audit chains rather than untracked edits in shared folders.

Research Corpus

A profile for institutional research, source verification, and governed synthesis. Used by organizations that produce reports, briefings, or technical analysis from reviewed sources, where every claim in an output traces back to an admitted record. Distinct from Counterpose in that publication is internal rather than public.

Countervail / Expose

Assessment and forensic reporting surfaces built around governed evidence records. Countervail provides professional services and conformance assessment outputs; Expose is the diagnostic instrument that produces governed evidence packs as input. Used in audit, diagnostic, and conformance engagements where the evidence chain matters as much as the conclusion.

Read-only renderer walkthroughs

Annotated, synthetic, read-only walkthroughs of the GARPedia renderer, framed for a non-technical reader.

  • Anatomy of a claim

    What was refused stays visible. The same idea at two layers: a publication layer's human editorial judgment, and an engine layer's mechanical refusal with proof attached.

  • Counterpose-shaped signal

    A synthetic Counterpose-shaped signal rendered through the GARPedia renderer: status, editions, amendment narration, and the provenance rail.

  • Reverse-wiki record

    The same renderer on a profile-neutral record, so you can see which surfaces are Counterpose-specific and which generalize.

  • Rubric consumer

    An external-consumer walkthrough showing a rubric-style product consuming GARPedia fixtures without a backend or real student material.

  • Reading an SRS receipt

    One synthetic SRS receipt read four ways: the authoritative JSON envelope, the ARCS plain-language reading aid, the GARP body-kind reading aid, and the conformance check.

What "examples" means here

Each system above is a profile plus a UI surface. The profile defines the domain rules, the UI surface presents records to operators or readers, and the shared layer beneath is GARP itself, documented at GARPedia and implemented through references at garp.tools. The systems on this page are examples of the GARP model in use rather than a product catalog from GARPedia.