Repository navigation
docs: state the engine's value model in AGENTS.md - #5133
Conversation
Co-authored-by: tembo[bot] <208362400+tembo-io[bot]@users.noreply.github.com>
|
Size (brotli, eager entry chunk)
|
Coverage Report for CI Build 44796213173Coverage remained the same at 79.459%Details
Uncovered ChangesNo uncovered changes found. Coverage RegressionsNo coverage regressions found. Coverage Stats
💛 - Coveralls |
Merging this PR will improve performance by 31.6%3 warnings
Performance Changes
Tip Curious why performance improved? Comment Comparing Footnotes
|
Summary
Adds one section to
AGENTS.md, under Engineering Standards: the engine's value model. It says what a node in the signals engine may store, which no single rule states and which lived only in discussion #3905 and the internals log, where fixing agents are not told to look.The model, as ruled on 2026-11-20:
isPendingis for data: an app shows work in flight with its owncreateOptimistic(false)flag or withaffects(); the engine does not add state so a guess can come back or announce itself.covers' covered value,kept,screens) are named as debt, not precedent.Why now. Between 2026-11-10 and 11-20, 90 fixes landed in
packages/signals/src; 84 changed no rule, scenario row or seat-table row. Two of the three extra stores came from such fixes (keptwith #4337,screenswith #4779), each for one scenario, neither reviewed against this model because the model was not written down. A census over the signals and web suites shows a node at rest holds a value beyond the model in only two tested situations, and one of them (#4336's give-back) was never reported by a user.Docs only. No source, test or behaviour change, so no changeset.
How did you test this change?
Nothing to run: one Markdown file. Checked that every rule id cited in the new section (F-1, F-2, F-6, F-11, D-33) stands in
RULES-FUNDAMENTALS.md/RULES-DERIVED.md, and that the three stores named exist at the paths given onmain@ 99db9bc.