Four cards, four states, all of them on this deployment at once. Nothing on this screen moves a card from one state to the next, because nothing in this build can: there is no contact-request route, and the consent record a request would write sits on the other side of the wall (DATA-02).
SampleNothing below is a measurement.
Drawn, not measured. ADR 0002 puts aggregation and the release rules in a signal service that neither product has written, so this repository has no signal-event table, no aggregated-signal table and no route that reads one. OncoSkepsis has no deployment either: its first tumour boards run November to December 2026.
Check it: POST /api/signals/ingest on this deployment answers with that refusal, and GET /api/signals/boundary publishes the admissible-field allow-list, which is empty.
medical oncologist in Ireland
sustained interest in HER2-low breast cancer
sustained topic signal
NP-15 reads this as the top 1.4 percent of topic scores in the disease area, and that reading stands until the OQ-27 validation study replaces it.
Asking since 2026-W28, still asking in 2026-W38. Weeks, never timestamps: the ISO week is the finest granularity the signal layer keeps (OQ-43).
There is no weekly figure here and no total, and the card type has no field that could hold one. A count beside one person is that person’s own activity, and no rounding makes a count of one safe to publish (X-12, OQ-14). Counts belong to the topic, where at least 8 different people stand behind every figure that is shown at all. They are on the signal layer overview, beside the weeks the rules withheld.
The consent record
Outcome
accepted
Requested
2026-W36
Decided
2026-W37
Company named in the request
Kalypso Therapeutics
Wording shown, verbatim
Kalypso Therapeutics would like to contact you about your interest in HER2-low breast cancer, to ask whether you would join an advisory board. Accepting shares your name and your work email address with Kalypso Therapeutics and with nobody else, and it shares nothing you have asked or answered in OncoSkepsis. Declining changes nothing about your OncoSkepsis access or your tumour boards. You can withdraw an acceptance later in one action, in the place you gave it.
The record keeps the wording as it was shown rather than a summary of it (OQ-42). A record holding a paraphrase would be a record of what the product meant to say, which is not the thing a clinician agreed to. Both dates are weeks, because a consent record is kept at the granularity the signal layer keeps (OQ-43).
The profile this acceptance opened
SampleNothing below is a measurement.
Drawn, and this person does not exist. There is no GET /api/experts/{id} route in this API, and expert_profile_items is a table with no writer anywhere in the repository, so there is nothing for a profile to be read from. It is on this screen because this clinician accepted one request from Kalypso Therapeutics in 2026-W37, and it is scoped to that account.
Check it: The API's OpenAPI document at /docs lists POST /api/experts/search and no expert profile path at all.
This deployment has no account configured, so the scope cannot be checked against one.
In a deployment with a signal layer, this panel opens for the account that asked and for no other. Here it is a fixture, and the sentence above it is the whole of the claim.
Name
Dr Fionnuala Sheridan
Profession
medical oncologist
Country
Ireland
Shared with
Kalypso Therapeutics, from 2026-W37
Scope
Shown to Kalypso Therapeutics and to nobody else, because this clinician accepted that one request. Another customer asking about the same topic sees the anonymous card.
Accepted wording, verbatim
Kalypso Therapeutics would like to contact you about your interest in HER2-low breast cancer, to ask whether you would join an advisory board. Accepting shares your name and your work email address with Kalypso Therapeutics and with nobody else, and it shares nothing you have asked or answered in OncoSkepsis. Declining changes nothing about your OncoSkepsis access or your tumour boards. You can withdraw an acceptance later in one action, in the place you gave it.
Tumour boards
Breast multidisciplinary meeting, Dublin
Selected publications
Antibody-drug conjugate sequencing after endocrine therapy in HER2-low disease, ESMO Open, 2025
Concordance of HER2 immunohistochemistry scoring across four reporting centres, Histopathology, 2024
Profile completion
70% A readout, not a rank. OQ-18 shows it to the customer and to the expert, and NP-06 forbids any scoring or sorting rule from using it. Nothing here sorts by it.
Tumour-board membership appears here and nowhere earlier: not on a card, not a list column, not a filter and not an export (NP-02, OQ-46). It exists once a person has accepted, and not before. The publications carry no DOI and no PMID, because a drawn identifier resolves to a real and unrelated paper (OQ-44).
Absent by decision
Anything the clinician asked, typed or answeredOQ-05, DATA-02No question text and no quoted phrase crosses the wall, before an acceptance or after one. A coded topic crosses. The words do not.
An employer, an institution, an avatar or initialsOQ-05, FD-02The card carries profession, country and topic, and its type has no field for any of these, so a screen cannot render one by reaching for it.
Tumour-board membership on a card, a column, a filter or an exportNP-02, OQ-46It appears on the revealed profile after an acceptance, and nowhere before it.
A conflict-of-interest fieldNP-09No field, no flag and no note, on this screen or on any type in this product.
Industry payments, claims and prescribing dataOQ-28Not fetched, not stored and not shown. Absent from the types, not switched off.
A second request after a declineOQ-42The decision is kept and this screen offers no retry, so asking again would have to be something a person does on the record.
Each decision above is in the requirement ledger. The wall itself is not a diagram: hand it a payload at the boundary screener and it names the field, the rule and the requirement.