Skip to content
ProofPack docs
  • FDA AI-DSF lifecycle guidance: DRAFT (Jan 2025) — not for implementation
  • PCCP guidance: final (Dec 2024, updated Aug 2025)
  • FDA Statistical Guidance on diagnostic tests: final (2007)
  • Guidance map v1

Support

The channel

Section titled “The channel”

Email support@globalphoenix.co.uk. It reaches a person at Global Phoenix Solutions Ltd. There is no live chat, and the “Ask the docs” box at the foot of every docs page does not send anything yet — a docs-grounded answerer is a later build day, and until it is switched on the box says so.

What we answer, and how fast

Section titled “What we answer, and how fast”

A licence includes support on computational-correctness questions — is this number right, why does this interval look like that, why did this gate fire — answered within one business day. That is the commitment, and it is the whole of it: we will tell you what the engine computed and why, and we will fix a wrong number as a severity-one defect.

We do not answer, on any channel, the questions ProofPack is out of scope for — which criterion you should set, what margin to choose, whether a submission will succeed. If you ask, the reply says so and points here. Trust and procurement conversations (DPA, security questionnaire, terms) are answered by a person too, from the trust page’s documents.

What to send

Section titled “What to send”
  • The engine version (proofpack --version) and the platform.
  • The HALT line and its detail line, or the --json-log object — these carry aggregates only and are safe to paste.
  • The output of proofpack map: header → role → confidence. That is the one artefact most first-run problems are solved from.

What never to send

Section titled “What never to send”

No test-set rows, no model outputs, no patient data, no criteria.yaml free text you would not want in our mailbox. A support message is the one route on the egress table that your own people control rather than our code; keep it to aggregates. If a message arrives with data in it, the data is not opened by any model and you are asked to resend without it.

Office hours

Section titled “Office hours”

Fortnightly office hours are part of every paid licence: a booked call with the person who wrote the engine, for computational-correctness questions and for walking a first run. Ask for a slot by replying to any ProofPack email; a booking link is not in the licence email today. Office hours are not a design-review service and do not change what the engine computes.

The “Ask the docs” box

Section titled “The “Ask the docs” box”

The box below every docs page is the front end of the docs-grounded answerer described in the support design: retrieval over these pages, a trap classifier that escalates regulatory-opinion, wrong-number, commercial, study-design and data-bearing questions to a person, and an answer that cites the section it came from and carries a fixed footer. Today it is markup only; its four answer states can be previewed by fragment — answered, acknowledged, refused, insufficient. The four state texts as built carry no digit; the site’s build test greps them on every docs page for a decimal, a percentage, a bracketed interval or two or more digits. The Ask button is disabled and there is no form behind the box until the answerer exists.