Internal · Reasoning Diff · Not part of the product experience

Demand shock

Why Aegis reached a different conclusion than the benchmark. This page collects evidence from one failed scenario. It does not create reasoning rules — those come only after the same failure appears across many scenarios.

Back to labDisagreementA sudden collapse in top-of-funnel demand that persists.
1

Belief comparison

Expected belief

Demand collapsed at the top of the funnel with spend unchanged, and revenue is now following the base down two periods later. This is external, not executional.

Confidence · high

Aegis belief

The business is defined by the relationship between Monthly Revenue · Customers, not by any one line: Monthly Revenue and Customers are moving as one, which points to a single underlying cause rather than two separate events.

Confidence · moderate

Aegis did not reach the expected dynamic — the conclusion rests on a different relationship.

2

Data sensing

Did Aegis look at the wrong evidence?

Benchmark prioritized

  • Trial Signups

    deteriorating · importance 78 · seen in 4 periods · emerging-pattern

  • Monthly Revenue

    deteriorating · importance 80 · seen in 4 periods · emerging-pattern

  • Customers

    deteriorating · importance 67 · seen in 4 periods · emerging-pattern

Aegis prioritized

  • Monthly Revenue

    deteriorating · importance 80 · seen in 4 periods · emerging-pattern

  • Trial Signups

    deteriorating · importance 78 · seen in 4 periods · emerging-pattern

  • Customers

    deteriorating · importance 67 · seen in 4 periods · emerging-pattern

  • Marketing Spend

    flat · importance 57 · seen in 4 periods · emerging-pattern

Ignored or underweighted

Nothing expected was missed.

Carried in addition: Marketing Spend.

No — every expected metric was read, but the conclusion also carried metrics the benchmark treats as secondary.

3

Mechanism misalignment

Why did Aegis reach a different conclusion?

Expected business explanation

Demand collapsed at the top of the funnel with spend unchanged, and revenue is now following the base down two periods later. This is external, not executional.

Aegis business explanation

Monthly Revenue moved −15.3% ($352K → $298K) while customers moved −13.1% (2,510 → 2,180). Monthly Revenue and Customers are moving as one, which points to a single underlying cause rather than two separate events.

Where it diverged

Aegis had the right evidence in hand but did not connect it: funnel-quality, spend-up-acquisition-quality was not surfaced, so the conclusion stopped at description rather than dynamic.

4

Decision impact

Expected recommendation

act-now

Aegis recommendation

act-now

The reasoning difference did not change the business decision — both readings resolve to "act-now". Only the explanation behind it differs, which affects trust in the review rather than the action taken.

5

Engine lesson

Failure type

Unformed relationship

Observed pattern

Marketing Spend vs Trial Signups

Category

The right metrics were read, but the relationship between them was not formed.

Root cause

Aegis held every metric the conclusion needed but stopped at description. funnel-quality, spend-up-acquisition-quality required the metrics to be read against each other, and each was explained on its own instead.

Supporting evidence

  • Marketing Spend

    flat · importance 57 · seen in 4 periods · emerging-pattern

  • Trial Signups

    deteriorating · importance 78 · seen in 4 periods · emerging-pattern

  • Monthly Revenue

    deteriorating · importance 80 · seen in 4 periods · emerging-pattern

  • Customers

    deteriorating · importance 67 · seen in 4 periods · emerging-pattern

Business impact

The recommendation survived — both readings resolve to "act-now" — but it was reached for the wrong reason, which costs trust in the review rather than the action.

Candidate principle

None. A single scenario is not evidence. This observation is filed to Judgment Memory and a principle is proposed only once the same behaviour recurs across scenarios.

Status · Evidence CollectionSee accumulated evidence for this pattern

Suggested improvement

Capture the exact readings for trial_signups, monthly_revenue, customers and the threshold each pattern rule needed. If the same near-miss recurs, the gap is in the rule's tolerance, not in the data.

Notes

  • Scenario family: demand-shock. Posture read as deteriorating; benchmark expected deteriorating.
  • Evidence overlap 100% · belief 0% · decision 100% · confidence 50%.
  • Evidence only. No reasoning rule should be changed from this single scenario.