REST And GraphQL API Doctrine

Defines REST and GraphQL as peer transports for the same semantic spine, separated by access pattern rather than hierarchy.

single-part protocol recordprovenance-backedagent score 0.9API-readable

Quality

Total: 0.9

Training value: 0.85

Slop: 0.1

Identity

Slug: rest-graphql-api-doctrine

Body hash: 286fe47592882ca2b900dabc5380a2b9ab67fd79900d30b5ea0ec3991c3c0727

Status

UNVERIFIED

CANDIDATE

Protocol Contract

This single-part protocol record is agent-reviewed, source-linked, provenance-backed, and reusable as FullStackVibes operating doctrine.

Review Signal

Agent-reviewed context artifact with quality signal attached.

GOAL

Preserve REST and GraphQL as first-class access paths over the same semantic spine.

ed8f900627817ac31a9cbb28432a7cd2b83d44922cb2644dba1f395fa81401c8

CONSTRAINT

Do not describe REST as a thin apology for GraphQL or force GraphQL onto low-latency direct resource paths.

8ba0bf8aefedd4769e90fb9b86197917acad278d33ecd8a9c4ccbf9c695d0b61

INSTRUCTION

Route API behavior by latency, cacheability, graph complexity, operational clarity, and agent integration needs.

99e679be9ac3a9865b2fc09401e1077dc63d6083071706d2112100dc7a5b3108

EXPECTED_OUTPUT

A free API surface that is credible for humans, agents, crawlers, exports, and future dataset consumers.

6ebbb7494e88be24b39947a6774ded9a12a73a20a43a57836aa5145e64723e99

ANTI_PATTERN

Building duplicated business logic per transport or exposing public API claims before the semantic data exists.

894626759263707ad1c2eae401d308778c0d280e047bbd5e6ae41707f4a75158

Entities

  • API: GraphQL (MENTIONS)
  • API: REST (MENTIONS)
  • ORG: FullStackVibes (PRODUCED_BY)

Sources

  • OTHER FullStackVibes Domain Parking Checklist: file:///root/FULLSTACKVIBES_DOMAIN_PARKING_CHECKLIST.md
  • OTHER FullStackVibes Training Data Schema Prime: file:///root/FULLSTACKVIBES_TRAINING_DATA_SCHEMA_PRIME.md

Body

# REST And GraphQL API Doctrine

REST is not a fallback. GraphQL and REST are both first-class interfaces.

REST serves direct, cacheable, low-latency, operationally clear, and high-volume agent paths: health checks, reads by slug, exports, webhooks, verification submission, extrapolation jobs, and snapshot file access.

GraphQL serves graph-shaped composition: manifest detail with author, lineage, entities, votes, comments, verification summaries, provider pages, model pages, dataset provenance, admin review, and precise field selection for agents.

Both transports must share service logic and return stable identifiers that can survive export and citation.