DDubaist

Dubaist · Trust layer

Data methodology

How Dubaist turns primary documents into publishable facts without hiding provenance or uncertainty.

Public data roadmap

What is available now — and what still needs verification

This is the current public data contract across 143 company profiles. Static registry coverage is counted exactly. Financial facts and company updates remain live, database-backed layers and are never inferred from a static profile.

Available in the public registry143 of 143

Official identity source

Exact source links are shown on each company profile.Inspect source directory
Available in the public registry143 of 143

Business-model context

Sector and business-model labels select the appropriate analytical lens.Open company directory
Available for part of the directory138 of 143

Reporting-period context

A registry period is context, not a published financial value.Open company directory
Available for part of the directory55 of 143

Review ready; verified figures appear after approval

Research completion does not automatically publish facts or conclusions.Read coverage policy
Live evidence check requiredLive evidence check required

Verified public financial facts

Each company is checked for a source trail, current evidence and editorial approval before figures appear.Open company directory
Live evidence check requiredLive evidence check required

Published company updates

Only human-published, exact-security events can enter the public chronology.Open updates hub

Published company reviews are automatically checked for percentage arithmetic, reserve-attribution completeness and language consistency before release.

No source — no fact. Missing, stale, conflicting or rights-blocked data remains visibly unavailable rather than being replaced with estimates.

Official-source integration

ADX MCP access is technically verified

Dubaist has verified authenticated access to the official ADX MCP service. Five live endpoint families are visible for equities, indices, derivatives, news and disclosures, and XBRL.

Technical access
Verified
Public display rights
Under licence review
Automated publication
Off

No ADX market value is published from this connection until the accepted product licence confirms display, storage, attribution and redistribution rights. Missing, stale or conflicting data remains closed, and publication requires editorial review.

Where each ADX data family will appear

Official data familyDubaist destinationCurrent state
Listed-company profiles and statusCompany identity and evidence pagesPrepared; public projection not activated
News and disclosuresUpdates, issuer chronology and event pagesPrepared; public projection not activated
XBRL filingsVerified financial-fact and source-document layersPrepared; public projection not activated
IndicesADX market and methodology pagesPrepared; public projection not activated
Equity and derivative market dataMarket views only under a separate display licencePrepared; public projection not activated

Evidence before values

A numerical value enters the public layer only with a company, period, currency, unit, fact class, consolidation scope, source document, locator and verification date. Missing values remain unknown rather than becoming zero.

Fact classes stay separate

Reported facts, normalized facts and calculations retain separate labels. Estimates, analyst inference and assumptions do not silently replace issuer disclosures. Restatements and source conflicts remain explicit relationships.

Rights and freshness

Collection follows robots.txt, bounded request frequency, an identified contact User-Agent, public no-login sources and no full mirroring. Current prices remain outside the licensed product perimeter.

Automatic publication and exceptions

A fact publishes automatically only when all applicable machine gates pass. Failed arithmetic, a source conflict, a restated or reclassified prior period, or a missing document/page locator remains private in the exception queue. Two footnoted scopes may publish only as an adjacent pair with an explicit label for each perimeter.