Capability
Connect a public report to inspectable source evidence.
Control / limit
Expose only approved source metadata and safe external destinations.
01
The Corteqx platform
One reporting event.Every layer accountable.
Corteqx organizes quarterly-report research around a persistent event object, with explicit layers for sources, verification, acquisition, analysis, delivery and revision.
Persistent objectReporting eventIssuer · period · event time
- 01Reporting event
- 02Sources
- 03Verification
- 04Acquisition
- 05Analysis
- 06Report
- 07Revision / provenance
Explicit state changes connect the layers.
02
Layered system architecture
The object stays stable.Its evidence can change.
The architecture separates identity, evidence and publication state. Each layer has a distinct job, and no layer silently stands in for another.
- 01
Reporting-event object
A stable identity holds the issuer, reporting period, event timing and availability state together as evidence changes around it.
- 02
Source layer
Official releases, presentations, exchange notices, calls, webcasts and transcripts remain named source types. Availability can differ by event.
- 03
Verification layer
Source identity, destination, timing and replacement state are checked before a source is treated as current evidence.
- 04
Acquisition layer
An available source is retained with its type, location and acquisition context. Missing or inaccessible material remains an explicit gap.
- 05
Analysis layer
Evidence can be compared and organized inside the protected research workspace while uncertainty and unsupported conclusions remain visible.
- 06
Report layer
A publication state, source-linked citations and evidence coverage describe what is available without exposing protected intermediate work.
- 07
Revision and provenance layer
Current and superseded source states remain distinguishable so a correction can update the report without erasing its lineage.
03
Public and protected
A deliberate boundary,not an accidental leak.
Public pages use a constrained projection of event, source, availability and revision metadata. Research work remains behind the product boundary.
- Analytical working context
- Intermediate transformations
- Unsupported or unresolved interpretations
Controlled boundaryAllowlistOnly reviewed, public-safe fields cross.
- Event identity and timing
- Approved source links and availability
- Report state, revision and provenance metadata
Capability
Show whether evidence or a report is available.
Control / limit
Represent missing, conditional and unavailable states without filling the gap with inference.
Capability
Publish a current revision while sources change.
Control / limit
Keep replacement and provenance state explicit instead of silently overwriting history.
04
Evidence discipline
State what is known.Preserve what is not.
The system is designed to make source state and uncertainty inspectable throughout the reporting event.
Source availabilityExplicit
A source that has not been acquired is shown as a gap, not treated as evidence.
Availability varies by issuer, event and source type.
VerificationSeparate
Finding a candidate destination does not make it an official, current source.
Identity, timing and replacement state remain part of the source relationship.
RevisionTraceable
A corrected source can change the current report without making the earlier state disappear.
The revision and provenance layer records continuity across the event.
See the system in operation
Follow one eventfrom discovery to revision.
The workflow shows how the same reporting-event identity moves through each operational stage, including conditional live evidence and controlled delivery.