Discovers reporting events automatically.
A candidate schedule remains unverified until a credible source supports its date and precision.
Company · Why Corteqx
A reporting event is a connected evidence set: written release, reported figures, guidance, presentation, webcast or call, transcript, Q&A, and every meaningful correction. Corteqx keeps that set inside one continuous research thread.
Written release
Reported figures
Guidance
Presentation
Webcast or call
Transcript
Q&A
Corrections and revisions
The fragmented quarter
Dates are checked separately from reports. Official files appear across issuer pages and notices. Presentation evidence and Q&A arrive later. Transcripts and corrections can change the record again. Teams are left to reconstruct the chronology by hand.
Why Corteqx exists
Corteqx exists to keep preparation, publication, analysis, presentation evidence, Q&A, and revision inside one accountable operating record. Autonomy matters because the work can begin before release. Trust matters because every state must remain inspectable afterward.
Institutional principles
The system is governed by a small set of operating commitments. Each statement is useful only because a control follows it.
ControlKeep the expected event, available schedule precision, source locations, and comparison context ready before the release arrives.
ControlDiscovery sources may locate an event. Issuer material and official notices remain the primary evidence for assertions.
ControlExact time, bounded window, and date-only schedules remain different states. Precision is never invented for visual neatness.
ControlConflicting timing, unavailable material, stale projections, and incomplete coverage remain readable conditions.
ControlA reviewable finding keeps a route to its source identity, document role, and supporting span when that span is available.
ControlA replacement or correction advances the current state without silently presenting the earlier evidence as current.
ControlNo transcript, expectation, excerpt, or Q&A is more truthful than an unattributable substitute.
ControlSource conflicts, missing prerequisites, unsafe destinations, and temporal ambiguity remain review conditions—not completed work.
What autonomy means
Autonomy is not a claim that the system is unconstrained. It is an observable sequence in which every action carries a condition and every material state leaves a record.
Detect reporting events, source changes, publication, and newly available evidence.
Check timing, source identity, authority, availability, and replacement state.
Acquire material, structure evidence, compare the quarter, and prepare a report when prerequisites allow.
Preserve source, time, availability, revision, evidence coverage, uncertainty, and escalation state.
Return pathSource identity · time · availability · revision · uncertainty
Discovers reporting events automatically.
A candidate schedule remains unverified until a credible source supports its date and precision.
Acquires available material automatically.
Only configured safe official locations cross into the public evidence record; missing material remains missing.
Structures and compares evidence automatically.
Unavailable prerequisites, conflicting sources, and incomplete evidence coverage remain explicit blockers.
Prepares and updates reports automatically.
Sources, revisions, uncertainty, and prior evidence are not silently overwritten by the newest state.
Evidence, revision, accountability
A source-linked report is more than a finished document. It is a set of inspectable relationships between the reporting event, the current source, the cited span, the publication and acquisition record, the revision, and what remains unresolved.
A reviewable finding remains connected to the official material and the conditions used to interpret it.[1]
Unavailable excerpts, missing live evidence, and protected analysis stay explicitly outside the public artifact.
Origin and scope
Corteqx is focused on Swedish listed-company reporting. The product model begins with the reporting event—preparation, publication, presentation, Q&A, and review—because that sequence gives source identity, timing, evidence, and revision one concrete operating context.
Identity in use
The same hierarchy must work in public narrative, operational product, report, evidence, revision, and mobile use. The identity is not a campaign layer placed over the system; it is the system’s accountability made legible.
Selected reporting period
Expected event · Time precision retained
Every reviewable statement keeps a return path to evidence.
Source span · Available when attributable
Public metadata and protected analysis remain separate.
Revision and source state stay readable without hover.
Prepared before release · Accountable after publication
Open the current public report, inspect the method that governs it, or request access to the protected reporting workspace.