GARPedia

Synthetic Demo: Rubric Consumer Rendering Rationale

Fixture-backed external consumer example showing a rubric-style product consuming a GARPedia page model without real student data, grades, or live integration.

Governed record · Edition 1 · Updated 2026-05-08

RecordSourcesRefusalsHistoryMachine

External consumer posture

This synthetic record shows a rubric-style consumer rendering GARPedia page-model posture as an external application primitive. The consumer reads record identity, source references, citation posture, object lint posture, receipt posture, and bundle references from committed fixtures rather than calling a live grading service.1

Rationale shape

The rationale is criterion-level and synthetic: it names the evidence trail a reader would inspect, but it does not assign a grade, identify a learner, name an institution, or reproduce real coursework. The page model therefore demonstrates rendering posture without becoming a grading authority.2

Fixture boundary

The consumer fixture links to the page-model JSON and portable export bundle as static public artifacts. It does not import garp-rubric, does not fetch from garp-local, does not authenticate a user, and does not mutate reviewer disposition.3

Technical details
record id
SYN-REC-RUBRIC-CONSUMER-0001
current edition
SYN-RUBRIC-CONSUMER-ED-0001

  1. Synthetic Rubric Q: Public Criteria for Rationale Rendering

    Fictional rubric criteria used to demonstrate an external consumer rendering a GARPedia page model without importing garp-rubric.

    • “External consumers can render a governed page-model relationship by reading fixture-backed record identity, source posture, citation posture, lint posture, and export references.”
    Technical details
    source id
    SYN-SRC-0040
    capture hash
    SYN-RUBRIC-CONSUMER-SPAN-0001
    SYN-RUBRIC-CONSUMER-FRAG-0001 · verbatim_verified

  2. Synthetic Practice Response Shell R: De-identified Fixture

    Fictional practice-response shell with no student identity, school identity, submission text, or grade.

    • “A rubric-style rationale fixture may describe criterion-level evidence posture without assigning a real grade, identifying a learner, or reproducing a real submission.”
    Technical details
    source id
    SYN-SRC-0041
    capture hash
    SYN-RUBRIC-CONSUMER-SPAN-0002
    SYN-RUBRIC-CONSUMER-FRAG-0002 · normalized_verified

  3. Synthetic Report S: External Consumer Export Contract

    Fictional report describing how a downstream product can consume page-model and bundle references as fixture metadata.

    • “A portable bundle reference is a static export fixture; it is not a live integration contract, network fetch, or authorization boundary.”
    Technical details
    source id
    SYN-SRC-0042
    capture hash
    SYN-RUBRIC-CONSUMER-SPAN-0003
    SYN-RUBRIC-CONSUMER-FRAG-0003 · verbatim_verified

This record declined to admit the candidate. A refusal is not a finding that the opposite claim is true, and does not establish that this claim is false.

Every candidate this record evaluated was admitted.

This record carries no governed lifecycle history to display.

Public projection

Machine-readable projections of this same governed record. A bundle appears here only when the public SDK supports it; committed demonstration fixtures are listed separately below and are not supported artifacts.

Page model
JSON

This record has no supported portable export bundle. The public GARPedia SDK supports one bundle format, and only records carrying a claim lifecycle with a separately owned verification report produce it.

Demonstration and historical artifacts

Not supported machine artifacts. The file below is a committed demonstration fixture, kept reachable for inspection and reproducibility. It declares the fixture bundle format, which the public client and the MCP adapter both refuse with a typed unsupported-format result. Reachability is not support.

Demo / historical fixture bundle (unsupported)
Unsupported demonstration fixture JSON

Verification artifacts

No committed verification report is attached to this record.

Verification workbench →

For developers →