A bounded public walkthrough

From signal to signed decision.

Follow one illustrative catch through the four states that make AEGIS inspectable: extraction, verification, Catch Card formation, and the human gate.

ILLUSTRATIVE ONLY
No live tenant data, provider calls, database writes, external sends, or durable Memoria writes are used here.
The four states

Inspect each transition.

1. Event extraction

AEGIS reads a supported source under a scoped grant and isolates a concrete operational event. It does not infer an approval from the event alone.

SourceIllustrative CRM activity
EventQualified deal has no confirmed next step
ObservedLast activity was 8 days ago
ScopeRead-only sample record

2. Evidence verification

The candidate is checked against source context and measurement boundaries. AEGIS keeps evidence separate from the later decision.

Evidence ACRM stage: Qualified
Evidence BOwner next-step field: empty
FreshnessLast activity: 8 days ago
Confidence boundaryNeeds human review; not a forecast

3. Catch Card

The verified candidate becomes a reviewable Catch Card. It proposes attention, never an autonomous send or durable memory write.

CATCH · PENDING HUMAN REVIEW

Qualified deal has no next step

Review the owner and confirm the next customer-facing step before the deal ages further.

4. Human gate

The operator decides whether the proposed catch should become an accepted outcome. This browser-only button demonstrates the state transition without writing anywhere.

Awaiting human signature
Boundary

What the anatomy does not claim.

Not universal detection

This is one supported, illustrative source path, not proof that every business signal can be detected.

Not autonomous execution

The lifecycle prepares a human decision. It does not send messages, mutate providers, or promote memory by itself.

Not a pilot report

Measured customer outcomes require a connected tenant, signed audit trail, and separately generated proof report.