⌘K

Laboratory EngineeringGuide

Integration testing & acceptance evidence

Separate source, loopback transport, persisted disposable tests and hosted laboratory qualification.

On this page

October 25 selected verification

Owner-supplied independent selected release-critical CI succeeded: 1,632/1,632 tests in 96 files, zero failures/skips, locked TypeScript and production build passing. Prompt4 synthetic acceptance is 29/29; separate real disposable PostgreSQL/PostgREST two-buyer acceptance is 7/7 and integrated acceptance is 24/24. This is selected isolated release-critical verification, not the entire historical broad suite.

The ULC-CAT-01 U00–U19 source closeout supplements the CA-READY 72-slice source record. Existing six-step onboarding and Step 5/6 remain unchanged. This documentation is source delivery until hosting propagation is independently observed.

Four evidence tiers

  • SOURCE — typed contracts, defensive projections and docs/tests exist. No installed or clinical authority follows.
  • ISOLATED loopback — real independent TCP/HTTP/SSH peers validate bounded transport/configuration behavior with synthetic data.
  • DISPOSABLE persisted — actual handlers/workers and disposable PostgreSQL/PostgREST persist scoped synthetic lifecycle and released-result read-back. This is not hosted genuine user Auth or vendor clinical evidence.
  • HOSTED VERIFIED — separately authorized installed laboratory identity, real interface/custody, genuine users and independent clinical/security witness. It is not established by the current synthetic ULC evidence.

ULC disposition and non-equivalence

  • U01 rich durable persistence remains PARTIAL; advanced imports are held/draft-only. U06–U09 vendor/live acceptance remains PARTIAL.
  • U10–U14 clinical review, Programs, network eligibility/pricing and R1 compatibility are source/projection contracts. The separate U11 A/B persisted proof is isolated only.
  • U15 remains PARTIAL: draft/wire/callback transformations are not a single joined Nexus canonical transaction. U16/U17 PASS_ISOLATED; U18 PASS_CI for the supplied selected run; U19 PASS_SOURCE.
  • A second lab reuses the same importer/executor with independent profile/credentials/codes/specimen. Config reuse is not a second real vendor certification.

Gates and next evidence

R0–R5 and G0–G10 are release-scope gates, not a count of passing tests. CA-READY G2 genuine signed-in/browser acceptance, G4 vendor ACK/archive semantics, G6 deployed issuer/collector/crash telemetry and G7–G10 Core/vendor/provider/clinical/security/launch approvals remain OPEN. Other source evidence does not override these gates.

  1. Shamil attaches exact run/SHA and selected scope; keep historical broad-suite debt separately owned.
  2. Core owner reviews installed authority and advanced persistence; no staged package is applied by documentation.
  3. Lab IT/vendor confirms actual ACK, idempotency, callback and finality semantics. Clinical reviewer and security/ops independently approve.
  4. Only separately authorized hosted acceptance and launch review can establish readiness; Production remains NO-GO.

Related resources