A Real .gram History Walkthrough
이 상세 자료는 아직 한국어로 번역되지 않아 영문 원문을 표시합니다.
GA 공개 출처와 지원 범위
- Status
- GA
- Component
- .gram format / Gram Core
- Deployment
- n/a (format spec)
- Applies to version
- Latest
- 출처 확인일
- 2026-10-25
- Owner
- thegram-one/thegram-format
- Public evidence
- Basis
- 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.
All pages: version and status matrix
출처 확인은 실제 계정 설치·기기 동작·서비스 상태의 검증을 뜻하지 않습니다.
Compare the actual initial and current states
Section titled “Compare the actual initial and current states”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
Section titled “Initial state: revision 0”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 to see the proposed decision as it appeared in that state.
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.
Current projection: revision 1 (current)
Section titled “Current projection: revision 1 (current)”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.
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.
Evidence: Reviewed the example change
A fictional teaching record added to demonstrate an explicit supports relation; not a real review result.
Validate the downloaded source
Section titled “Validate the downloaded source”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
Section titled “What this example does not prove”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.
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
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
Source: Fictional example disclosure
The review scenario is invented for instruction and is not real operational evidence.
Source and renderer 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
Canonical source: history-walkthrough.gram