Skip to content

Update almanac.md #283

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 28, 2023
Merged

Update almanac.md #283

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/almanac.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,8 +14,8 @@
## Overview

An almanac collects facts through an engine run cycle. As the engine computes fact values,
the results are stored in the almanac and cache'd. If the engine detects a fact computation has
been previously computed, it re-uses the cache'd result from the almanac. Every time ```engine.run()``` is invoked,
the results are stored in the almanac and cached. If the engine detects a fact computation has
been previously computed, it reuses the cached result from the almanac. Every time ```engine.run()``` is invoked,
a new almanac is instantiated.

The almanac for the current engine run is available as arguments passed to the fact evaluation methods and
Expand Down