Examples
A Real .gram History Walkthrough
Follow one .gram document through actual Core history, compare recorded states, and validate the downloadable source rather than treating a revision label as decoration.
Explore as .gram
Start with the initial state
This teaching document begins at its actual Core revision 0. The decision below is proposed in this initial state. No evidence record is present yet, so this revision embeds only records that already exist.
The revision 0 decision
Inspect the decision record in the initial replay. Its status is proposed. The example is fictional and illustrates a document state, not a real product decision or review.
Fictional teaching decision. Its status changes in a later Core patch so the document journal records an actual before/after state.
Read history with Core
A current read returns the current body; it does not replay history. Use Core's state operation with a revision selector to reconstruct a historical state, and record the resolved revision identity returned by Core. Change discovery is incremental from a cursor, while a range query is bounded and is not a complete replay.
The source records below define the format, state-selection contract, and fictional-example boundary.
Current Core history format and source replay behavior; Core generates the journal.
https://github.com/clab-one/thegram-format/blob/main/spec/source-history-render.mdHistorical state selectors and selected revision identity; see the current gram_state contract.
https://github.com/clab-one/thegram-format/blob/main/native/temporal.rsThe review scenario is invented for instruction and is not real operational evidence.
What this example does not prove
The scenario is fictional. It does not demonstrate synchronization to Vault or Drive, account permission, cryptographic authorship, external reproduction, or application-wide feature availability. A successful Core audit establishes that the source passes that Core's history validation; it does not establish where the file came from.
sha256:6cfd407a855bf5ffefff3d9f77356b27b9d83ab876af485ecc4c5f8589750ae6@gram 2
doc blog-history-walkthrough
t A Real .gram History Walkthrough
d Follow one .gram document through actual Core history, compare recorded states, and validate the downloadable source rather than treating a revision label as decoration.
tag examples
view document
::rich
# Start with the initial state
This teaching document begins at its actual Core revision 0. The decision below is proposed in this initial state. No evidence record is present yet, so this revision embeds only records that already exist.
## The revision 0 decision
Inspect the decision record in the initial replay. Its status is proposed. The example is fictional and illustrates a document state, not a real product decision or review.
[[decision-history-example]]
## Read history with Core
A current read returns the current body; it does not replay history. Use Core's state operation with a revision selector to reconstruct a historical state, and record the resolved revision identity returned by Core. Change discovery is incremental from a cursor, while a range query is bounded and is not a complete replay.
The source records below define the format, state-selection contract, and fictional-example boundary.
[[src-core-history]]
[[src-state-api]]
[[src-fiction]]
## What this example does not prove
The scenario is fictional. It does not demonstrate synchronization to Vault or Drive, account permission, cryptographic authorship, external reproduction, or application-wide feature availability. A successful Core audit establishes that the source passes that Core's history validation; it does not establish where the file came from.
::end
D decision-history-example
t Require a review before accepting an example change
d Fictional teaching decision. Its status changes in a later Core patch so the document journal records an actual before/after state.
x proposed
source src-fiction
SRC src-core-history
t Core History/6 and replay contract
d Current Core history format and source replay behavior; Core generates the journal.
ref https://github.com/clab-one/thegram-format/blob/main/spec/source-history-render.md
SRC src-state-api
t Core state-selection API
d Historical state selectors and selected revision identity; see the current gram_state contract.
ref https://github.com/clab-one/thegram-format/blob/main/native/temporal.rs
SRC src-fiction
t Fictional example disclosure
d The review scenario is invented for instruction and is not real operational evidence.