Add opt-in in-memory message boards for Guardian v3 (#62373)

## What changed

Set `features.guardianv3.message_board_in_memory = true` to give each
new or cleared root thread an in-memory SQLite board. The housekeeper
and reviewer share the board until the last handle closes. The reviewer
can read evidence and update its own subscriptions. On-disk storage
remains the default.

With in-memory storage enabled, the attached reviewer is unavailable
on resumed roots because evidence intake starts at the end of history
and a fresh board has no earlier evidence.

## Testing

Exercise evidence catch-up and later post delivery with both storage
modes. Check that only the on-disk mode creates a database file, the
reviewer cannot update channels, and a cold resume skips evidence intake
in memory mode.

GitOrigin-RevId: 338f44720fca510b2baf40fd4b3a4b30245d4fc2
This commit is contained in:
felixxia-oai
2026-11-18 21:57:35 +00:00
committed by copyberry
parent 8bbe7c7d66
commit d7c289ec25
8 changed files with 208 additions and 49 deletions
+3
View File
@@ -315,6 +315,9 @@ where
#[derive(Serialize, Deserialize, Debug, Clone, Default, PartialEq, Eq, JsonSchema)]
#[serde(deny_unknown_fields)]
pub struct GuardianV3ConfigToml {
/// Keep each fresh root's Guardian board in memory until the runtime closes. Defaults to false.
#[serde(skip_serializing_if = "Option::is_none")]
pub message_board_in_memory: Option<bool>,
#[serde(skip_serializing_if = "Option::is_none")]
pub enabled: Option<bool>,
#[serde(skip_serializing_if = "Option::is_none")]
+3
View File
@@ -255,6 +255,8 @@ fn guardian_v3_feature_config_resolves_base_and_profile_toggles() {
fn guardian_v3_prompt_settings_do_not_implicitly_enable_the_feature() {
let features: FeaturesToml = toml::from_str(
r#"
[guardianv3]
message_board_in_memory = true
[guardianv3.housekeeper]
routing_instructions = "Group related deployment evidence."
batch_timeout_ms = 15000
@@ -269,6 +271,7 @@ retrieval_instructions = "Search before assessing deployments."
features.guardianv3,
Some(FeatureToml::Config(crate::GuardianV3ConfigToml {
enabled: None,
message_board_in_memory: Some(true),
housekeeper: Some(crate::GuardianV3HousekeeperConfigToml {
routing_instructions: Some("Group related deployment evidence.".to_owned()),
batch_timeout_ms: std::num::NonZeroU32::new(15_000),