About · Stewardship

Keep the evidence inspectable as the work evolves

Software, domain knowledge and institutional decisions change on different schedules. Stewardship means making those changes understandable and keeping responsibility for review visible

Current functions

Cartographer is the specialist experience for maintaining domain knowledge. It separates source and project work from human review and controlled publication. The public BCI landscape uses published catalogue material; a record’s presence is not a certification of its claims or a complete account of the field

The BCI application presents context, sources, assumptions and missing information for inspection. The companion explains the method and provides guidance. Those functions are connected, but they should not be mistaken for an independent regulator, a scientific validation service or an institutional decision authority

Different records, different responsibilities

Record or outputWhat to understand
Published caseA source-based catalogue record. Review its sources, date, scope and gaps. It may be a useful lead without being suitable for a particular person or setting.
Exploration draftA browser-local record of a question, alternatives and assumptions. It is not a server-synced project assessment.
Saved assessmentAn authenticated record with its own access rules and supplied inputs. It can be revised; it is not an immutable institutional ledger.
PassportAn assessment output for carrying reasoning into discussion. The people using it remain responsible for the decision and subsequent actions.
Landscape or trend viewA view of a defined published population. Coverage, filters and missing dates affect what a comparison can support.

A change to a source, a model or an app screen may affect different outputs. An updated interface alone does not establish that an old assessment has been re-reviewed

Questions and corrections

Send questions about Compass or a possible correction to info@gesda.global. Include the page or public case link, the statement concerned and, where possible, a source that helps explain the correction

For a software issue, describe the screen, the steps that led to it and what you expected. Keep private assessment information, personal health details and account credentials out of an initial email

A submitted correction is a request for review. It does not change a published case, saved assessment or previous export automatically. Check the date and sources of the version you use, and retain the context of any decision already made

What readers can check now

Look for a clear content type, relevant sources, the date and scope of an example, and an explanation of missing evidence. When an assessment supports a discussion, ask which assumptions matter and who will follow up on the open questions

For a published essay, retain its original date and distinguish its example from a current project record. For a guide, check the edition and whether its screenshots match the current interface

Guide edition · 2 October 2026

Find a guide for your role