Operating layer

AI system inside the page

Example for Mercury: thematic AI widget, server-side run, hard analysis, no-go criteria, and human handoff working as one UX pattern.

View consoleFloating AI widget bottom-right

Audience adaptation

One logic, different explanation levels

The system does not speak to everyone the same way. It changes depth, tone, and output shape for the person in front of us: client, visitor, partner, or counterparty.

Required methodReverse reconstruction → Chronological inversion → Bidirectional analysis → The present as an archive of the future

تحتاج كل بطاقة إلى معاينة بصرية: صورة موجودة، مصدر معالج جمالياً، أو إعادة بناء علمية.

Client

Simple and confident

Explain value without overload: what it is, why it matters, what risks are covered, and the next step.

"What do I get and why can I trust it?"

Interested visitor

Orient and engage

Give an overview, show scale, reduce complexity anxiety, and offer a safe exploration path.

"Where do I start if I am not a specialist?"

Partner

Business structure

Show responsibilities, cooperation scenarios, integration points, data requirements, and success criteria.

"How do we integrate this into our product or process?"

Counterparty

Firm but fair

Separate facts from promises, reveal incentives, hidden asymmetries, entry conditions, and stop reasons.

"What must be true for us to move forward reasonably?"

Basic levelNo jargon: meaning, value, limits, and the next safe step.

Business levelRisks, alternatives, actions, ownership zones, and decision criteria.

Expert levelClaims ledger, sources, counterfactuals, no-go triggers, and verification status.

Reverse reconstructionmoving from the present trace back to the impact event

Chronological inversionreading the object from future state back through earlier layers

Bidirectional analysischecking past-to-present and present-to-past interpretations

The present as an archive of the futuretreating today's profile as evidence for future analysis

Fast scenario library

Explain this craterCompare objectsResearch planMedia brief

The browser stores no model/API keys. The request goes through a BFF where providers, logs, and evals can be added.

Claims ledger

Mercury is ready for editorial reviewpartly verified

page, catalog, and profiles pass build and e2e

AI output can be used as publishable copynot verified

editorial review and sources are required

Visuals and clips can be expanded in batchesprobable

Earth SVG/MP4 generator and content schema already exist

No-go filter

A critical fact is not backed by a primary source
The AI slice relies on untrusted or stale context
A visual lacks clear rights or source caption
A second pass materially disagrees

Example verdict

GO ONLY IF: the profile can be expanded only after sources, coordinates, visual rights, and editorial status are verified.

This is the same standard I apply in our work: action first, then weak-point analysis, then a durable conclusion.