/profiles

Profiles

What a profile is

A profile is a configured GARP system for a specific domain or use case. It defines which objects exist, what counts as admission, which sources are recognized, which review actions gate promotion, and what export formats are produced for downstream readers. Two organizations with different review workflows produce two different profiles even when both follow the same protocol, because the admission boundary and the labels around it are domain-specific while the underlying primitives are shared.

Five named profiles

Counterpose Profile

For contested public knowledge and publication. Claims enter as candidates, require source support and a review action before promotion, and become records that can be disputed, revised, superseded, or withdrawn through subsequent governed events. Counterpose at counterpose.org is the standalone publication platform built on this profile, and the first public platform using governed analytical records as its underlying object model. Counterpedia is a separate read-and-render surface that generalizes the public-reader grammar across profiles, so the same renderer components work for Counterpose-shaped signals and for records under any other GARP profile.

Coursework Triage Profile

For grading worklists, rubric-backed evidence packs, and professor review. Routes student submissions into review queues and preserves the basis for every routing decision, while keeping machine assistance separate from human grading authority. Used in the GARP Rubric demo.

Legal File Profile

For claims, exhibits, filings, disputes, and audit chains tied to a specific matter. Each filing becomes a record with custody state, lineage, and procedural metadata, suitable for matter archives, administrative dockets, and procedural workflows where untracked edits are not acceptable.

ARCS Anchor Profile

For document capture, canonical entity linking, logical-record assembly, and watched import folders. Operates as the custody substrate beneath higher-level GARP profiles and pairs with the ARCS record custody standard at arcsstandard.org.

Research Corpus Profile

For institutional research, source verification, and governed synthesis. Used by organizations that produce reports, briefings, or technical analysis from reviewed sources and need every claim in an output to trace back to an admitted record.

Starter profile shape

A profile is declarative configuration. The shape below is illustrative of the Counterpose publication profile and is not a complete schema; the canonical schema and validator live at garp.tools.

yaml

profile_id: counterpose_publication
objects:
  - source
  - claim
  - candidate_record
  - evidence_pack
  - record
  - response
  - digest
admission_boundary:
  requires:
    - cited_source
    - review_action
    - governance_state
export_formats:
  - markdown
  - pdf
  - json

How profiles relate to implementation

The profile YAML is the configuration that binds a GARP system to a domain. The Profile SDK that loads, validates, and binds it to a workbench and source registry lives at garp.tools alongside the schemas, validators, and command-line references that operate against profile files.