signed outSign in

Medical oncologist in Greece

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 Greece

sustained interest in KRAS G12C in lung adenocarcinoma

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-W29, still asking in 2026-W38. Weeks, never timestamps: the ISO week is the finest granularity the signal layer keeps (OQ-43).

not contacted

Request contactA name is shared only if this person accepts, and only with the account that asked.

No count on this card

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.

Request contact

SampleNothing below is a measurement.

Drawn. There is no contact-request route: DATA-02 puts the consent record inside the signal layer, so no Skepsis Insights store may hold one, and nothing here writes one. The wording shown is the text a consent record would store verbatim.

Check it: POST /api/signals/consent on this deployment answers 409 gated, naming XFER-01: where a signal-layer consent record lives has not been chosen. Press Send below and this screen makes that call and prints what comes back.

Requesting company

Wording shown to the clinician

Kalypso Therapeutics would like to contact you about your interest in KRAS G12C in lung adenocarcinoma, 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.

There is no message box on this form and no field anybody can type into. Everything a clinician would be shown is fixed above, because the consent record stores the wording verbatim (OQ-42), and a sentence the record does not store is a promise nobody can audit. The wording states what declining costs, which is nothing, because XFER-02 makes withdrawal one action exactly as the grant was.

Pressing this sends nothing to anybody. It asks this deployment what would happen, and prints the answer.

Absent by decision

Anything the clinician asked, typed or answered OQ-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 initials OQ-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 export NP-02, OQ-46It appears on the revealed profile after an acceptance, and nowhere before it.
A conflict-of-interest field NP-09No field, no flag and no note, on this screen or on any type in this product.
Industry payments, claims and prescribing data OQ-28Not fetched, not stored and not shown. Absent from the types, not switched off.
A second request after a decline OQ-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.

Medical oncologist in Greece

SampleNothing below is a measurement.

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 Greece

sustained interest in KRAS G12C in lung adenocarcinoma

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-W29, still asking in 2026-W38. Weeks, never timestamps: the ISO week is the finest granularity the signal layer keeps (OQ-43).

not contacted

Request contactA name is shared only if this person accepts, and only with the account that asked.

No count on this card

Request contact

SampleNothing below is a measurement.

Requesting company

Wording shown to the clinician

Kalypso Therapeutics would like to contact you about your interest in KRAS G12C in lung adenocarcinoma, 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.

Pressing this sends nothing to anybody. It asks this deployment what would happen, and prints the answer.

Absent by decision

Anything the clinician asked, typed or answered OQ-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 initials OQ-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 export NP-02, OQ-46It appears on the revealed profile after an acceptance, and nowhere before it.
A conflict-of-interest field NP-09No field, no flag and no note, on this screen or on any type in this product.
Industry payments, claims and prescribing data OQ-28Not fetched, not stored and not shown. Absent from the types, not switched off.
A second request after a decline OQ-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.