You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Review mode for generated output: hold atoms, concept pages and facts until an external check approves them
#8512
Setup. An organisation brain for a small team: one Postgres, a shared company source plus one source per member. Production runs 0.60.466.0; the code paths below were read on current main (0.60.565.0).
The problem. Our rule is that nothing generated reaches readers until a second model has checked it against its origin and screened it for things that must never sit in a shared brain (health, family, pay, contracts, credentials, judgements of named colleagues). Today there is no supported way to hold generated output until such a check passes:
extract_atoms and synthesize_concepts publish what they write straight away. Atom visibility is inherited from the origin page (effectiveVisibility in src/core/cycle/extract-atoms.ts), so atoms from a shared page are readable by every remote caller at once.
A wrapper can only make output private after the fact. In our case unchecked atoms were readable for a short window before the wrapper reached them, so we now hold generation completely.
Facts are private by default, which helps, but we found no supported operation to make a fact readable once it has been checked (we may have missed one).
What we run instead. Each night we restore the daily dump into a local copy, generate there, check every item on the copy, and write only the checked final state back to production. It works, but it costs a full restore per night and rebuilds a publish path outside gbrain.
The idea: a review mode for generation.
A setting such as dream.review: required (per source or per phase). Generated atoms, concept pages and facts are created held: not returned to remote callers, not in search or recall, each with a stable id and its origin pin.
A read operation that lists held items with their origin text, and approve / reject operations (single and batch) that publish or discard them with a receipt. The existing generations machinery (publishManagedAtomGeneration, heldForInput) may be the natural seam.
Idempotency as today: a rejected item is not generated again from an unchanged origin.
Held counts in last_run and brain health, so an operator sees a queue that is not moving.
That would let any team put a human or model review between generation and readers without a second database. Related earlier reports on generated-output markers: #5211, #5212.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Setup. An organisation brain for a small team: one Postgres, a shared company source plus one source per member. Production runs 0.60.466.0; the code paths below were read on current
main(0.60.565.0).The problem. Our rule is that nothing generated reaches readers until a second model has checked it against its origin and screened it for things that must never sit in a shared brain (health, family, pay, contracts, credentials, judgements of named colleagues). Today there is no supported way to hold generated output until such a check passes:
extract_atomsandsynthesize_conceptspublish what they write straight away. Atom visibility is inherited from the origin page (effectiveVisibilityinsrc/core/cycle/extract-atoms.ts), so atoms from a shared page are readable by every remote caller at once.What we run instead. Each night we restore the daily dump into a local copy, generate there, check every item on the copy, and write only the checked final state back to production. It works, but it costs a full restore per night and rebuilds a publish path outside gbrain.
The idea: a review mode for generation.
dream.review: required(per source or per phase). Generated atoms, concept pages and facts are created held: not returned to remote callers, not in search orrecall, each with a stable id and its origin pin.publishManagedAtomGeneration,heldForInput) may be the natural seam.last_runand brain health, so an operator sees a queue that is not moving.That would let any team put a human or model review between generation and readers without a second database. Related earlier reports on generated-output markers: #5211, #5212.
All reactions