Skip to content

Commit e68f128

Browse files
authored
📚 Define REPL history in architecture terminology (#879)
1 parent 2d719f7 commit e68f128

1 file changed

Lines changed: 1 addition & 0 deletions

File tree

‎architecture.md‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -31,6 +31,7 @@ and categorization rather than clarify them, so both stay exactly as written.
3131
| replay determinism | the journal doesn't lose the execution chain: replaying arrives at the same state, where execution can continue |
3232
| replay | using the durable journal to restore the recorded portion of a document execution without repeating durable effects; after the recorded entries are consumed, execution may continue live |
3333
| divergence | reserved for replay: a replay that departs from the recorded journal |
34+
| REPL history | the immutable ordered execution records the REPL reads from the durable journal and projects into `ReplModel`; the History surface presents this read model and is not itself a journal |
3435
| middleware | applied by the lexical structure, used by runtime execution |
3536
| workflow run | a workflow being carried out with its progress and outcome recorded durably; document executions perform its work, while ongoing effects remain scoped to the document execution in which they run |
3637
| document execution | one evaluation of a root document initiated through `execute()`, producing one output stream and one completion result while reading and appending a durable journal; its ongoing effects belong to the Effection scope in which the evaluation runs |

0 commit comments

Comments
 (0)