probe_id stringlengths 9 9 | cluster_id stringclasses 54
values | archetype stringclasses 4
values | archetype_instance stringclasses 24
values | kind stringclasses 4
values | principal stringclasses 15
values | inject_after_event stringclasses 82
values | context_frame dict | task stringlengths 158 351 | modality stringclasses 6
values | targets listlengths 1 3 | must_not_use listlengths 0 2 | assertions listlengths 1 4 | counterfactual_probe dict | judge_rubric null | metrics listlengths 1 1 | latency_series dict |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
P-0001-01 | P-0001 | A1 | A1-001 | application | persona:lena | E-0082 | {
"kind": "team_internal",
"ref": "team:platform"
} | Write a short note for the platform team handbook section on endpoint style. Include a rule statement plus three sample path snippets for new resources so engineers can copy the format into upcoming APIs. | document | [
"F-0001"
] | [] | [
{
"id": "asrt-1",
"kind": "fact_applied",
"fact_id": "F-0001",
"checker": "semantic",
"criterion": "The rule statement and sample path snippets name resources using kebab-case (hyphenated, lowercase) segments.",
"weight": 1
},
{
"id": "asrt-cs",
"kind": "fact_absent",
"checke... | {
"ledger_deltas": [
"F-0001"
],
"assertions": [
{
"id": "casrt-1",
"kind": "fact_applied",
"fact_id": "F-0001",
"checker": "semantic",
"criterion": "The rule statement and sample path snippets name resources using camelCase segments.",
"weight": 1
},
{
"i... | null | [
"propagation_latency"
] | {
"offsets_events": [
5,
20,
60
],
"metric": "propagation_latency"
} |
P-0001-02 | P-0001 | A1 | A1-001 | application | persona:lena | E-0097 | {
"kind": "team_internal",
"ref": "team:platform"
} | Write a short note for the platform team handbook section on endpoint style. Include a rule statement plus three sample path snippets for new resources so engineers can copy the format into upcoming APIs. | document | [
"F-0001"
] | [] | [
{
"id": "asrt-1",
"kind": "fact_applied",
"fact_id": "F-0001",
"checker": "semantic",
"criterion": "The rule statement and sample path snippets name resources using kebab-case (hyphenated, lowercase) segments.",
"weight": 1
},
{
"id": "asrt-cs",
"kind": "fact_absent",
"checke... | {
"ledger_deltas": [
"F-0001"
],
"assertions": [
{
"id": "casrt-1",
"kind": "fact_applied",
"fact_id": "F-0001",
"checker": "semantic",
"criterion": "The rule statement and sample path snippets name resources using camelCase segments.",
"weight": 1
},
{
"i... | null | [
"propagation_latency"
] | {
"offsets_events": [
5,
20,
60
],
"metric": "propagation_latency"
} |
P-0001-03 | P-0001 | A1 | A1-001 | application | persona:lena | E-0137 | {
"kind": "team_internal",
"ref": "team:platform"
} | Write a short note for the platform team handbook section on endpoint style. Include a rule statement plus three sample path snippets for new resources so engineers can copy the format into upcoming APIs. | document | [
"F-0001"
] | [] | [
{
"id": "asrt-1",
"kind": "fact_applied",
"fact_id": "F-0001",
"checker": "semantic",
"criterion": "The rule statement and sample path snippets name resources using kebab-case (hyphenated, lowercase) segments.",
"weight": 1
},
{
"id": "asrt-cs",
"kind": "fact_absent",
"checke... | {
"ledger_deltas": [
"F-0001"
],
"assertions": [
{
"id": "casrt-1",
"kind": "fact_applied",
"fact_id": "F-0001",
"checker": "semantic",
"criterion": "The rule statement and sample path snippets name resources using camelCase segments.",
"weight": 1
},
{
"i... | null | [
"propagation_latency"
] | {
"offsets_events": [
5,
20,
60
],
"metric": "propagation_latency"
} |
P-0002-01 | P-0002 | A2 | A2-001 | application | persona:yuki | E-0118 | {
"kind": "team_internal",
"ref": "team:platform"
} | Prepare the platform team's event-page copy for the next growth demo session. Include the speaking-time rule each presenter must follow and keep the wording ready to paste without edits. | document | [
"F-0005"
] | [] | [
{
"id": "asrt-1",
"kind": "fact_applied",
"fact_id": "F-0005",
"checker": "semantic",
"criterion": "The event-page copy states each presenter gets five minutes to speak.",
"weight": 1
}
] | {
"ledger_deltas": [
"F-0005"
],
"assertions": [
{
"id": "casrt-1",
"kind": "fact_applied",
"fact_id": "F-0005",
"checker": "semantic",
"criterion": "The event-page copy states each presenter gets fifteen minutes to speak.",
"weight": 1
}
]
} | null | [
"proactive_application"
] | {
"offsets_events": [
4,
30,
80
],
"metric": "proactive_application"
} |
P-0002-02 | P-0002 | A2 | A2-001 | application | persona:yuki | E-0168 | {
"kind": "team_internal",
"ref": "team:platform"
} | Prepare the platform team's event-page copy for the next growth demo session. Include the speaking-time rule each presenter must follow and keep the wording ready to paste without edits. | document | [
"F-0005"
] | [] | [
{
"id": "asrt-1",
"kind": "fact_applied",
"fact_id": "F-0005",
"checker": "semantic",
"criterion": "The event-page copy states each presenter gets five minutes to speak.",
"weight": 1
}
] | {
"ledger_deltas": [
"F-0005"
],
"assertions": [
{
"id": "casrt-1",
"kind": "fact_applied",
"fact_id": "F-0005",
"checker": "semantic",
"criterion": "The event-page copy states each presenter gets fifteen minutes to speak.",
"weight": 1
}
]
} | null | [
"proactive_application"
] | {
"offsets_events": [
4,
30,
80
],
"metric": "proactive_application"
} |
P-0002-03 | P-0002 | A2 | A2-001 | application | persona:yuki | E-0092 | {
"kind": "team_internal",
"ref": "team:platform"
} | Prepare the platform team's event-page copy for the next growth demo session. Include the speaking-time rule each presenter must follow and keep the wording ready to paste without edits. | document | [
"F-0005"
] | [] | [
{
"id": "asrt-1",
"kind": "fact_applied",
"fact_id": "F-0005",
"checker": "semantic",
"criterion": "The event-page copy states each presenter gets five minutes to speak.",
"weight": 1
}
] | {
"ledger_deltas": [
"F-0005"
],
"assertions": [
{
"id": "casrt-1",
"kind": "fact_applied",
"fact_id": "F-0005",
"checker": "semantic",
"criterion": "The event-page copy states each presenter gets fifteen minutes to speak.",
"weight": 1
}
]
} | null | [
"proactive_application"
] | {
"offsets_events": [
4,
30,
80
],
"metric": "proactive_application"
} |
P-0003-01 | P-0003 | A4 | A4-001 | scope_resolution | persona:mei | E-0091 | {
"kind": "org_facing",
"ref": null
} | Draft an all-hands note that explains how strategic priorities are surfaced to leadership across the business. Keep it short and directive, with a clear section on timing, who joins, and what teams should bring so the note can be reused in future announcements. | document | [
"F-0009",
"F-0010",
"F-0011"
] | [] | [
{
"id": "asrt-1",
"kind": "scope_correct",
"fact_id": "F-0009",
"checker": "semantic",
"criterion": "The note presents this as a recurring leadership forum on a weekly rhythm for the whole business, not as a team-level or personal practice.",
"weight": 1
},
{
"id": "asrt-2",
"kin... | {
"ledger_deltas": [
"F-0009",
"F-0010",
"F-0011"
],
"assertions": [
{
"id": "casrt-1",
"kind": "scope_correct",
"fact_id": "F-0009",
"checker": "semantic",
"criterion": "The note says these reviews are paused until the next quarterly planning cycle rather than schedu... | null | [
"scope_resolution_accuracy"
] | null |
P-0003-02 | P-0003 | A4 | A4-001 | scope_resolution | persona:yuki | E-0091 | {
"kind": "org_facing",
"ref": null
} | Draft an all-hands note that explains how strategic priorities are surfaced to leadership across the business. Keep it short and directive, with a clear section on timing, who joins, and what teams should bring so the note can be reused in future announcements. | document | [
"F-0009",
"F-0010",
"F-0011"
] | [] | [
{
"id": "asrt-1",
"kind": "scope_correct",
"fact_id": "F-0009",
"checker": "semantic",
"criterion": "The note presents this as a recurring leadership forum on a weekly rhythm for the whole business, not as a team-level or personal practice.",
"weight": 1
},
{
"id": "asrt-2",
"kin... | {
"ledger_deltas": [
"F-0009",
"F-0010",
"F-0011"
],
"assertions": [
{
"id": "casrt-1",
"kind": "scope_correct",
"fact_id": "F-0009",
"checker": "semantic",
"criterion": "The note says these reviews are paused until the next quarterly planning cycle rather than schedu... | null | [
"scope_resolution_accuracy"
] | null |
P-0003-03 | P-0003 | A4 | A4-001 | scope_resolution | persona:mei | E-0085 | {
"kind": "org_facing",
"ref": null
} | Draft an all-hands note that explains how strategic priorities are surfaced to leadership across the business. Keep it short and directive, with a clear section on timing, who joins, and what teams should bring so the note can be reused in future announcements. | document | [
"F-0009",
"F-0010",
"F-0011"
] | [] | [
{
"id": "asrt-1",
"kind": "scope_correct",
"fact_id": "F-0009",
"checker": "semantic",
"criterion": "The note presents this as a recurring leadership forum on a weekly rhythm for the whole business, not as a team-level or personal practice.",
"weight": 1
},
{
"id": "asrt-2",
"kin... | {
"ledger_deltas": [
"F-0009",
"F-0010",
"F-0011"
],
"assertions": [
{
"id": "casrt-1",
"kind": "scope_correct",
"fact_id": "F-0009",
"checker": "semantic",
"criterion": "The note says these reviews are paused until the next quarterly planning cycle rather than schedu... | null | [
"scope_resolution_accuracy"
] | null |
P-0004-01 | P-0004 | A4 | A4-001 | scope_resolution | persona:mei | E-0091 | {
"kind": "team_internal",
"ref": "team:platform"
} | Write a short operating note for the platform group that sets the recurring forum for discussing shifts in upcoming work. Make it something the team can paste into its channel, and include timing, where it sits in the team routine, and what each pass is meant to cover. | message | [
"F-0009",
"F-0010",
"F-0011"
] | [] | [
{
"id": "asrt-1",
"kind": "scope_correct",
"fact_id": "F-0010",
"checker": "semantic",
"criterion": "The note sets this forum on a biweekly (every-two-weeks) rhythm as part of team planning.",
"weight": 1
},
{
"id": "asrt-3",
"kind": "fact_absent",
"fact_id": "F-0011",
"c... | {
"ledger_deltas": [
"F-0009",
"F-0010",
"F-0011"
],
"assertions": [
{
"id": "casrt-1",
"kind": "scope_correct",
"fact_id": "F-0010",
"checker": "semantic",
"criterion": "The note sets this forum on a monthly rhythm as part of team planning.",
"weight": 1
},... | null | [
"scope_resolution_accuracy"
] | null |
P-0004-02 | P-0004 | A4 | A4-001 | scope_resolution | persona:yuki | E-0091 | {
"kind": "team_internal",
"ref": "team:platform"
} | Write a short operating note for the platform group that sets the recurring forum for discussing shifts in upcoming work. Make it something the team can paste into its channel, and include timing, where it sits in the team routine, and what each pass is meant to cover. | message | [
"F-0009",
"F-0010",
"F-0011"
] | [] | [
{
"id": "asrt-1",
"kind": "scope_correct",
"fact_id": "F-0010",
"checker": "semantic",
"criterion": "The note sets this forum on a biweekly (every-two-weeks) rhythm as part of team planning.",
"weight": 1
},
{
"id": "asrt-3",
"kind": "fact_absent",
"fact_id": "F-0011",
"c... | {
"ledger_deltas": [
"F-0009",
"F-0010",
"F-0011"
],
"assertions": [
{
"id": "casrt-1",
"kind": "scope_correct",
"fact_id": "F-0010",
"checker": "semantic",
"criterion": "The note sets this forum on a monthly rhythm as part of team planning.",
"weight": 1
},... | null | [
"scope_resolution_accuracy"
] | null |
P-0004-03 | P-0004 | A4 | A4-001 | scope_resolution | persona:mei | E-0085 | {
"kind": "team_internal",
"ref": "team:platform"
} | Write a short operating note for the platform group that sets the recurring forum for discussing shifts in upcoming work. Make it something the team can paste into its channel, and include timing, where it sits in the team routine, and what each pass is meant to cover. | message | [
"F-0009",
"F-0010",
"F-0011"
] | [] | [
{
"id": "asrt-1",
"kind": "scope_correct",
"fact_id": "F-0010",
"checker": "semantic",
"criterion": "The note sets this forum on a biweekly (every-two-weeks) rhythm as part of team planning.",
"weight": 1
},
{
"id": "asrt-3",
"kind": "fact_absent",
"fact_id": "F-0011",
"c... | {
"ledger_deltas": [
"F-0009",
"F-0010",
"F-0011"
],
"assertions": [
{
"id": "casrt-1",
"kind": "scope_correct",
"fact_id": "F-0010",
"checker": "semantic",
"criterion": "The note sets this forum on a monthly rhythm as part of team planning.",
"weight": 1
},... | null | [
"scope_resolution_accuracy"
] | null |
P-0005-01 | P-0005 | A4 | A4-001 | scope_resolution | persona:mei | E-0091 | {
"kind": "personal",
"ref": "persona:mei"
} | Make yourself a private routine note for checking changes to upcoming work. Keep it lightweight and reusable, and spell out both how often you want to do it and the format you want to use, so you can follow the same practice even during crowded stretches. | plan | [
"F-0009",
"F-0010",
"F-0011"
] | [] | [
{
"id": "asrt-1",
"kind": "scope_correct",
"fact_id": "F-0011",
"checker": "semantic",
"criterion": "The note describes Mei's own recurring practice as a monthly written check-in, not a team or company forum.",
"weight": 1
}
] | {
"ledger_deltas": [
"F-0009",
"F-0010",
"F-0011"
],
"assertions": [
{
"id": "casrt-1",
"kind": "scope_correct",
"fact_id": "F-0011",
"checker": "semantic",
"criterion": "The note describes Mei's own recurring practice as a live meeting every week rather than a monthl... | null | [
"scope_resolution_accuracy"
] | null |
P-0005-02 | P-0005 | A4 | A4-001 | scope_resolution | persona:yuki | E-0091 | {
"kind": "personal",
"ref": "persona:mei"
} | Make yourself a private routine note for checking changes to upcoming work. Keep it lightweight and reusable, and spell out both how often you want to do it and the format you want to use, so you can follow the same practice even during crowded stretches. | plan | [
"F-0009",
"F-0010",
"F-0011"
] | [] | [
{
"id": "asrt-1",
"kind": "scope_correct",
"fact_id": "F-0011",
"checker": "semantic",
"criterion": "The note describes Mei's own recurring practice as a monthly written check-in, not a team or company forum.",
"weight": 1
}
] | {
"ledger_deltas": [
"F-0009",
"F-0010",
"F-0011"
],
"assertions": [
{
"id": "casrt-1",
"kind": "scope_correct",
"fact_id": "F-0011",
"checker": "semantic",
"criterion": "The note describes Mei's own recurring practice as a live meeting every week rather than a monthl... | null | [
"scope_resolution_accuracy"
] | null |
P-0005-03 | P-0005 | A4 | A4-001 | scope_resolution | persona:mei | E-0085 | {
"kind": "personal",
"ref": "persona:mei"
} | Make yourself a private routine note for checking changes to upcoming work. Keep it lightweight and reusable, and spell out both how often you want to do it and the format you want to use, so you can follow the same practice even during crowded stretches. | plan | [
"F-0009",
"F-0010",
"F-0011"
] | [] | [
{
"id": "asrt-1",
"kind": "scope_correct",
"fact_id": "F-0011",
"checker": "semantic",
"criterion": "The note describes Mei's own recurring practice as a monthly written check-in, not a team or company forum.",
"weight": 1
}
] | {
"ledger_deltas": [
"F-0009",
"F-0010",
"F-0011"
],
"assertions": [
{
"id": "casrt-1",
"kind": "scope_correct",
"fact_id": "F-0011",
"checker": "semantic",
"criterion": "The note describes Mei's own recurring practice as a live meeting every week rather than a monthl... | null | [
"scope_resolution_accuracy"
] | null |
P-0006-01 | P-0006 | A7 | A7-001 | staleness | persona:lena | E-0014 | {
"kind": "org_facing",
"ref": null
} | Write a short engineering-wide policy note explaining when a design doc becomes mandatory for a change that touches several services. Include the numeric cutoff in plain language and one quick example. | document | [
"F-0015"
] | [] | [
{
"id": "asrt-1",
"kind": "fact_applied",
"fact_id": "F-0015",
"checker": "semantic",
"criterion": "The policy note states a design doc becomes mandatory once a change touches three or more services.",
"weight": 1
}
] | {
"ledger_deltas": [
"F-0015"
],
"assertions": [
{
"id": "casrt-1",
"kind": "fact_applied",
"fact_id": "F-0015",
"checker": "semantic",
"criterion": "The policy note states a design doc becomes mandatory once a change touches two or more services.",
"weight": 1
}
... | null | [
"staleness_rate"
] | null |
P-0006-02 | P-0006 | A7 | A7-001 | staleness | persona:lena | E-0013 | {
"kind": "org_facing",
"ref": null
} | Write a short engineering-wide policy note explaining when a design doc becomes mandatory for a change that touches several services. Include the numeric cutoff in plain language and one quick example. | document | [
"F-0015"
] | [] | [
{
"id": "asrt-1",
"kind": "fact_applied",
"fact_id": "F-0015",
"checker": "semantic",
"criterion": "The policy note states a design doc becomes mandatory once a change touches three or more services.",
"weight": 1
}
] | {
"ledger_deltas": [
"F-0015"
],
"assertions": [
{
"id": "casrt-1",
"kind": "fact_applied",
"fact_id": "F-0015",
"checker": "semantic",
"criterion": "The policy note states a design doc becomes mandatory once a change touches two or more services.",
"weight": 1
}
... | null | [
"staleness_rate"
] | null |
P-0006-03 | P-0006 | A7 | A7-001 | staleness | persona:lena | E-0018 | {
"kind": "org_facing",
"ref": null
} | Write a short engineering-wide policy note explaining when a design doc becomes mandatory for a change that touches several services. Include the numeric cutoff in plain language and one quick example. | document | [
"F-0015"
] | [] | [
{
"id": "asrt-1",
"kind": "fact_applied",
"fact_id": "F-0015",
"checker": "semantic",
"criterion": "The policy note states a design doc becomes mandatory once a change touches three or more services.",
"weight": 1
}
] | {
"ledger_deltas": [
"F-0015"
],
"assertions": [
{
"id": "casrt-1",
"kind": "fact_applied",
"fact_id": "F-0015",
"checker": "semantic",
"criterion": "The policy note states a design doc becomes mandatory once a change touches two or more services.",
"weight": 1
}
... | null | [
"staleness_rate"
] | null |
P-0007-01 | P-0007 | A7 | A7-001 | staleness | persona:lena | E-0116 | {
"kind": "org_facing",
"ref": null
} | Draft the updated org policy snippet for when a design doc is mandatory as changes spread across services. Include the current cutoff and a borderline example so teams can classify work correctly. | document | [
"F-0016"
] | [
"F-0015"
] | [
{
"id": "asrt-1",
"kind": "fact_applied",
"fact_id": "F-0016",
"checker": "semantic",
"criterion": "The updated policy snippet states the design-doc threshold is five or more services.",
"weight": 1
},
{
"id": "asrt-2",
"kind": "fact_absent",
"fact_id": "F-0015",
"checker... | {
"ledger_deltas": [
"F-0016"
],
"assertions": [
{
"id": "casrt-1",
"kind": "fact_applied",
"fact_id": "F-0016",
"checker": "semantic",
"criterion": "The updated policy snippet states the design-doc threshold is seven or more services.",
"weight": 1
},
{
"... | null | [
"staleness_rate"
] | null |
P-0007-02 | P-0007 | A7 | A7-001 | staleness | persona:lena | E-0115 | {
"kind": "org_facing",
"ref": null
} | Draft the updated org policy snippet for when a design doc is mandatory as changes spread across services. Include the current cutoff and a borderline example so teams can classify work correctly. | document | [
"F-0016"
] | [
"F-0015"
] | [
{
"id": "asrt-1",
"kind": "fact_applied",
"fact_id": "F-0016",
"checker": "semantic",
"criterion": "The updated policy snippet states the design-doc threshold is five or more services.",
"weight": 1
},
{
"id": "asrt-2",
"kind": "fact_absent",
"fact_id": "F-0015",
"checker... | {
"ledger_deltas": [
"F-0016"
],
"assertions": [
{
"id": "casrt-1",
"kind": "fact_applied",
"fact_id": "F-0016",
"checker": "semantic",
"criterion": "The updated policy snippet states the design-doc threshold is seven or more services.",
"weight": 1
},
{
"... | null | [
"staleness_rate"
] | null |
P-0007-03 | P-0007 | A7 | A7-001 | staleness | persona:lena | E-0120 | {
"kind": "org_facing",
"ref": null
} | Draft the updated org policy snippet for when a design doc is mandatory as changes spread across services. Include the current cutoff and a borderline example so teams can classify work correctly. | document | [
"F-0016"
] | [
"F-0015"
] | [
{
"id": "asrt-1",
"kind": "fact_applied",
"fact_id": "F-0016",
"checker": "semantic",
"criterion": "The updated policy snippet states the design-doc threshold is five or more services.",
"weight": 1
},
{
"id": "asrt-2",
"kind": "fact_absent",
"fact_id": "F-0015",
"checker... | {
"ledger_deltas": [
"F-0016"
],
"assertions": [
{
"id": "casrt-1",
"kind": "fact_applied",
"fact_id": "F-0016",
"checker": "semantic",
"criterion": "The updated policy snippet states the design-doc threshold is seven or more services.",
"weight": 1
},
{
"... | null | [
"staleness_rate"
] | null |
P-0008-01 | P-0008 | A7 | A7-001 | staleness | persona:lena | E-0167 | {
"kind": "org_facing",
"ref": null
} | Write a company-wide engineering note that clears up the current architecture writeup gate after recent confusion. Base it on a rollout example that updates a product repo plus a platform-owned dependency. State the present trigger plainly and add a brief reviewer checklist so teams stop relying on the old counting heu... | document | [
"F-0017"
] | [
"F-0015",
"F-0016"
] | [
{
"id": "asrt-1",
"kind": "fact_applied",
"fact_id": "F-0017",
"checker": "semantic",
"criterion": "The note makes the trigger depend on whether work touches a shared library, not on counting services.",
"weight": 1
},
{
"id": "asrt-2",
"kind": "fact_absent",
"fact_id": "F-00... | {
"ledger_deltas": [
"F-0017"
],
"assertions": [
{
"id": "casrt-1",
"kind": "fact_applied",
"fact_id": "F-0017",
"checker": "semantic",
"criterion": "The note treats a design doc as optional unless the change spans ten or more services.",
"weight": 1
},
{
... | null | [
"staleness_rate"
] | null |
P-0008-02 | P-0008 | A7 | A7-001 | staleness | persona:lena | E-0166 | {
"kind": "org_facing",
"ref": null
} | Write a company-wide engineering note that clears up the current architecture writeup gate after recent confusion. Base it on a rollout example that updates a product repo plus a platform-owned dependency. State the present trigger plainly and add a brief reviewer checklist so teams stop relying on the old counting heu... | document | [
"F-0017"
] | [
"F-0015",
"F-0016"
] | [
{
"id": "asrt-1",
"kind": "fact_applied",
"fact_id": "F-0017",
"checker": "semantic",
"criterion": "The note makes the trigger depend on whether work touches a shared library, not on counting services.",
"weight": 1
},
{
"id": "asrt-2",
"kind": "fact_absent",
"fact_id": "F-00... | {
"ledger_deltas": [
"F-0017"
],
"assertions": [
{
"id": "casrt-1",
"kind": "fact_applied",
"fact_id": "F-0017",
"checker": "semantic",
"criterion": "The note treats a design doc as optional unless the change spans ten or more services.",
"weight": 1
},
{
... | null | [
"staleness_rate"
] | null |
P-0008-03 | P-0008 | A7 | A7-001 | staleness | persona:lena | E-0171 | {
"kind": "org_facing",
"ref": null
} | Write a company-wide engineering note that clears up the current architecture writeup gate after recent confusion. Base it on a rollout example that updates a product repo plus a platform-owned dependency. State the present trigger plainly and add a brief reviewer checklist so teams stop relying on the old counting heu... | document | [
"F-0017"
] | [
"F-0015",
"F-0016"
] | [
{
"id": "asrt-1",
"kind": "fact_applied",
"fact_id": "F-0017",
"checker": "semantic",
"criterion": "The note makes the trigger depend on whether work touches a shared library, not on counting services.",
"weight": 1
},
{
"id": "asrt-2",
"kind": "fact_absent",
"fact_id": "F-00... | {
"ledger_deltas": [
"F-0017"
],
"assertions": [
{
"id": "casrt-1",
"kind": "fact_applied",
"fact_id": "F-0017",
"checker": "semantic",
"criterion": "The note treats a design doc as optional unless the change spans ten or more services.",
"weight": 1
},
{
... | null | [
"staleness_rate"
] | null |
P-0009-01 | P-0009 | A7 | A7-001 | historical | persona:lena | E-0170 | {
"kind": "org_facing",
"ref": null
} | Prepare a short company retrospective entry for an all-hands timeline of process shifts around architecture writeups. Include the earlier threshold teams used when one initiative reached multiple product systems, and phrase it as a past-state milestone rather than current guidance. | document | [
"F-0015"
] | [] | [
{
"id": "asrt-1",
"kind": "fact_applied",
"fact_id": "F-0015",
"checker": "semantic",
"criterion": "The retrospective entry recounts the earlier threshold as three or more services.",
"weight": 1
}
] | {
"ledger_deltas": [
"F-0015"
],
"assertions": [
{
"id": "casrt-1",
"kind": "fact_applied",
"fact_id": "F-0015",
"checker": "semantic",
"criterion": "The retrospective entry recounts the earlier threshold as two or more services.",
"weight": 1
}
]
} | null | [
"history_retention"
] | null |
P-0009-02 | P-0009 | A7 | A7-001 | historical | persona:lena | E-0166 | {
"kind": "org_facing",
"ref": null
} | Prepare a short company retrospective entry for an all-hands timeline of process shifts around architecture writeups. Include the earlier threshold teams used when one initiative reached multiple product systems, and phrase it as a past-state milestone rather than current guidance. | document | [
"F-0015"
] | [] | [
{
"id": "asrt-1",
"kind": "fact_applied",
"fact_id": "F-0015",
"checker": "semantic",
"criterion": "The retrospective entry recounts the earlier threshold as three or more services.",
"weight": 1
}
] | {
"ledger_deltas": [
"F-0015"
],
"assertions": [
{
"id": "casrt-1",
"kind": "fact_applied",
"fact_id": "F-0015",
"checker": "semantic",
"criterion": "The retrospective entry recounts the earlier threshold as two or more services.",
"weight": 1
}
]
} | null | [
"history_retention"
] | null |
P-0009-03 | P-0009 | A7 | A7-001 | historical | persona:lena | E-0171 | {
"kind": "org_facing",
"ref": null
} | Prepare a short company retrospective entry for an all-hands timeline of process shifts around architecture writeups. Include the earlier threshold teams used when one initiative reached multiple product systems, and phrase it as a past-state milestone rather than current guidance. | document | [
"F-0015"
] | [] | [
{
"id": "asrt-1",
"kind": "fact_applied",
"fact_id": "F-0015",
"checker": "semantic",
"criterion": "The retrospective entry recounts the earlier threshold as three or more services.",
"weight": 1
}
] | {
"ledger_deltas": [
"F-0015"
],
"assertions": [
{
"id": "casrt-1",
"kind": "fact_applied",
"fact_id": "F-0015",
"checker": "semantic",
"criterion": "The retrospective entry recounts the earlier threshold as two or more services.",
"weight": 1
}
]
} | null | [
"history_retention"
] | null |
P-0010-01 | P-0010 | A1 | A1-002 | application | persona:otto | E-0078 | {
"kind": "team_internal",
"ref": "team:growth"
} | Write a short handbook update for the growth team covering how on-call rotations are recognized. Include a payroll-ready example for one full rotation and note what a manager needs to submit after the coverage window ends. | document | [
"F-0021"
] | [] | [
{
"id": "asrt-1",
"kind": "fact_applied",
"fact_id": "F-0021",
"checker": "semantic",
"criterion": "The handbook update states on-call coverage earns a $250 per-week stipend.",
"weight": 1
}
] | {
"ledger_deltas": [
"F-0021"
],
"assertions": [
{
"id": "casrt-1",
"kind": "fact_applied",
"fact_id": "F-0021",
"checker": "semantic",
"criterion": "The handbook update says on-call coverage is recognized with time off rather than a cash payment.",
"weight": 1
}
... | null | [
"propagation_latency"
] | {
"offsets_events": [
5,
20,
60
],
"metric": "propagation_latency"
} |
P-0010-02 | P-0010 | A1 | A1-002 | application | persona:otto | E-0093 | {
"kind": "team_internal",
"ref": "team:growth"
} | Write a short handbook update for the growth team covering how on-call rotations are recognized. Include a payroll-ready example for one full rotation and note what a manager needs to submit after the coverage window ends. | document | [
"F-0021"
] | [] | [
{
"id": "asrt-1",
"kind": "fact_applied",
"fact_id": "F-0021",
"checker": "semantic",
"criterion": "The handbook update states on-call coverage earns a $250 per-week stipend.",
"weight": 1
}
] | {
"ledger_deltas": [
"F-0021"
],
"assertions": [
{
"id": "casrt-1",
"kind": "fact_applied",
"fact_id": "F-0021",
"checker": "semantic",
"criterion": "The handbook update says on-call coverage is recognized with time off rather than a cash payment.",
"weight": 1
}
... | null | [
"propagation_latency"
] | {
"offsets_events": [
5,
20,
60
],
"metric": "propagation_latency"
} |
P-0010-03 | P-0010 | A1 | A1-002 | application | persona:otto | E-0133 | {
"kind": "team_internal",
"ref": "team:growth"
} | Write a short handbook update for the growth team covering how on-call rotations are recognized. Include a payroll-ready example for one full rotation and note what a manager needs to submit after the coverage window ends. | document | [
"F-0021"
] | [] | [
{
"id": "asrt-1",
"kind": "fact_applied",
"fact_id": "F-0021",
"checker": "semantic",
"criterion": "The handbook update states on-call coverage earns a $250 per-week stipend.",
"weight": 1
}
] | {
"ledger_deltas": [
"F-0021"
],
"assertions": [
{
"id": "casrt-1",
"kind": "fact_applied",
"fact_id": "F-0021",
"checker": "semantic",
"criterion": "The handbook update says on-call coverage is recognized with time off rather than a cash payment.",
"weight": 1
}
... | null | [
"propagation_latency"
] | {
"offsets_events": [
5,
20,
60
],
"metric": "propagation_latency"
} |
P-0011-01 | P-0011 | A2 | A2-002 | application | persona:celine | E-0043 | {
"kind": "team_internal",
"ref": "team:growth"
} | Draft the growth team’s partner incident checklist. Include the deadline for the very first outbound note to the affected partner, and make the instruction explicit enough that whoever is covering comms can send it right away without extra approval. | checklist | [
"F-0026"
] | [] | [
{
"id": "asrt-1",
"kind": "fact_applied",
"fact_id": "F-0026",
"checker": "semantic",
"criterion": "The checklist requires the first outbound partner note within thirty minutes.",
"weight": 1
}
] | {
"ledger_deltas": [
"F-0026"
],
"assertions": [
{
"id": "casrt-1",
"kind": "fact_applied",
"fact_id": "F-0026",
"checker": "semantic",
"criterion": "The checklist allows the first outbound partner note to wait until the next business day.",
"weight": 1
}
]
} | null | [
"proactive_application"
] | {
"offsets_events": [
4,
30,
80
],
"metric": "proactive_application"
} |
P-0011-02 | P-0011 | A2 | A2-002 | application | persona:celine | E-0093 | {
"kind": "team_internal",
"ref": "team:growth"
} | Draft the growth team’s partner incident checklist. Include the deadline for the very first outbound note to the affected partner, and make the instruction explicit enough that whoever is covering comms can send it right away without extra approval. | checklist | [
"F-0026"
] | [] | [
{
"id": "asrt-1",
"kind": "fact_applied",
"fact_id": "F-0026",
"checker": "semantic",
"criterion": "The checklist requires the first outbound partner note within thirty minutes.",
"weight": 1
}
] | {
"ledger_deltas": [
"F-0026"
],
"assertions": [
{
"id": "casrt-1",
"kind": "fact_applied",
"fact_id": "F-0026",
"checker": "semantic",
"criterion": "The checklist allows the first outbound partner note to wait until the next business day.",
"weight": 1
}
]
} | null | [
"proactive_application"
] | {
"offsets_events": [
4,
30,
80
],
"metric": "proactive_application"
} |
P-0011-03 | P-0011 | A2 | A2-002 | application | persona:celine | E-0017 | {
"kind": "team_internal",
"ref": "team:growth"
} | Draft the growth team’s partner incident checklist. Include the deadline for the very first outbound note to the affected partner, and make the instruction explicit enough that whoever is covering comms can send it right away without extra approval. | checklist | [
"F-0026"
] | [] | [
{
"id": "asrt-1",
"kind": "fact_applied",
"fact_id": "F-0026",
"checker": "semantic",
"criterion": "The checklist requires the first outbound partner note within thirty minutes.",
"weight": 1
}
] | {
"ledger_deltas": [
"F-0026"
],
"assertions": [
{
"id": "casrt-1",
"kind": "fact_applied",
"fact_id": "F-0026",
"checker": "semantic",
"criterion": "The checklist allows the first outbound partner note to wait until the next business day.",
"weight": 1
}
]
} | null | [
"proactive_application"
] | {
"offsets_events": [
4,
30,
80
],
"metric": "proactive_application"
} |
P-0012-01 | P-0012 | A4 | A4-002 | scope_resolution | persona:celine | E-0082 | {
"kind": "org_facing",
"ref": null
} | Write a company-wide Slack etiquette post for the workspace’s default discussion channel during a standard operating window. State the turnaround standard for follow-ups there, and keep the guidance framed for the whole org rather than a squad’s urgent lane or any individual habit. | message | [
"F-0030",
"F-0031",
"F-0032"
] | [] | [
{
"id": "asrt-1",
"kind": "scope_correct",
"fact_id": "F-0030",
"checker": "semantic",
"criterion": "The post sets a four-business-hour reply expectation for the default discussion channel.",
"weight": 1
},
{
"id": "asrt-2",
"kind": "fact_absent",
"fact_id": "F-0031",
"ch... | {
"ledger_deltas": [
"F-0030",
"F-0031",
"F-0032"
],
"assertions": [
{
"id": "casrt-1",
"kind": "scope_correct",
"fact_id": "F-0030",
"checker": "semantic",
"criterion": "The post says the default discussion channel has no turnaround standard on company holidays.",
... | null | [
"scope_resolution_accuracy"
] | null |
P-0012-02 | P-0012 | A4 | A4-002 | scope_resolution | persona:anouk | E-0082 | {
"kind": "org_facing",
"ref": null
} | Write a company-wide Slack etiquette post for the workspace’s default discussion channel during a standard operating window. State the turnaround standard for follow-ups there, and keep the guidance framed for the whole org rather than a squad’s urgent lane or any individual habit. | message | [
"F-0030",
"F-0031",
"F-0032"
] | [] | [
{
"id": "asrt-1",
"kind": "scope_correct",
"fact_id": "F-0030",
"checker": "semantic",
"criterion": "The post sets a four-business-hour reply expectation for the default discussion channel.",
"weight": 1
},
{
"id": "asrt-2",
"kind": "fact_absent",
"fact_id": "F-0031",
"ch... | {
"ledger_deltas": [
"F-0030",
"F-0031",
"F-0032"
],
"assertions": [
{
"id": "casrt-1",
"kind": "scope_correct",
"fact_id": "F-0030",
"checker": "semantic",
"criterion": "The post says the default discussion channel has no turnaround standard on company holidays.",
... | null | [
"scope_resolution_accuracy"
] | null |
P-0012-03 | P-0012 | A4 | A4-002 | scope_resolution | persona:celine | E-0076 | {
"kind": "org_facing",
"ref": null
} | Write a company-wide Slack etiquette post for the workspace’s default discussion channel during a standard operating window. State the turnaround standard for follow-ups there, and keep the guidance framed for the whole org rather than a squad’s urgent lane or any individual habit. | message | [
"F-0030",
"F-0031",
"F-0032"
] | [] | [
{
"id": "asrt-1",
"kind": "scope_correct",
"fact_id": "F-0030",
"checker": "semantic",
"criterion": "The post sets a four-business-hour reply expectation for the default discussion channel.",
"weight": 1
},
{
"id": "asrt-2",
"kind": "fact_absent",
"fact_id": "F-0031",
"ch... | {
"ledger_deltas": [
"F-0030",
"F-0031",
"F-0032"
],
"assertions": [
{
"id": "casrt-1",
"kind": "scope_correct",
"fact_id": "F-0030",
"checker": "semantic",
"criterion": "The post says the default discussion channel has no turnaround standard on company holidays.",
... | null | [
"scope_resolution_accuracy"
] | null |
P-0013-01 | P-0013 | A4 | A4-002 | scope_resolution | persona:celine | E-0082 | {
"kind": "team_internal",
"ref": "team:growth"
} | Write a short guidance note for the growth team covering how to handle urgent Slack threads routed to platform support. Make the turnaround commitment explicit for that lane, and keep the draft centered on team operations rather than company-wide channels or a coworker’s personal habits. | message | [
"F-0030",
"F-0031",
"F-0032"
] | [] | [
{
"id": "asrt-1",
"kind": "scope_correct",
"fact_id": "F-0031",
"checker": "semantic",
"criterion": "The note sets a one-hour reply expectation for urgent platform-tagged Slack threads.",
"weight": 1
},
{
"id": "asrt-3",
"kind": "fact_absent",
"fact_id": "F-0032",
"checke... | {
"ledger_deltas": [
"F-0030",
"F-0031",
"F-0032"
],
"assertions": [
{
"id": "casrt-1",
"kind": "scope_correct",
"fact_id": "F-0031",
"checker": "semantic",
"criterion": "The note sets a four-hour reply expectation for urgent platform-tagged Slack threads.",
"we... | null | [
"scope_resolution_accuracy"
] | null |
P-0013-02 | P-0013 | A4 | A4-002 | scope_resolution | persona:anouk | E-0082 | {
"kind": "team_internal",
"ref": "team:growth"
} | Write a short guidance note for the growth team covering how to handle urgent Slack threads routed to platform support. Make the turnaround commitment explicit for that lane, and keep the draft centered on team operations rather than company-wide channels or a coworker’s personal habits. | message | [
"F-0030",
"F-0031",
"F-0032"
] | [] | [
{
"id": "asrt-1",
"kind": "scope_correct",
"fact_id": "F-0031",
"checker": "semantic",
"criterion": "The note sets a one-hour reply expectation for urgent platform-tagged Slack threads.",
"weight": 1
},
{
"id": "asrt-3",
"kind": "fact_absent",
"fact_id": "F-0032",
"checke... | {
"ledger_deltas": [
"F-0030",
"F-0031",
"F-0032"
],
"assertions": [
{
"id": "casrt-1",
"kind": "scope_correct",
"fact_id": "F-0031",
"checker": "semantic",
"criterion": "The note sets a four-hour reply expectation for urgent platform-tagged Slack threads.",
"we... | null | [
"scope_resolution_accuracy"
] | null |
P-0013-03 | P-0013 | A4 | A4-002 | scope_resolution | persona:celine | E-0076 | {
"kind": "team_internal",
"ref": "team:growth"
} | Write a short guidance note for the growth team covering how to handle urgent Slack threads routed to platform support. Make the turnaround commitment explicit for that lane, and keep the draft centered on team operations rather than company-wide channels or a coworker’s personal habits. | message | [
"F-0030",
"F-0031",
"F-0032"
] | [] | [
{
"id": "asrt-1",
"kind": "scope_correct",
"fact_id": "F-0031",
"checker": "semantic",
"criterion": "The note sets a one-hour reply expectation for urgent platform-tagged Slack threads.",
"weight": 1
},
{
"id": "asrt-3",
"kind": "fact_absent",
"fact_id": "F-0032",
"checke... | {
"ledger_deltas": [
"F-0030",
"F-0031",
"F-0032"
],
"assertions": [
{
"id": "casrt-1",
"kind": "scope_correct",
"fact_id": "F-0031",
"checker": "semantic",
"criterion": "The note sets a four-hour reply expectation for urgent platform-tagged Slack threads.",
"we... | null | [
"scope_resolution_accuracy"
] | null |
P-0014-01 | P-0014 | A4 | A4-002 | scope_resolution | persona:celine | E-0082 | {
"kind": "personal",
"ref": "persona:celine"
} | Write your own Slack handling plan for a typical workweek. Focus on non-urgent items, describe the cadence you want to follow, and keep it as a personal operating note rather than a team rule or company-wide standard. | plan | [
"F-0030",
"F-0031",
"F-0032"
] | [] | [
{
"id": "asrt-1",
"kind": "scope_correct",
"fact_id": "F-0032",
"checker": "semantic",
"criterion": "The plan sets a recurring personal cadence with two set times each day for non-urgent Slack work, rather than treating those items as immediate interruptions.",
"weight": 1
}
] | {
"ledger_deltas": [
"F-0030",
"F-0031",
"F-0032"
],
"assertions": [
{
"id": "casrt-1",
"kind": "scope_correct",
"fact_id": "F-0032",
"checker": "semantic",
"criterion": "The plan says non-urgent Slack items should be handled as they come in instead of being saved for... | null | [
"scope_resolution_accuracy"
] | null |
P-0014-02 | P-0014 | A4 | A4-002 | scope_resolution | persona:anouk | E-0082 | {
"kind": "personal",
"ref": "persona:celine"
} | Write your own Slack handling plan for a typical workweek. Focus on non-urgent items, describe the cadence you want to follow, and keep it as a personal operating note rather than a team rule or company-wide standard. | plan | [
"F-0030",
"F-0031",
"F-0032"
] | [] | [
{
"id": "asrt-1",
"kind": "scope_correct",
"fact_id": "F-0032",
"checker": "semantic",
"criterion": "The plan sets a recurring personal cadence with two set times each day for non-urgent Slack work, rather than treating those items as immediate interruptions.",
"weight": 1
}
] | {
"ledger_deltas": [
"F-0030",
"F-0031",
"F-0032"
],
"assertions": [
{
"id": "casrt-1",
"kind": "scope_correct",
"fact_id": "F-0032",
"checker": "semantic",
"criterion": "The plan says non-urgent Slack items should be handled as they come in instead of being saved for... | null | [
"scope_resolution_accuracy"
] | null |
P-0014-03 | P-0014 | A4 | A4-002 | scope_resolution | persona:celine | E-0076 | {
"kind": "personal",
"ref": "persona:celine"
} | Write your own Slack handling plan for a typical workweek. Focus on non-urgent items, describe the cadence you want to follow, and keep it as a personal operating note rather than a team rule or company-wide standard. | plan | [
"F-0030",
"F-0031",
"F-0032"
] | [] | [
{
"id": "asrt-1",
"kind": "scope_correct",
"fact_id": "F-0032",
"checker": "semantic",
"criterion": "The plan sets a recurring personal cadence with two set times each day for non-urgent Slack work, rather than treating those items as immediate interruptions.",
"weight": 1
}
] | {
"ledger_deltas": [
"F-0030",
"F-0031",
"F-0032"
],
"assertions": [
{
"id": "casrt-1",
"kind": "scope_correct",
"fact_id": "F-0032",
"checker": "semantic",
"criterion": "The plan says non-urgent Slack items should be handled as they come in instead of being saved for... | null | [
"scope_resolution_accuracy"
] | null |
P-0015-01 | P-0015 | A7 | A7-002 | staleness | persona:celine | E-0014 | {
"kind": "org_facing",
"ref": null
} | Draft an all-hands intranet blurb announcing the current standup setup for the whole company. Keep it short, practical, and clear enough that everyone can follow the routine without extra manager explanation. | message | [
"F-0036"
] | [] | [
{
"id": "asrt-1",
"kind": "fact_applied",
"fact_id": "F-0036",
"checker": "semantic",
"criterion": "The blurb says org standups are capped at 15 minutes and includes a written asynchronous alternative for people who do not join live.",
"weight": 1
}
] | {
"ledger_deltas": [
"F-0036"
],
"assertions": [
{
"id": "casrt-1",
"kind": "fact_applied",
"fact_id": "F-0036",
"checker": "semantic",
"criterion": "The blurb says org standups are capped at 30 minutes and does not offer a written asynchronous alternative.",
"weight": ... | null | [
"staleness_rate"
] | null |
P-0015-02 | P-0015 | A7 | A7-002 | staleness | persona:celine | E-0013 | {
"kind": "org_facing",
"ref": null
} | Draft an all-hands intranet blurb announcing the current standup setup for the whole company. Keep it short, practical, and clear enough that everyone can follow the routine without extra manager explanation. | message | [
"F-0036"
] | [] | [
{
"id": "asrt-1",
"kind": "fact_applied",
"fact_id": "F-0036",
"checker": "semantic",
"criterion": "The blurb says org standups are capped at 15 minutes and includes a written asynchronous alternative for people who do not join live.",
"weight": 1
}
] | {
"ledger_deltas": [
"F-0036"
],
"assertions": [
{
"id": "casrt-1",
"kind": "fact_applied",
"fact_id": "F-0036",
"checker": "semantic",
"criterion": "The blurb says org standups are capped at 30 minutes and does not offer a written asynchronous alternative.",
"weight": ... | null | [
"staleness_rate"
] | null |
P-0015-03 | P-0015 | A7 | A7-002 | staleness | persona:celine | E-0018 | {
"kind": "org_facing",
"ref": null
} | Draft an all-hands intranet blurb announcing the current standup setup for the whole company. Keep it short, practical, and clear enough that everyone can follow the routine without extra manager explanation. | message | [
"F-0036"
] | [] | [
{
"id": "asrt-1",
"kind": "fact_applied",
"fact_id": "F-0036",
"checker": "semantic",
"criterion": "The blurb says org standups are capped at 15 minutes and includes a written asynchronous alternative for people who do not join live.",
"weight": 1
}
] | {
"ledger_deltas": [
"F-0036"
],
"assertions": [
{
"id": "casrt-1",
"kind": "fact_applied",
"fact_id": "F-0036",
"checker": "semantic",
"criterion": "The blurb says org standups are capped at 30 minutes and does not offer a written asynchronous alternative.",
"weight": ... | null | [
"staleness_rate"
] | null |
P-0016-01 | P-0016 | A7 | A7-002 | staleness | persona:celine | E-0065 | {
"kind": "org_facing",
"ref": null
} | Write a company-wide handbook update describing the latest standup expectations. Keep it concise for a banner announcement and clear enough that nobody needs follow-up questions about how the session should run. | message | [
"F-0037"
] | [
"F-0036"
] | [
{
"id": "asrt-1",
"kind": "fact_applied",
"fact_id": "F-0037",
"checker": "semantic",
"criterion": "The update states that org standups run for 10 minutes and that contributions are limited to blockers.",
"weight": 1
},
{
"id": "asrt-2",
"kind": "fact_absent",
"fact_id": "F-0... | {
"ledger_deltas": [
"F-0037"
],
"assertions": [
{
"id": "casrt-1",
"kind": "fact_applied",
"fact_id": "F-0037",
"checker": "semantic",
"criterion": "The update states that org standups run for 20 minutes and include full attendee status updates.",
"weight": 1
},
... | null | [
"staleness_rate"
] | null |
P-0016-02 | P-0016 | A7 | A7-002 | staleness | persona:celine | E-0064 | {
"kind": "org_facing",
"ref": null
} | Write a company-wide handbook update describing the latest standup expectations. Keep it concise for a banner announcement and clear enough that nobody needs follow-up questions about how the session should run. | message | [
"F-0037"
] | [
"F-0036"
] | [
{
"id": "asrt-1",
"kind": "fact_applied",
"fact_id": "F-0037",
"checker": "semantic",
"criterion": "The update states that org standups run for 10 minutes and that contributions are limited to blockers.",
"weight": 1
},
{
"id": "asrt-2",
"kind": "fact_absent",
"fact_id": "F-0... | {
"ledger_deltas": [
"F-0037"
],
"assertions": [
{
"id": "casrt-1",
"kind": "fact_applied",
"fact_id": "F-0037",
"checker": "semantic",
"criterion": "The update states that org standups run for 20 minutes and include full attendee status updates.",
"weight": 1
},
... | null | [
"staleness_rate"
] | null |
P-0016-03 | P-0016 | A7 | A7-002 | staleness | persona:celine | E-0069 | {
"kind": "org_facing",
"ref": null
} | Write a company-wide handbook update describing the latest standup expectations. Keep it concise for a banner announcement and clear enough that nobody needs follow-up questions about how the session should run. | message | [
"F-0037"
] | [
"F-0036"
] | [
{
"id": "asrt-1",
"kind": "fact_applied",
"fact_id": "F-0037",
"checker": "semantic",
"criterion": "The update states that org standups run for 10 minutes and that contributions are limited to blockers.",
"weight": 1
},
{
"id": "asrt-2",
"kind": "fact_absent",
"fact_id": "F-0... | {
"ledger_deltas": [
"F-0037"
],
"assertions": [
{
"id": "casrt-1",
"kind": "fact_applied",
"fact_id": "F-0037",
"checker": "semantic",
"criterion": "The update states that org standups run for 20 minutes and include full attendee status updates.",
"weight": 1
},
... | null | [
"staleness_rate"
] | null |
P-0017-01 | P-0017 | A7 | A7-002 | staleness | persona:celine | E-0167 | {
"kind": "org_facing",
"ref": null
} | Prepare a company handbook page that explains the current standup rhythm across the org. Make it easy for new hires to follow the weekly pattern and know what participation looks like on ordinary days versus the one shared gathering. | document | [
"F-0038"
] | [
"F-0036",
"F-0037"
] | [
{
"id": "asrt-1",
"kind": "fact_applied",
"fact_id": "F-0038",
"checker": "semantic",
"criterion": "The page says standups are asynchronous by default and that there is a live sync on Wednesdays.",
"weight": 1
},
{
"id": "asrt-2",
"kind": "fact_absent",
"fact_id": "F-0036",
... | {
"ledger_deltas": [
"F-0038"
],
"assertions": [
{
"id": "casrt-1",
"kind": "fact_applied",
"fact_id": "F-0038",
"checker": "semantic",
"criterion": "The page says standups are canceled and replaced by daily written status posts.",
"weight": 1
},
{
"id": "... | null | [
"staleness_rate"
] | null |
P-0017-02 | P-0017 | A7 | A7-002 | staleness | persona:celine | E-0166 | {
"kind": "org_facing",
"ref": null
} | Prepare a company handbook page that explains the current standup rhythm across the org. Make it easy for new hires to follow the weekly pattern and know what participation looks like on ordinary days versus the one shared gathering. | document | [
"F-0038"
] | [
"F-0036",
"F-0037"
] | [
{
"id": "asrt-1",
"kind": "fact_applied",
"fact_id": "F-0038",
"checker": "semantic",
"criterion": "The page says standups are asynchronous by default and that there is a live sync on Wednesdays.",
"weight": 1
},
{
"id": "asrt-2",
"kind": "fact_absent",
"fact_id": "F-0036",
... | {
"ledger_deltas": [
"F-0038"
],
"assertions": [
{
"id": "casrt-1",
"kind": "fact_applied",
"fact_id": "F-0038",
"checker": "semantic",
"criterion": "The page says standups are canceled and replaced by daily written status posts.",
"weight": 1
},
{
"id": "... | null | [
"staleness_rate"
] | null |
P-0017-03 | P-0017 | A7 | A7-002 | staleness | persona:celine | E-0171 | {
"kind": "org_facing",
"ref": null
} | Prepare a company handbook page that explains the current standup rhythm across the org. Make it easy for new hires to follow the weekly pattern and know what participation looks like on ordinary days versus the one shared gathering. | document | [
"F-0038"
] | [
"F-0036",
"F-0037"
] | [
{
"id": "asrt-1",
"kind": "fact_applied",
"fact_id": "F-0038",
"checker": "semantic",
"criterion": "The page says standups are asynchronous by default and that there is a live sync on Wednesdays.",
"weight": 1
},
{
"id": "asrt-2",
"kind": "fact_absent",
"fact_id": "F-0036",
... | {
"ledger_deltas": [
"F-0038"
],
"assertions": [
{
"id": "casrt-1",
"kind": "fact_applied",
"fact_id": "F-0038",
"checker": "semantic",
"criterion": "The page says standups are canceled and replaced by daily written status posts.",
"weight": 1
},
{
"id": "... | null | [
"staleness_rate"
] | null |
P-0018-01 | P-0018 | A7 | A7-002 | historical | persona:celine | E-0170 | {
"kind": "org_facing",
"ref": null
} | Write a short audit entry for the company handbook that records the standup setup used in the earlier version of the policy, so operations can reconcile older calendar holds with archived guidance. | review | [
"F-0036"
] | [] | [
{
"id": "asrt-1",
"kind": "fact_applied",
"fact_id": "F-0036",
"checker": "semantic",
"criterion": "The audit entry recounts that org standups were capped at 15 minutes and had a written asynchronous alternative.",
"weight": 1
}
] | {
"ledger_deltas": [
"F-0036"
],
"assertions": [
{
"id": "casrt-1",
"kind": "fact_applied",
"fact_id": "F-0036",
"checker": "semantic",
"criterion": "The audit entry recounts that org standups were capped at 30 minutes and had no written asynchronous alternative.",
"wei... | null | [
"history_retention"
] | null |
P-0018-02 | P-0018 | A7 | A7-002 | historical | persona:celine | E-0166 | {
"kind": "org_facing",
"ref": null
} | Write a short audit entry for the company handbook that records the standup setup used in the earlier version of the policy, so operations can reconcile older calendar holds with archived guidance. | review | [
"F-0036"
] | [] | [
{
"id": "asrt-1",
"kind": "fact_applied",
"fact_id": "F-0036",
"checker": "semantic",
"criterion": "The audit entry recounts that org standups were capped at 15 minutes and had a written asynchronous alternative.",
"weight": 1
}
] | {
"ledger_deltas": [
"F-0036"
],
"assertions": [
{
"id": "casrt-1",
"kind": "fact_applied",
"fact_id": "F-0036",
"checker": "semantic",
"criterion": "The audit entry recounts that org standups were capped at 30 minutes and had no written asynchronous alternative.",
"wei... | null | [
"history_retention"
] | null |
P-0018-03 | P-0018 | A7 | A7-002 | historical | persona:celine | E-0171 | {
"kind": "org_facing",
"ref": null
} | Write a short audit entry for the company handbook that records the standup setup used in the earlier version of the policy, so operations can reconcile older calendar holds with archived guidance. | review | [
"F-0036"
] | [] | [
{
"id": "asrt-1",
"kind": "fact_applied",
"fact_id": "F-0036",
"checker": "semantic",
"criterion": "The audit entry recounts that org standups were capped at 15 minutes and had a written asynchronous alternative.",
"weight": 1
}
] | {
"ledger_deltas": [
"F-0036"
],
"assertions": [
{
"id": "casrt-1",
"kind": "fact_applied",
"fact_id": "F-0036",
"checker": "semantic",
"criterion": "The audit entry recounts that org standups were capped at 30 minutes and had no written asynchronous alternative.",
"wei... | null | [
"history_retention"
] | null |
P-0019-01 | P-0019 | A1 | A1-003 | application | persona:mei | E-0102 | {
"kind": "team_internal",
"ref": "team:platform"
} | Write a short platform-team checklist for handling Growth travel requests for an upcoming offsite. The checklist should state the timing gate a request has to satisfy before the team proceeds, plus the fallback path when someone comes in late. Keep it operational and ready to paste into the team runbook. | checklist | [
"F-0042"
] | [] | [
{
"id": "asrt-1",
"kind": "fact_applied",
"fact_id": "F-0042",
"checker": "semantic",
"criterion": "The checklist requires Growth travel bookings at least fourteen days ahead of the trip.",
"weight": 1
}
] | {
"ledger_deltas": [
"F-0042"
],
"assertions": [
{
"id": "casrt-1",
"kind": "fact_applied",
"fact_id": "F-0042",
"checker": "semantic",
"criterion": "The checklist allows Growth travel bookings with as little as two days' notice.",
"weight": 1
}
]
} | null | [
"propagation_latency"
] | {
"offsets_events": [
5,
20,
60
],
"metric": "propagation_latency"
} |
P-0019-02 | P-0019 | A1 | A1-003 | application | persona:mei | E-0117 | {
"kind": "team_internal",
"ref": "team:platform"
} | Write a short platform-team checklist for handling Growth travel requests for an upcoming offsite. The checklist should state the timing gate a request has to satisfy before the team proceeds, plus the fallback path when someone comes in late. Keep it operational and ready to paste into the team runbook. | checklist | [
"F-0042"
] | [] | [
{
"id": "asrt-1",
"kind": "fact_applied",
"fact_id": "F-0042",
"checker": "semantic",
"criterion": "The checklist requires Growth travel bookings at least fourteen days ahead of the trip.",
"weight": 1
}
] | {
"ledger_deltas": [
"F-0042"
],
"assertions": [
{
"id": "casrt-1",
"kind": "fact_applied",
"fact_id": "F-0042",
"checker": "semantic",
"criterion": "The checklist allows Growth travel bookings with as little as two days' notice.",
"weight": 1
}
]
} | null | [
"propagation_latency"
] | {
"offsets_events": [
5,
20,
60
],
"metric": "propagation_latency"
} |
P-0019-03 | P-0019 | A1 | A1-003 | application | persona:mei | E-0157 | {
"kind": "team_internal",
"ref": "team:platform"
} | Write a short platform-team checklist for handling Growth travel requests for an upcoming offsite. The checklist should state the timing gate a request has to satisfy before the team proceeds, plus the fallback path when someone comes in late. Keep it operational and ready to paste into the team runbook. | checklist | [
"F-0042"
] | [] | [
{
"id": "asrt-1",
"kind": "fact_applied",
"fact_id": "F-0042",
"checker": "semantic",
"criterion": "The checklist requires Growth travel bookings at least fourteen days ahead of the trip.",
"weight": 1
}
] | {
"ledger_deltas": [
"F-0042"
],
"assertions": [
{
"id": "casrt-1",
"kind": "fact_applied",
"fact_id": "F-0042",
"checker": "semantic",
"criterion": "The checklist allows Growth travel bookings with as little as two days' notice.",
"weight": 1
}
]
} | null | [
"propagation_latency"
] | {
"offsets_events": [
5,
20,
60
],
"metric": "propagation_latency"
} |
P-0020-01 | P-0020 | A2 | A2-003 | application | persona:celine | E-0065 | {
"kind": "team_internal",
"ref": "team:growth"
} | Create a Growth-team checklist for handling platform vendor bills. Keep it practical for the ops channel, and include the dollar cutoff that changes the routing path plus the order of handoffs before funds are sent. | checklist | [
"F-0047"
] | [] | [
{
"id": "asrt-1",
"kind": "fact_applied",
"fact_id": "F-0047",
"checker": "semantic",
"criterion": "The checklist sends platform invoices above $5,000 to finance for approval before payment.",
"weight": 1
}
] | {
"ledger_deltas": [
"F-0047"
],
"assertions": [
{
"id": "casrt-1",
"kind": "fact_applied",
"fact_id": "F-0047",
"checker": "semantic",
"criterion": "The checklist says platform invoices under $10,000 can be paid without finance review.",
"weight": 1
}
]
} | null | [
"proactive_application"
] | {
"offsets_events": [
4,
30,
80
],
"metric": "proactive_application"
} |
P-0020-02 | P-0020 | A2 | A2-003 | application | persona:celine | E-0115 | {
"kind": "team_internal",
"ref": "team:growth"
} | Create a Growth-team checklist for handling platform vendor bills. Keep it practical for the ops channel, and include the dollar cutoff that changes the routing path plus the order of handoffs before funds are sent. | checklist | [
"F-0047"
] | [] | [
{
"id": "asrt-1",
"kind": "fact_applied",
"fact_id": "F-0047",
"checker": "semantic",
"criterion": "The checklist sends platform invoices above $5,000 to finance for approval before payment.",
"weight": 1
}
] | {
"ledger_deltas": [
"F-0047"
],
"assertions": [
{
"id": "casrt-1",
"kind": "fact_applied",
"fact_id": "F-0047",
"checker": "semantic",
"criterion": "The checklist says platform invoices under $10,000 can be paid without finance review.",
"weight": 1
}
]
} | null | [
"proactive_application"
] | {
"offsets_events": [
4,
30,
80
],
"metric": "proactive_application"
} |
P-0020-03 | P-0020 | A2 | A2-003 | application | persona:celine | E-0039 | {
"kind": "team_internal",
"ref": "team:growth"
} | Create a Growth-team checklist for handling platform vendor bills. Keep it practical for the ops channel, and include the dollar cutoff that changes the routing path plus the order of handoffs before funds are sent. | checklist | [
"F-0047"
] | [] | [
{
"id": "asrt-1",
"kind": "fact_applied",
"fact_id": "F-0047",
"checker": "semantic",
"criterion": "The checklist sends platform invoices above $5,000 to finance for approval before payment.",
"weight": 1
}
] | {
"ledger_deltas": [
"F-0047"
],
"assertions": [
{
"id": "casrt-1",
"kind": "fact_applied",
"fact_id": "F-0047",
"checker": "semantic",
"criterion": "The checklist says platform invoices under $10,000 can be paid without finance review.",
"weight": 1
}
]
} | null | [
"proactive_application"
] | {
"offsets_events": [
4,
30,
80
],
"metric": "proactive_application"
} |
P-0021-01 | P-0021 | A4 | A4-003 | scope_resolution | persona:mei | E-0046 | {
"kind": "org_facing",
"ref": null
} | Draft a company-wide note that sets the writing standard for public-facing product text. Make it usable by any team at the company, and frame it as a shared rule rather than something tied to one function or your own habits. Keep it crisp enough for an all-hands follow-up. | document | [
"F-0051",
"F-0052",
"F-0053"
] | [] | [
{
"id": "asrt-1",
"kind": "scope_correct",
"fact_id": "F-0051",
"checker": "semantic",
"criterion": "The note sets a company-wide standard that public-facing product text should be easy for a broad audience to understand and free of specialist terminology.",
"weight": 1
},
{
"id": "a... | {
"ledger_deltas": [
"F-0051",
"F-0052",
"F-0053"
],
"assertions": [
{
"id": "casrt-1",
"kind": "scope_correct",
"fact_id": "F-0051",
"checker": "semantic",
"criterion": "The note treats brand voice guidelines as optional for internal-only company documents.",
"... | null | [
"scope_resolution_accuracy"
] | null |
P-0021-02 | P-0021 | A4 | A4-003 | scope_resolution | persona:mei | E-0040 | {
"kind": "org_facing",
"ref": null
} | Draft a company-wide note that sets the writing standard for public-facing product text. Make it usable by any team at the company, and frame it as a shared rule rather than something tied to one function or your own habits. Keep it crisp enough for an all-hands follow-up. | document | [
"F-0051",
"F-0052",
"F-0053"
] | [] | [
{
"id": "asrt-1",
"kind": "scope_correct",
"fact_id": "F-0051",
"checker": "semantic",
"criterion": "The note sets a company-wide standard that public-facing product text should be easy for a broad audience to understand and free of specialist terminology.",
"weight": 1
},
{
"id": "a... | {
"ledger_deltas": [
"F-0051",
"F-0052",
"F-0053"
],
"assertions": [
{
"id": "casrt-1",
"kind": "scope_correct",
"fact_id": "F-0051",
"checker": "semantic",
"criterion": "The note treats brand voice guidelines as optional for internal-only company documents.",
"... | null | [
"scope_resolution_accuracy"
] | null |
P-0021-03 | P-0021 | A4 | A4-003 | scope_resolution | persona:mei | E-0045 | {
"kind": "org_facing",
"ref": null
} | Draft a company-wide note that sets the writing standard for public-facing product text. Make it usable by any team at the company, and frame it as a shared rule rather than something tied to one function or your own habits. Keep it crisp enough for an all-hands follow-up. | document | [
"F-0051",
"F-0052",
"F-0053"
] | [] | [
{
"id": "asrt-1",
"kind": "scope_correct",
"fact_id": "F-0051",
"checker": "semantic",
"criterion": "The note sets a company-wide standard that public-facing product text should be easy for a broad audience to understand and free of specialist terminology.",
"weight": 1
},
{
"id": "a... | {
"ledger_deltas": [
"F-0051",
"F-0052",
"F-0053"
],
"assertions": [
{
"id": "casrt-1",
"kind": "scope_correct",
"fact_id": "F-0051",
"checker": "semantic",
"criterion": "The note treats brand voice guidelines as optional for internal-only company documents.",
"... | null | [
"scope_resolution_accuracy"
] | null |
P-0022-01 | P-0022 | A4 | A4-003 | scope_resolution | persona:mei | E-0046 | {
"kind": "team_internal",
"ref": "team:platform"
} | Draft a brief guidance note for the platform team to use when helping on launch blurbs. Keep the note scoped to team practice, not a company standard or a reminder about your own writing habits. Make it direct enough to drop into the team wiki. | document | [
"F-0051",
"F-0052",
"F-0053"
] | [] | [
{
"id": "asrt-1",
"kind": "scope_correct",
"fact_id": "F-0052",
"checker": "semantic",
"criterion": "The note tells the platform team to shape launch blurbs around the energetic style used by Growth marketing, rather than around a general company clarity rule.",
"weight": 1
},
{
"id"... | {
"ledger_deltas": [
"F-0051",
"F-0052",
"F-0053"
],
"assertions": [
{
"id": "casrt-1",
"kind": "scope_correct",
"fact_id": "F-0052",
"checker": "semantic",
"criterion": "The note tells the platform team to use a restrained, formal style for launch blurbs.",
"we... | null | [
"scope_resolution_accuracy"
] | null |
P-0022-02 | P-0022 | A4 | A4-003 | scope_resolution | persona:mei | E-0040 | {
"kind": "team_internal",
"ref": "team:platform"
} | Draft a brief guidance note for the platform team to use when helping on launch blurbs. Keep the note scoped to team practice, not a company standard or a reminder about your own writing habits. Make it direct enough to drop into the team wiki. | document | [
"F-0051",
"F-0052",
"F-0053"
] | [] | [
{
"id": "asrt-1",
"kind": "scope_correct",
"fact_id": "F-0052",
"checker": "semantic",
"criterion": "The note tells the platform team to shape launch blurbs around the energetic style used by Growth marketing, rather than around a general company clarity rule.",
"weight": 1
},
{
"id"... | {
"ledger_deltas": [
"F-0051",
"F-0052",
"F-0053"
],
"assertions": [
{
"id": "casrt-1",
"kind": "scope_correct",
"fact_id": "F-0052",
"checker": "semantic",
"criterion": "The note tells the platform team to use a restrained, formal style for launch blurbs.",
"we... | null | [
"scope_resolution_accuracy"
] | null |
P-0022-03 | P-0022 | A4 | A4-003 | scope_resolution | persona:mei | E-0045 | {
"kind": "team_internal",
"ref": "team:platform"
} | Draft a brief guidance note for the platform team to use when helping on launch blurbs. Keep the note scoped to team practice, not a company standard or a reminder about your own writing habits. Make it direct enough to drop into the team wiki. | document | [
"F-0051",
"F-0052",
"F-0053"
] | [] | [
{
"id": "asrt-1",
"kind": "scope_correct",
"fact_id": "F-0052",
"checker": "semantic",
"criterion": "The note tells the platform team to shape launch blurbs around the energetic style used by Growth marketing, rather than around a general company clarity rule.",
"weight": 1
},
{
"id"... | {
"ledger_deltas": [
"F-0051",
"F-0052",
"F-0053"
],
"assertions": [
{
"id": "casrt-1",
"kind": "scope_correct",
"fact_id": "F-0052",
"checker": "semantic",
"criterion": "The note tells the platform team to use a restrained, formal style for launch blurbs.",
"we... | null | [
"scope_resolution_accuracy"
] | null |
P-0023-01 | P-0023 | A4 | A4-003 | scope_resolution | persona:mei | E-0046 | {
"kind": "personal",
"ref": "persona:mei"
} | Write a private checklist for yourself before you draft launch blurbs later today. Keep it as working notes about how you want to write, not team guidance or a company standard. Make each line actionable so you can use it during a quick self-edit. | checklist | [
"F-0051",
"F-0052",
"F-0053"
] | [] | [
{
"id": "asrt-1",
"kind": "scope_correct",
"fact_id": "F-0053",
"checker": "semantic",
"criterion": "The checklist reflects a personal editing preference for brief sentences and digit-based quantities.",
"weight": 1
}
] | {
"ledger_deltas": [
"F-0051",
"F-0052",
"F-0053"
],
"assertions": [
{
"id": "casrt-1",
"kind": "scope_correct",
"fact_id": "F-0053",
"checker": "semantic",
"criterion": "The checklist reflects a personal editing preference for longer sentences and quantities written ... | null | [
"scope_resolution_accuracy"
] | null |
P-0023-02 | P-0023 | A4 | A4-003 | scope_resolution | persona:mei | E-0040 | {
"kind": "personal",
"ref": "persona:mei"
} | Write a private checklist for yourself before you draft launch blurbs later today. Keep it as working notes about how you want to write, not team guidance or a company standard. Make each line actionable so you can use it during a quick self-edit. | checklist | [
"F-0051",
"F-0052",
"F-0053"
] | [] | [
{
"id": "asrt-1",
"kind": "scope_correct",
"fact_id": "F-0053",
"checker": "semantic",
"criterion": "The checklist reflects a personal editing preference for brief sentences and digit-based quantities.",
"weight": 1
}
] | {
"ledger_deltas": [
"F-0051",
"F-0052",
"F-0053"
],
"assertions": [
{
"id": "casrt-1",
"kind": "scope_correct",
"fact_id": "F-0053",
"checker": "semantic",
"criterion": "The checklist reflects a personal editing preference for longer sentences and quantities written ... | null | [
"scope_resolution_accuracy"
] | null |
P-0023-03 | P-0023 | A4 | A4-003 | scope_resolution | persona:mei | E-0045 | {
"kind": "personal",
"ref": "persona:mei"
} | Write a private checklist for yourself before you draft launch blurbs later today. Keep it as working notes about how you want to write, not team guidance or a company standard. Make each line actionable so you can use it during a quick self-edit. | checklist | [
"F-0051",
"F-0052",
"F-0053"
] | [] | [
{
"id": "asrt-1",
"kind": "scope_correct",
"fact_id": "F-0053",
"checker": "semantic",
"criterion": "The checklist reflects a personal editing preference for brief sentences and digit-based quantities.",
"weight": 1
}
] | {
"ledger_deltas": [
"F-0051",
"F-0052",
"F-0053"
],
"assertions": [
{
"id": "casrt-1",
"kind": "scope_correct",
"fact_id": "F-0053",
"checker": "semantic",
"criterion": "The checklist reflects a personal editing preference for longer sentences and quantities written ... | null | [
"scope_resolution_accuracy"
] | null |
P-0024-01 | P-0024 | A7 | A7-003 | staleness | persona:yuki | E-0014 | {
"kind": "org_facing",
"ref": null
} | Prepare an all-hands note announcing the bug triage handoff schedule for the next month. Include how often the owner changes and who is in the rotation, so other teams can plan where to send issues. Keep the wording formal and straightforward. | message | [
"F-0057"
] | [] | [
{
"id": "asrt-1",
"kind": "fact_applied",
"fact_id": "F-0057",
"checker": "semantic",
"criterion": "The note describes bug triage as changing hands once per week among the platform group; it does not describe a day-by-day turnover.",
"weight": 1
}
] | {
"ledger_deltas": [
"F-0057"
],
"assertions": [
{
"id": "casrt-1",
"kind": "fact_applied",
"fact_id": "F-0057",
"checker": "semantic",
"criterion": "The note describes bug triage as changing hands each day among the full platform group; it does not describe a once-per-week t... | null | [
"staleness_rate"
] | null |
P-0024-02 | P-0024 | A7 | A7-003 | staleness | persona:yuki | E-0013 | {
"kind": "org_facing",
"ref": null
} | Prepare an all-hands note announcing the bug triage handoff schedule for the next month. Include how often the owner changes and who is in the rotation, so other teams can plan where to send issues. Keep the wording formal and straightforward. | message | [
"F-0057"
] | [] | [
{
"id": "asrt-1",
"kind": "fact_applied",
"fact_id": "F-0057",
"checker": "semantic",
"criterion": "The note describes bug triage as changing hands once per week among the platform group; it does not describe a day-by-day turnover.",
"weight": 1
}
] | {
"ledger_deltas": [
"F-0057"
],
"assertions": [
{
"id": "casrt-1",
"kind": "fact_applied",
"fact_id": "F-0057",
"checker": "semantic",
"criterion": "The note describes bug triage as changing hands each day among the full platform group; it does not describe a once-per-week t... | null | [
"staleness_rate"
] | null |
P-0024-03 | P-0024 | A7 | A7-003 | staleness | persona:yuki | E-0018 | {
"kind": "org_facing",
"ref": null
} | Prepare an all-hands note announcing the bug triage handoff schedule for the next month. Include how often the owner changes and who is in the rotation, so other teams can plan where to send issues. Keep the wording formal and straightforward. | message | [
"F-0057"
] | [] | [
{
"id": "asrt-1",
"kind": "fact_applied",
"fact_id": "F-0057",
"checker": "semantic",
"criterion": "The note describes bug triage as changing hands once per week among the platform group; it does not describe a day-by-day turnover.",
"weight": 1
}
] | {
"ledger_deltas": [
"F-0057"
],
"assertions": [
{
"id": "casrt-1",
"kind": "fact_applied",
"fact_id": "F-0057",
"checker": "semantic",
"criterion": "The note describes bug triage as changing hands each day among the full platform group; it does not describe a once-per-week t... | null | [
"staleness_rate"
] | null |
P-0025-01 | P-0025 | A7 | A7-003 | staleness | persona:yuki | E-0065 | {
"kind": "org_facing",
"ref": null
} | Draft a company-wide note for support, product, and engineering that explains the current bug triage coverage model for the next quarter. Include a concrete July-through-August example showing when the named contact changes and how readers should route issues if the listed contact drops out mid-cycle. | document | [
"F-0058"
] | [
"F-0057"
] | [
{
"id": "asrt-1",
"kind": "fact_applied",
"fact_id": "F-0058",
"checker": "semantic",
"criterion": "The note describes bug triage rotating every two weeks with a backup assignee in place.",
"weight": 1
},
{
"id": "asrt-2",
"kind": "fact_absent",
"fact_id": "F-0057",
"chec... | {
"ledger_deltas": [
"F-0058"
],
"assertions": [
{
"id": "casrt-1",
"kind": "fact_applied",
"fact_id": "F-0058",
"checker": "semantic",
"criterion": "The note presents one standing point person for bug triage on a month-by-month cycle and does not include a fallback contact."... | null | [
"staleness_rate"
] | null |
P-0025-02 | P-0025 | A7 | A7-003 | staleness | persona:yuki | E-0064 | {
"kind": "org_facing",
"ref": null
} | Draft a company-wide note for support, product, and engineering that explains the current bug triage coverage model for the next quarter. Include a concrete July-through-August example showing when the named contact changes and how readers should route issues if the listed contact drops out mid-cycle. | document | [
"F-0058"
] | [
"F-0057"
] | [
{
"id": "asrt-1",
"kind": "fact_applied",
"fact_id": "F-0058",
"checker": "semantic",
"criterion": "The note describes bug triage rotating every two weeks with a backup assignee in place.",
"weight": 1
},
{
"id": "asrt-2",
"kind": "fact_absent",
"fact_id": "F-0057",
"chec... | {
"ledger_deltas": [
"F-0058"
],
"assertions": [
{
"id": "casrt-1",
"kind": "fact_applied",
"fact_id": "F-0058",
"checker": "semantic",
"criterion": "The note presents one standing point person for bug triage on a month-by-month cycle and does not include a fallback contact."... | null | [
"staleness_rate"
] | null |
P-0025-03 | P-0025 | A7 | A7-003 | staleness | persona:yuki | E-0069 | {
"kind": "org_facing",
"ref": null
} | Draft a company-wide note for support, product, and engineering that explains the current bug triage coverage model for the next quarter. Include a concrete July-through-August example showing when the named contact changes and how readers should route issues if the listed contact drops out mid-cycle. | document | [
"F-0058"
] | [
"F-0057"
] | [
{
"id": "asrt-1",
"kind": "fact_applied",
"fact_id": "F-0058",
"checker": "semantic",
"criterion": "The note describes bug triage rotating every two weeks with a backup assignee in place.",
"weight": 1
},
{
"id": "asrt-2",
"kind": "fact_absent",
"fact_id": "F-0057",
"chec... | {
"ledger_deltas": [
"F-0058"
],
"assertions": [
{
"id": "casrt-1",
"kind": "fact_applied",
"fact_id": "F-0058",
"checker": "semantic",
"criterion": "The note presents one standing point person for bug triage on a month-by-month cycle and does not include a fallback contact."... | null | [
"staleness_rate"
] | null |
P-0026-01 | P-0026 | A7 | A7-003 | staleness | persona:yuki | E-0167 | {
"kind": "org_facing",
"ref": null
} | Write a company announcement that explains the current bug triage operating model and tells people where to check for the active contact each workday. Include a short example covering Monday through Friday so teams route escalations consistently. | message | [
"F-0059"
] | [
"F-0057",
"F-0058"
] | [
{
"id": "asrt-1",
"kind": "fact_applied",
"fact_id": "F-0059",
"checker": "semantic",
"criterion": "The announcement tells readers that bug triage coverage changes day by day and that the active contact can be found in Slack.",
"weight": 1
},
{
"id": "asrt-2",
"kind": "fact_absen... | {
"ledger_deltas": [
"F-0059"
],
"assertions": [
{
"id": "casrt-1",
"kind": "fact_applied",
"fact_id": "F-0059",
"checker": "semantic",
"criterion": "The announcement describes bug triage as being assigned informally case by case, without a standing handoff plan or published ... | null | [
"staleness_rate"
] | null |
P-0026-02 | P-0026 | A7 | A7-003 | staleness | persona:yuki | E-0166 | {
"kind": "org_facing",
"ref": null
} | Write a company announcement that explains the current bug triage operating model and tells people where to check for the active contact each workday. Include a short example covering Monday through Friday so teams route escalations consistently. | message | [
"F-0059"
] | [
"F-0057",
"F-0058"
] | [
{
"id": "asrt-1",
"kind": "fact_applied",
"fact_id": "F-0059",
"checker": "semantic",
"criterion": "The announcement tells readers that bug triage coverage changes day by day and that the active contact can be found in Slack.",
"weight": 1
},
{
"id": "asrt-2",
"kind": "fact_absen... | {
"ledger_deltas": [
"F-0059"
],
"assertions": [
{
"id": "casrt-1",
"kind": "fact_applied",
"fact_id": "F-0059",
"checker": "semantic",
"criterion": "The announcement describes bug triage as being assigned informally case by case, without a standing handoff plan or published ... | null | [
"staleness_rate"
] | null |
P-0026-03 | P-0026 | A7 | A7-003 | staleness | persona:yuki | E-0171 | {
"kind": "org_facing",
"ref": null
} | Write a company announcement that explains the current bug triage operating model and tells people where to check for the active contact each workday. Include a short example covering Monday through Friday so teams route escalations consistently. | message | [
"F-0059"
] | [
"F-0057",
"F-0058"
] | [
{
"id": "asrt-1",
"kind": "fact_applied",
"fact_id": "F-0059",
"checker": "semantic",
"criterion": "The announcement tells readers that bug triage coverage changes day by day and that the active contact can be found in Slack.",
"weight": 1
},
{
"id": "asrt-2",
"kind": "fact_absen... | {
"ledger_deltas": [
"F-0059"
],
"assertions": [
{
"id": "casrt-1",
"kind": "fact_applied",
"fact_id": "F-0059",
"checker": "semantic",
"criterion": "The announcement describes bug triage as being assigned informally case by case, without a standing handoff plan or published ... | null | [
"staleness_rate"
] | null |
P-0027-01 | P-0027 | A7 | A7-003 | historical | persona:yuki | E-0170 | {
"kind": "org_facing",
"ref": null
} | Write a brief handbook changelog entry for the engineering org that documents the earlier bug triage model used before the latest update. Make it specific enough for an audit reader to understand who carried the duty and how often the handoff happened at that time. | document | [
"F-0057"
] | [] | [
{
"id": "asrt-1",
"kind": "fact_applied",
"fact_id": "F-0057",
"checker": "semantic",
"criterion": "The changelog recounts the earlier bug triage model as a once-per-week handoff among the platform group, not a day-by-day rotation.",
"weight": 1
}
] | {
"ledger_deltas": [
"F-0057"
],
"assertions": [
{
"id": "casrt-1",
"kind": "fact_applied",
"fact_id": "F-0057",
"checker": "semantic",
"criterion": "The changelog recounts the earlier bug triage model as a day-by-day handoff among the full platform group, not a once-per-week... | null | [
"history_retention"
] | null |
P-0027-02 | P-0027 | A7 | A7-003 | historical | persona:yuki | E-0166 | {
"kind": "org_facing",
"ref": null
} | Write a brief handbook changelog entry for the engineering org that documents the earlier bug triage model used before the latest update. Make it specific enough for an audit reader to understand who carried the duty and how often the handoff happened at that time. | document | [
"F-0057"
] | [] | [
{
"id": "asrt-1",
"kind": "fact_applied",
"fact_id": "F-0057",
"checker": "semantic",
"criterion": "The changelog recounts the earlier bug triage model as a once-per-week handoff among the platform group, not a day-by-day rotation.",
"weight": 1
}
] | {
"ledger_deltas": [
"F-0057"
],
"assertions": [
{
"id": "casrt-1",
"kind": "fact_applied",
"fact_id": "F-0057",
"checker": "semantic",
"criterion": "The changelog recounts the earlier bug triage model as a day-by-day handoff among the full platform group, not a once-per-week... | null | [
"history_retention"
] | null |
P-0027-03 | P-0027 | A7 | A7-003 | historical | persona:yuki | E-0171 | {
"kind": "org_facing",
"ref": null
} | Write a brief handbook changelog entry for the engineering org that documents the earlier bug triage model used before the latest update. Make it specific enough for an audit reader to understand who carried the duty and how often the handoff happened at that time. | document | [
"F-0057"
] | [] | [
{
"id": "asrt-1",
"kind": "fact_applied",
"fact_id": "F-0057",
"checker": "semantic",
"criterion": "The changelog recounts the earlier bug triage model as a once-per-week handoff among the platform group, not a day-by-day rotation.",
"weight": 1
}
] | {
"ledger_deltas": [
"F-0057"
],
"assertions": [
{
"id": "casrt-1",
"kind": "fact_applied",
"fact_id": "F-0057",
"checker": "semantic",
"criterion": "The changelog recounts the earlier bug triage model as a day-by-day handoff among the full platform group, not a once-per-week... | null | [
"history_retention"
] | null |
P-0028-01 | P-0028 | A1 | A1-004 | application | persona:kofi | E-0057 | {
"kind": "team_internal",
"ref": "team:growth"
} | Draft a Growth-team maintenance checklist for runbooks. Make it usable in your next team meeting, with the recurring refresh cadence, who tracks the next due date, and what kicks off the update process. | checklist | [
"F-0063"
] | [] | [
{
"id": "asrt-1",
"kind": "fact_applied",
"fact_id": "F-0063",
"checker": "semantic",
"criterion": "The checklist puts runbooks on a recurring 60-day review cycle rather than waiting for major incidents.",
"weight": 1
}
] | {
"ledger_deltas": [
"F-0063"
],
"assertions": [
{
"id": "casrt-1",
"kind": "fact_applied",
"fact_id": "F-0063",
"checker": "semantic",
"criterion": "The checklist calls for formal runbook review only after major incidents occur.",
"weight": 1
}
]
} | null | [
"propagation_latency"
] | {
"offsets_events": [
5,
20,
60
],
"metric": "propagation_latency"
} |
P-0028-02 | P-0028 | A1 | A1-004 | application | persona:kofi | E-0072 | {
"kind": "team_internal",
"ref": "team:growth"
} | Draft a Growth-team maintenance checklist for runbooks. Make it usable in your next team meeting, with the recurring refresh cadence, who tracks the next due date, and what kicks off the update process. | checklist | [
"F-0063"
] | [] | [
{
"id": "asrt-1",
"kind": "fact_applied",
"fact_id": "F-0063",
"checker": "semantic",
"criterion": "The checklist puts runbooks on a recurring 60-day review cycle rather than waiting for major incidents.",
"weight": 1
}
] | {
"ledger_deltas": [
"F-0063"
],
"assertions": [
{
"id": "casrt-1",
"kind": "fact_applied",
"fact_id": "F-0063",
"checker": "semantic",
"criterion": "The checklist calls for formal runbook review only after major incidents occur.",
"weight": 1
}
]
} | null | [
"propagation_latency"
] | {
"offsets_events": [
5,
20,
60
],
"metric": "propagation_latency"
} |
P-0028-03 | P-0028 | A1 | A1-004 | application | persona:kofi | E-0112 | {
"kind": "team_internal",
"ref": "team:growth"
} | Draft a Growth-team maintenance checklist for runbooks. Make it usable in your next team meeting, with the recurring refresh cadence, who tracks the next due date, and what kicks off the update process. | checklist | [
"F-0063"
] | [] | [
{
"id": "asrt-1",
"kind": "fact_applied",
"fact_id": "F-0063",
"checker": "semantic",
"criterion": "The checklist puts runbooks on a recurring 60-day review cycle rather than waiting for major incidents.",
"weight": 1
}
] | {
"ledger_deltas": [
"F-0063"
],
"assertions": [
{
"id": "casrt-1",
"kind": "fact_applied",
"fact_id": "F-0063",
"checker": "semantic",
"criterion": "The checklist calls for formal runbook review only after major incidents occur.",
"weight": 1
}
]
} | null | [
"propagation_latency"
] | {
"offsets_events": [
5,
20,
60
],
"metric": "propagation_latency"
} |
P-0029-01 | P-0029 | A2 | A2-004 | application | persona:otto | E-0053 | {
"kind": "team_internal",
"ref": "team:growth"
} | Draft a short follow-up checklist for the growth team to use right after a retrospective. Make it operational rather than reflective: list the required fields for each action item, state how quickly those fields need to be filled in, and make the checklist ready to paste into the team workspace. | checklist | [
"F-0067"
] | [] | [
{
"id": "asrt-1",
"kind": "fact_applied",
"fact_id": "F-0067",
"checker": "semantic",
"criterion": "The checklist requires each action item to name a responsible person.",
"weight": 1
},
{
"id": "asrt-2",
"kind": "fact_applied",
"fact_id": "F-0067",
"checker": "semantic",... | {
"ledger_deltas": [
"F-0067"
],
"assertions": [
{
"id": "casrt-1",
"kind": "fact_applied",
"fact_id": "F-0067",
"checker": "semantic",
"criterion": "The checklist allows action items to remain unassigned.",
"weight": 1
},
{
"id": "casrt-2",
"kind": ... | null | [
"proactive_application"
] | {
"offsets_events": [
4,
30,
80
],
"metric": "proactive_application"
} |
P-0029-02 | P-0029 | A2 | A2-004 | application | persona:otto | E-0103 | {
"kind": "team_internal",
"ref": "team:growth"
} | Draft a short follow-up checklist for the growth team to use right after a retrospective. Make it operational rather than reflective: list the required fields for each action item, state how quickly those fields need to be filled in, and make the checklist ready to paste into the team workspace. | checklist | [
"F-0067"
] | [] | [
{
"id": "asrt-1",
"kind": "fact_applied",
"fact_id": "F-0067",
"checker": "semantic",
"criterion": "The checklist requires each action item to name a responsible person.",
"weight": 1
},
{
"id": "asrt-2",
"kind": "fact_applied",
"fact_id": "F-0067",
"checker": "semantic",... | {
"ledger_deltas": [
"F-0067"
],
"assertions": [
{
"id": "casrt-1",
"kind": "fact_applied",
"fact_id": "F-0067",
"checker": "semantic",
"criterion": "The checklist allows action items to remain unassigned.",
"weight": 1
},
{
"id": "casrt-2",
"kind": ... | null | [
"proactive_application"
] | {
"offsets_events": [
4,
30,
80
],
"metric": "proactive_application"
} |
P-0029-03 | P-0029 | A2 | A2-004 | application | persona:otto | E-0027 | {
"kind": "team_internal",
"ref": "team:growth"
} | Draft a short follow-up checklist for the growth team to use right after a retrospective. Make it operational rather than reflective: list the required fields for each action item, state how quickly those fields need to be filled in, and make the checklist ready to paste into the team workspace. | checklist | [
"F-0067"
] | [] | [
{
"id": "asrt-1",
"kind": "fact_applied",
"fact_id": "F-0067",
"checker": "semantic",
"criterion": "The checklist requires each action item to name a responsible person.",
"weight": 1
},
{
"id": "asrt-2",
"kind": "fact_applied",
"fact_id": "F-0067",
"checker": "semantic",... | {
"ledger_deltas": [
"F-0067"
],
"assertions": [
{
"id": "casrt-1",
"kind": "fact_applied",
"fact_id": "F-0067",
"checker": "semantic",
"criterion": "The checklist allows action items to remain unassigned.",
"weight": 1
},
{
"id": "casrt-2",
"kind": ... | null | [
"proactive_application"
] | {
"offsets_events": [
4,
30,
80
],
"metric": "proactive_application"
} |
P-0030-01 | P-0030 | A4 | A4-004 | scope_resolution | persona:otto | E-0124 | {
"kind": "org_facing",
"ref": null
} | Draft a company-wide engineering handbook note for the shared pull-request checklist. Keep it concise and directive, suitable for broad circulation across engineering. Focus only on the standard that applies everywhere for this checklist topic, and leave out team-specific security steps and any one person's reviewing h... | document | [
"F-0072",
"F-0073",
"F-0074"
] | [] | [
{
"id": "asrt-1",
"kind": "scope_correct",
"fact_id": "F-0072",
"checker": "semantic",
"criterion": "The handbook note states that production-bound changes require two approvals.",
"weight": 1
},
{
"id": "asrt-2",
"kind": "fact_absent",
"fact_id": "F-0073",
"checker": "se... | {
"ledger_deltas": [
"F-0072",
"F-0073",
"F-0074"
],
"assertions": [
{
"id": "casrt-1",
"kind": "scope_correct",
"fact_id": "F-0072",
"checker": "semantic",
"criterion": "The handbook note states that changes may ship with a single approval during freeze windows.",
... | null | [
"scope_resolution_accuracy"
] | null |
P-0030-02 | P-0030 | A4 | A4-004 | scope_resolution | persona:otto | E-0118 | {
"kind": "org_facing",
"ref": null
} | Draft a company-wide engineering handbook note for the shared pull-request checklist. Keep it concise and directive, suitable for broad circulation across engineering. Focus only on the standard that applies everywhere for this checklist topic, and leave out team-specific security steps and any one person's reviewing h... | document | [
"F-0072",
"F-0073",
"F-0074"
] | [] | [
{
"id": "asrt-1",
"kind": "scope_correct",
"fact_id": "F-0072",
"checker": "semantic",
"criterion": "The handbook note states that production-bound changes require two approvals.",
"weight": 1
},
{
"id": "asrt-2",
"kind": "fact_absent",
"fact_id": "F-0073",
"checker": "se... | {
"ledger_deltas": [
"F-0072",
"F-0073",
"F-0074"
],
"assertions": [
{
"id": "casrt-1",
"kind": "scope_correct",
"fact_id": "F-0072",
"checker": "semantic",
"criterion": "The handbook note states that changes may ship with a single approval during freeze windows.",
... | null | [
"scope_resolution_accuracy"
] | null |
P-0030-03 | P-0030 | A4 | A4-004 | scope_resolution | persona:otto | E-0123 | {
"kind": "org_facing",
"ref": null
} | Draft a company-wide engineering handbook note for the shared pull-request checklist. Keep it concise and directive, suitable for broad circulation across engineering. Focus only on the standard that applies everywhere for this checklist topic, and leave out team-specific security steps and any one person's reviewing h... | document | [
"F-0072",
"F-0073",
"F-0074"
] | [] | [
{
"id": "asrt-1",
"kind": "scope_correct",
"fact_id": "F-0072",
"checker": "semantic",
"criterion": "The handbook note states that production-bound changes require two approvals.",
"weight": 1
},
{
"id": "asrt-2",
"kind": "fact_absent",
"fact_id": "F-0073",
"checker": "se... | {
"ledger_deltas": [
"F-0072",
"F-0073",
"F-0074"
],
"assertions": [
{
"id": "casrt-1",
"kind": "scope_correct",
"fact_id": "F-0072",
"checker": "semantic",
"criterion": "The handbook note states that changes may ship with a single approval during freeze windows.",
... | null | [
"scope_resolution_accuracy"
] | null |
P-0031-01 | P-0031 | A4 | A4-004 | scope_resolution | persona:otto | E-0124 | {
"kind": "team_internal",
"ref": "team:growth"
} | Draft the growth team's PR checklist update for work touching sign-in, session handling, or permissions. Keep it ready for the team channel, use a short checkbox format, and spell out the extra review section that applies only to those cases. Do not turn this into a company-wide standard or a note about one person's pr... | checklist | [
"F-0072",
"F-0073",
"F-0074"
] | [] | [
{
"id": "asrt-1",
"kind": "scope_correct",
"fact_id": "F-0073",
"checker": "semantic",
"criterion": "The checklist says auth-related PRs need security checklist items.",
"weight": 1
},
{
"id": "asrt-3",
"kind": "fact_absent",
"fact_id": "F-0074",
"checker": "semantic",
... | {
"ledger_deltas": [
"F-0072",
"F-0073",
"F-0074"
],
"assertions": [
{
"id": "casrt-1",
"kind": "scope_correct",
"fact_id": "F-0073",
"checker": "semantic",
"criterion": "The checklist says auth-related PRs do not need security checklist items.",
"weight": 1
... | null | [
"scope_resolution_accuracy"
] | null |
P-0031-02 | P-0031 | A4 | A4-004 | scope_resolution | persona:otto | E-0118 | {
"kind": "team_internal",
"ref": "team:growth"
} | Draft the growth team's PR checklist update for work touching sign-in, session handling, or permissions. Keep it ready for the team channel, use a short checkbox format, and spell out the extra review section that applies only to those cases. Do not turn this into a company-wide standard or a note about one person's pr... | checklist | [
"F-0072",
"F-0073",
"F-0074"
] | [] | [
{
"id": "asrt-1",
"kind": "scope_correct",
"fact_id": "F-0073",
"checker": "semantic",
"criterion": "The checklist says auth-related PRs need security checklist items.",
"weight": 1
},
{
"id": "asrt-3",
"kind": "fact_absent",
"fact_id": "F-0074",
"checker": "semantic",
... | {
"ledger_deltas": [
"F-0072",
"F-0073",
"F-0074"
],
"assertions": [
{
"id": "casrt-1",
"kind": "scope_correct",
"fact_id": "F-0073",
"checker": "semantic",
"criterion": "The checklist says auth-related PRs do not need security checklist items.",
"weight": 1
... | null | [
"scope_resolution_accuracy"
] | null |
P-0031-03 | P-0031 | A4 | A4-004 | scope_resolution | persona:otto | E-0123 | {
"kind": "team_internal",
"ref": "team:growth"
} | Draft the growth team's PR checklist update for work touching sign-in, session handling, or permissions. Keep it ready for the team channel, use a short checkbox format, and spell out the extra review section that applies only to those cases. Do not turn this into a company-wide standard or a note about one person's pr... | checklist | [
"F-0072",
"F-0073",
"F-0074"
] | [] | [
{
"id": "asrt-1",
"kind": "scope_correct",
"fact_id": "F-0073",
"checker": "semantic",
"criterion": "The checklist says auth-related PRs need security checklist items.",
"weight": 1
},
{
"id": "asrt-3",
"kind": "fact_absent",
"fact_id": "F-0074",
"checker": "semantic",
... | {
"ledger_deltas": [
"F-0072",
"F-0073",
"F-0074"
],
"assertions": [
{
"id": "casrt-1",
"kind": "scope_correct",
"fact_id": "F-0073",
"checker": "semantic",
"criterion": "The checklist says auth-related PRs do not need security checklist items.",
"weight": 1
... | null | [
"scope_resolution_accuracy"
] | null |
P-0032-01 | P-0032 | A4 | A4-004 | scope_resolution | persona:otto | E-0124 | {
"kind": "personal",
"ref": "persona:otto"
} | Write your own PR triage note for tomorrow. Make it a personal checklist you can use to decide which review requests to open first and when to handle them during the day. Keep it practical, with a simple ordering rule and a time cue that helps you clear a batch quickly without turning it into team policy. | checklist | [
"F-0072",
"F-0073",
"F-0074"
] | [] | [
{
"id": "asrt-1",
"kind": "scope_correct",
"fact_id": "F-0074",
"checker": "semantic",
"criterion": "The note says PRs under 200 lines should be handled before lunch.",
"weight": 1
}
] | {
"ledger_deltas": [
"F-0072",
"F-0073",
"F-0074"
],
"assertions": [
{
"id": "casrt-1",
"kind": "scope_correct",
"fact_id": "F-0074",
"checker": "semantic",
"criterion": "The note says PRs over 200 lines should be handled after lunch.",
"weight": 1
}
]
} | null | [
"scope_resolution_accuracy"
] | null |
P-0032-02 | P-0032 | A4 | A4-004 | scope_resolution | persona:otto | E-0118 | {
"kind": "personal",
"ref": "persona:otto"
} | Write your own PR triage note for tomorrow. Make it a personal checklist you can use to decide which review requests to open first and when to handle them during the day. Keep it practical, with a simple ordering rule and a time cue that helps you clear a batch quickly without turning it into team policy. | checklist | [
"F-0072",
"F-0073",
"F-0074"
] | [] | [
{
"id": "asrt-1",
"kind": "scope_correct",
"fact_id": "F-0074",
"checker": "semantic",
"criterion": "The note says PRs under 200 lines should be handled before lunch.",
"weight": 1
}
] | {
"ledger_deltas": [
"F-0072",
"F-0073",
"F-0074"
],
"assertions": [
{
"id": "casrt-1",
"kind": "scope_correct",
"fact_id": "F-0074",
"checker": "semantic",
"criterion": "The note says PRs over 200 lines should be handled after lunch.",
"weight": 1
}
]
} | null | [
"scope_resolution_accuracy"
] | null |
P-0032-03 | P-0032 | A4 | A4-004 | scope_resolution | persona:otto | E-0123 | {
"kind": "personal",
"ref": "persona:otto"
} | Write your own PR triage note for tomorrow. Make it a personal checklist you can use to decide which review requests to open first and when to handle them during the day. Keep it practical, with a simple ordering rule and a time cue that helps you clear a batch quickly without turning it into team policy. | checklist | [
"F-0072",
"F-0073",
"F-0074"
] | [] | [
{
"id": "asrt-1",
"kind": "scope_correct",
"fact_id": "F-0074",
"checker": "semantic",
"criterion": "The note says PRs under 200 lines should be handled before lunch.",
"weight": 1
}
] | {
"ledger_deltas": [
"F-0072",
"F-0073",
"F-0074"
],
"assertions": [
{
"id": "casrt-1",
"kind": "scope_correct",
"fact_id": "F-0074",
"checker": "semantic",
"criterion": "The note says PRs over 200 lines should be handled after lunch.",
"weight": 1
}
]
} | null | [
"scope_resolution_accuracy"
] | null |
P-0033-01 | P-0033 | A7 | A7-004 | staleness | persona:kofi | E-0065 | {
"kind": "org_facing",
"ref": null
} | Draft a company-wide note for squad leads announcing the current sprint spillover policy for next cycle. Put the operative sentence first, then add one plain-language line on what counts toward it and one line on what a lead should do when a squad is above it. Keep it short enough for the weekly operations update. | document | [
"F-0079"
] | [] | [
{
"id": "asrt-1",
"kind": "fact_applied",
"fact_id": "F-0079",
"checker": "semantic",
"criterion": "The note states that carryover is limited to two unfinished tickets per squad.",
"weight": 1
}
] | {
"ledger_deltas": [
"F-0079"
],
"assertions": [
{
"id": "casrt-1",
"kind": "fact_applied",
"fact_id": "F-0079",
"checker": "semantic",
"criterion": "The note states that squads can carry over unfinished tickets without any cap.",
"weight": 1
},
{
"id": "c... | null | [
"staleness_rate"
] | null |
P-0033-02 | P-0033 | A7 | A7-004 | staleness | persona:kofi | E-0064 | {
"kind": "org_facing",
"ref": null
} | Draft a company-wide note for squad leads announcing the current sprint spillover policy for next cycle. Put the operative sentence first, then add one plain-language line on what counts toward it and one line on what a lead should do when a squad is above it. Keep it short enough for the weekly operations update. | document | [
"F-0079"
] | [] | [
{
"id": "asrt-1",
"kind": "fact_applied",
"fact_id": "F-0079",
"checker": "semantic",
"criterion": "The note states that carryover is limited to two unfinished tickets per squad.",
"weight": 1
}
] | {
"ledger_deltas": [
"F-0079"
],
"assertions": [
{
"id": "casrt-1",
"kind": "fact_applied",
"fact_id": "F-0079",
"checker": "semantic",
"criterion": "The note states that squads can carry over unfinished tickets without any cap.",
"weight": 1
},
{
"id": "c... | null | [
"staleness_rate"
] | null |
P-0033-03 | P-0033 | A7 | A7-004 | staleness | persona:kofi | E-0069 | {
"kind": "org_facing",
"ref": null
} | Draft a company-wide note for squad leads announcing the current sprint spillover policy for next cycle. Put the operative sentence first, then add one plain-language line on what counts toward it and one line on what a lead should do when a squad is above it. Keep it short enough for the weekly operations update. | document | [
"F-0079"
] | [] | [
{
"id": "asrt-1",
"kind": "fact_applied",
"fact_id": "F-0079",
"checker": "semantic",
"criterion": "The note states that carryover is limited to two unfinished tickets per squad.",
"weight": 1
}
] | {
"ledger_deltas": [
"F-0079"
],
"assertions": [
{
"id": "casrt-1",
"kind": "fact_applied",
"fact_id": "F-0079",
"checker": "semantic",
"criterion": "The note states that squads can carry over unfinished tickets without any cap.",
"weight": 1
},
{
"id": "c... | null | [
"staleness_rate"
] | null |
P-0034-01 | P-0034 | A7 | A7-004 | staleness | persona:kofi | E-0116 | {
"kind": "org_facing",
"ref": null
} | Prepare a company-wide FAQ entry for sprint spillover so squad leads stop asking in Slack. Start with the operative sentence, then add a brief example showing when a squad is still within policy. Keep it concise and ready to paste into the handbook without extra framing. | document | [
"F-0080"
] | [
"F-0079"
] | [
{
"id": "asrt-1",
"kind": "fact_applied",
"fact_id": "F-0080",
"checker": "semantic",
"criterion": "The entry states that carryover is limited to four unfinished tickets per squad.",
"weight": 1
},
{
"id": "asrt-2",
"kind": "fact_absent",
"fact_id": "F-0079",
"checker": "... | {
"ledger_deltas": [
"F-0080"
],
"assertions": [
{
"id": "casrt-1",
"kind": "fact_applied",
"fact_id": "F-0080",
"checker": "semantic",
"criterion": "The entry states that carryover is limited to one unfinished ticket per squad.",
"weight": 1
},
{
"id": "c... | null | [
"staleness_rate"
] | null |
End of preview. Expand in Data Studio
memory-bench v1.0.0, public release
A screened benchmark for organizational memory in agent harnesses: does a memory system keep a rule that was stated once, drop a fact that was superseded, and pick the right one when tiers conflict?
371 valid paired probe instances across 3 simulated organizations, drawn from 486 probes over 612 events. Scored as pair credit: an instance counts only if the base task and its counterfactual twin both pass, so anything answerable from priors earns nothing.
Layout
data/org-0000N/ events.jsonl the stream, one event per line
probes.jsonl work tasks + scoring assertions
g3-report.json the frozen valid set
org.json personas/teams/event witness index
(ground-truth ledger REDACTED)
data/org-0000N-twin/ events.jsonl counterfactual stream
org.json redacted, as above
croissant.json dataset metadata (Croissant 1.0)
rai.json responsible-AI metadata
CHECKSUMS.txt sha256 of every shipped file
MANIFEST.json what shipped, what was withheld, and why
MAINTENANCE.md versioning + the re-anchoring procedure
LICENSE-DATA CC BY 4.0
What is withheld, and why
The ground-truth fact ledger (746 facts across the public seeds) stays private: it records which facts are probed and which are planted distractors, so publishing it would let a system learn the generator's planting patterns rather than remember the organization. The generator and the two unscreened holdout seeds are withheld for the same reason. They are the answer if the public seeds are ever contaminated.
The probe assertions ARE published. Scoring is impossible without them, and an open benchmark that hides its criteria cannot be checked. This makes the set open-book by construction: a system tuned against these criteria will score well here and generalize nowhere, and the canary strings embedded in every stream are how you detect one that trained on this data.
A warning about the anchors
Every instance's validity was established under one pinned worker model, which
its provider has since deprecated. Probe validity is task-model-relative: we
measured 37/54 versus 17/54 cluster survival across two workers under
identical rules. The valid set shipped here is valid relative to that
worker, not in the abstract. Running a different worker without re-screening
produces numbers that do not mean what they appear to mean. MAINTENANCE.md
gives the procedure.
Papers and code
- Dataset and validity study: doi:10.5281/zenodo.22838320
- Construction methodology: doi:10.5281/zenodo.22838602
- Harness, screening and scoring, and the evidence behind every number: github.com/notmehul/memory-bench
- Development record: github.com/notmehul/memory-bench-history
Citation
Srivastava, M. (2026). memory-bench: A Screened Benchmark Dataset and Validity Study for Organizational Memory in Agent Harnesses. Zenodo. https://doi.org/10.5281/zenodo.22838320
License
Data: CC BY 4.0 (LICENSE-DATA). Code in the repository: MIT.
- Downloads last month
- 31