AI analyst readiness
Issues & evidence Trace findings back to the exact source and revision.
Demo data No real customer. Synthetic evaluation.
Assessments Questions & results Issues & evidence Owner review Context package Readiness report
Prioritized findings Severity follows case importance and source conflicts. Failure causes are hypotheses.
Refund timing · Finance · Monthly close high impact
Conflicting source evidence · Business context hypothesis · reject
Exact source evidence
Source identifier old-close-faq
Revision archive
Location sample/old-close-faq.md · line 3
Observed 2026-11-03T10:00:00.000Z
Coverage complete
Input SHA-256 aab8aa499a279d483b35d75d6f91beafb2afa8920978dce123d12eebbc79201b Assign refunds to the month of the original charge.
Conflicting excerpt · finance-refunds
Source identifier finance-refunds
Revision 1
Location sample/finance-refunds.md · line 3
Observed 2026-11-03T10:00:00.000Z
Coverage complete
Input SHA-256 f6ff79cf69d4c34b289a4a823d874e9dd5ede21df7713194f45057e1ddc7c50c Assign refunds to the UTC calendar month when the refund settles.
Current approved statement Assign refunds to the UTC calendar month when the refund settles.
What is an active customer? high impact
Incorrect · Business context hypothesis · needs review
Observed and expected
Expected Ask whether the user means Product engagement or Finance monthly close.
Observed An active customer is an organization with a settled payment this month.
Origin Authored synthetic baseline response fixture
Confidence high
Which month gets a refund for an October charge that settled in November? high impact
Confidently incorrect · Business context hypothesis · needs review
Observed and expected
Expected November in UTC, based on settlement date.
Observed Definitely October. Refunds always use the original charge month.
Origin Authored synthetic baseline response fixture
Confidence high
Source snapshots old-close-faq @ archive · complete
Location sample/old-close-faq.md
Observed 2026-11-03T10:00:00.000Z
Scope Finance · Monthly close
Coverage complete
Structured claims 1
SHA-256 aab8aa499a279d483b35d75d6f91beafb2afa8920978dce123d12eebbc79201b # Finance · Monthly close
Assign refunds to the month of the original charge.
finance-refunds @ 1 · complete
Location sample/finance-refunds.md
Observed 2026-11-03T10:00:00.000Z
Scope Finance · Monthly close
Coverage complete
Structured claims 1
SHA-256 f6ff79cf69d4c34b289a4a823d874e9dd5ede21df7713194f45057e1ddc7c50c # Finance · Monthly close
Assign refunds to the UTC calendar month when the refund settles.
finance-active @ 1 · complete
Location sample/finance-active.md
Observed 2026-11-03T10:00:00.000Z
Scope Finance · Monthly close
Coverage complete
Structured claims 1
SHA-256 12176d3b9c070511176d9b4b648f344e4de73c0ab09794324dc468c9354eb74e # Finance · Monthly close
Count organizations with a settled subscription payment during the UTC calendar month. Exclude refunded payments.
product-active @ 1 · complete
Location sample/product-active.md
Observed 2026-11-03T10:00:00.000Z
Scope Product · Engagement
Coverage complete
Structured claims 1
SHA-256 2b2d3091852fa53dd433664fbc6460fe2f235b81175b03a880c47fd794539116 # Product · Engagement
Count organizations with at least one qualifying workspace event in the prior rolling 30 days. Exclude internal and sandbox workspaces.