---
title: A Real .gram History Walkthrough
description: Follow one .gram document through actual Core history, compare recorded states, and validate the downloadable source rather than treating a revision label as decoration.
url: https://docs.thegram.one/ko/examples/history-walkthrough/
lang: en
requested_lang: ko
fallback_from: https://docs.thegram.one/examples/history-walkthrough/
tier: current
status:
  component: .gram format / Gram Core
  deployment: n/a (format spec)
  applies_to_version: Latest
  status: GA
  last_verified: "2026-10-25"
  owner: thegram-one/thegram-format
  public_evidence:
    - https://thegram.one/gram-file/
  rationale: The public .gram overview confirms revision history is retained in the file; the walkthrough’s specific replay fixture is an example, not a current Core release claim.
source: https://docs.thegram.one/sources/history-walkthrough.gram
date_published: "2026-10-12T23:28:28.114Z"
date_modified: "2026-10-12T23:29:19.986Z"
evidence:
  Canonical source SHA-256: da7787bf7496021b1879d841823dd1337004bd853604ef78b916f1f80352ead0
  Selected revision: r1 · sha256:d6d8d1a74772f93ee3358e547c510f0d4ee11f6500d813f40dc0d7452e3ccf13
  Local renderer: configured local Thegram renderer · API thegram-web-render/1
  Core source: git+https://github.com/clab-one/thegram-format.git?rev=b16489e1d0d77d38f82d2f61776524737aa31557#b16489e1d0d77d38f82d2f61776524737aa31557
---

# A Real .gram History Walkthrough

<div class="gram-doc-anchor" id="e0-blog-history-walkthrough"></div>

## Compare the actual initial and current states {#h0-1}

Core revision 0 contains the proposed decision and no evidence record. Core revision 1 changes that same decision to accepted and adds the fictional evidence record with an explicit supports relation. These are the actual states replayed from this document's native History/6 journal.

### Initial state: revision 0 {#h0-3}

Replay revision 0. The decision status is proposed; the evidence record is absent. This initial source embeds only records present at revision 0.

[Open the revision 0 snapshot](/examples/history-walkthrough/revisions/0/) to see the proposed decision as it appeared in that state.

<div class="gram-record" id="e0-decision-history-example" data-record-type="decision">

**Decision:** Require a review before accepting an example change · *Accepted*

Fictional teaching decision. Its status changes in a later Core patch so the document journal records an actual before/after state.

</div>

### Current projection: revision 1 (current) {#h0-6}

The current projection below shows the same decision as accepted at revision 1, with the fictional evidence record and its supports relation. The evidence is teaching material, not a real review result.

<div class="gram-record" id="blog-history-walkthrough-e0-decision-history-example-2" data-record-type="decision">

**Decision:** Require a review before accepting an example change · *Accepted*

Fictional teaching decision. Its status changes in a later Core patch so the document journal records an actual before/after state.

</div>

<div class="gram-record" id="e0-evidence-history-example" data-record-type="evidence">

**Evidence:** Reviewed the example change

A fictional teaching record added to demonstrate an explicit supports relation; not a real review result.

</div>

### Validate the downloaded source {#h0-10}

Use this page's Download source action to save the canonical .gram file. Its History/6 journal is part of the download; the HTML page is only the current rendered projection. Audit the downloaded file with Core, then call gram_state for revision 0 and revision 1 and compare the decision status, evidence record, and relation. Report the revision identity returned by each state selection; do not treat a current gram_read as historical replay.

For an MCP client, gram_state selects one revision by path and exactly one revision, recorded-time, or effective-time selector. It returns the selected revision identity and resolved state. gram_read reads the current body; it does not replay history. Use the exact downloaded path.

A historical revision is read-only. To make a change based on earlier information, update current state with a new CAS-protected operation. Do not rewrite old journal entries or paste earlier bytes over the current document.

### What this example does not prove {#h0-14}

The scenario is fictional, and its example decision is only a teaching record. It does not demonstrate synchronization to Vault or Drive, account permission, cryptographic authorship, external reproduction, or application-wide feature availability. A successful local Core audit establishes that the downloaded bytes pass that Core's history validation; it does not establish where the file came from.

<div class="gram-record" id="e0-src-core-history" data-record-type="source">

**Source:** Core History/6 and replay contract

Current Core history format and source replay behavior; Core generates the journal.

Reference: [https://github.com/clab-one/thegram-format/blob/main/spec/source-history-render.md](https://github.com/clab-one/thegram-format/blob/main/spec/source-history-render.md)

</div>

<div class="gram-record" id="e0-src-state-api" data-record-type="source">

**Source:** Core state-selection API

Historical state selectors and selected revision identity; see the current gram_state contract.

Reference: [https://github.com/clab-one/thegram-format/blob/main/native/temporal.rs](https://github.com/clab-one/thegram-format/blob/main/native/temporal.rs)

</div>

<div class="gram-record" id="e0-src-fiction" data-record-type="source">

**Source:** Fictional example disclosure

The review scenario is invented for instruction and is not real operational evidence.

</div>