Observations
Record the stated conditions before the layout note
Put each figure from the page on its own line. Do not mix in a preference.
x.ai published this account (2026-09-16): Grok Build writes conventions, decisions, and project facts after each turn and reloads them in later sessions via markdown notes, /memory, and /dream.
This guide uses that public page as the example. This site did not run the test, close the deal, or measure the product.
Write only what the page says
The page's claim is: Grok Build writes conventions, decisions, and project facts after each turn and reloads them in later sessions via markdown notes, /memory, and /dream.
Put the URL under that sentence. If a later recap adds a number or a date, keep the original page as the record.
Put each figure from the page on its own line. Do not mix in a preference.
Do the site's check on this one page. Fill a line only when the page supports it. Where the page is silent, write Not stated.
A finished note names the page, the date, and the limit of the claim. It does not borrow a result from a different story.
Stop at the untested line
Anything you did not open, install, or count stays untested. Leave that line visible.
Source page: Grok Build adds persistent project memory.