FastYoke at the edge — integrity you can attest

Hardware-attested integrity is a hard requirement for the Certified tier. A device qualifies when it provides:

1. TPM 2.0 — discrete preferred; firmware/fTPM acceptable on x86-64.
2. UEFI Secure Boot — or an equivalent verified boot chain on ARM64.
3. Measured boot — PCR extension that FastYoke reads at agent startup.

FastYoke reads the TPM quote and measured-boot PCRs on start and surfaces edge-node integrity attestation as a compliance control in your Trust Center and auditor room. Your SOC 2 / compliance story extends all the way down to the edge — not "the gateway is locked in a cabinet," but "here is the measured, signed proof that this node booted the software we shipped."

Every exposure is a regulated event. The device console captures the delivered dose, the kVp, the filtration, the geometry, the operator identity, and the subject cohort — and every one of those fields is required by the study protocol, the animal-care protocol, and the retention regime that follows. Miss the timestamp and take a finding at the animal-care review. Miss the operator signature and take an e-records deviation at the sponsor audit. Miss the dose-rate calibration link, and the paper the study feeds cannot be published.

FastYoke Edge sits between the device and the compliance regime. An Edge Agent talks to the console over RS-232/RS-485, a DICOM MPPS feed, or a vendor-proprietary file drop — pulls the session record the moment the exposure ends, signs it with the tenant's key, writes it to the on-device per-tenant SQLite, and syncs to the tenant's cloud tier as soon as network returns. The device console is unchanged. The operator's workflow is unchanged. The record that lands in the research-data-management system carries the boot-attestation evidence for the device that produced it — so an auditor doesn't have to trust the record, they can verify that the device that wrote it was in a known-good state at exposure time.

The mechanism is compatible with a Part 11 retention regime — the append-only event log, per-tenant crypto, and RBAC primitives that Part 11 asks for are already how FastYoke stores every other tenant record. Mapping the specific controls to a specific regulatory posture is a conversation, not a checkbox.

Every mile is a regulated event. A refrigerated trailer running a mixed produce load carries a temperature-record obligation the receiver will absolutely audit at the dock — miss a five-minute excursion and the receiver either accepts the load with a claim attached or refuses it outright. The reefer unit already produces the reading on its own Modbus bus. What it doesn't do is timestamp it against dispatch, GPS-anchor it, sign it, and survive the 400-mile stretch of I-40 through the Texas panhandle where LTE is a suggestion.

FastYoke Edge sits in the cab. An Edge Agent talks to the reefer over RS-485 or J1939, pulls the temperature reading on the duty-cycle interval the load called for, tags it with the load number and the driver, signs it with the carrier's tenant key, buffers to on-device SQLite, and syncs to dispatch when the truck rolls into a working tower. The receiver sees the signed record before the trailer is dropped. The chain-of-custody story runs from origin to delivery with cryptographic receipts at every hop — compatible with an FSMA Sanitary Transportation retention posture, without asking the driver to touch a tablet.

The same Edge Node runs at the DC gate. A camera reads the container number, the gate boom opens against the appointment window, and the yard system records the arrival — locally, sub-second, then syncs. A three-second cloud round-trip to open a gate is not a technical inconvenience; it is a queue backing up onto the highway.

Every transaction is a customer relationship. When the store's ISP hiccups mid-swipe, three things need to keep working: the card reader has to take the payment on the local acquirer path; the cash drawer has to open on the receipt-printer command; the inventory has to decrement so the next customer isn't sold the last unit twice. Cloud-only POS gives you an outage window the size of the ISP's next fibre-cut. Local-first POS gives you a store that runs the same on a bad-network day as on a good one.

FastYoke Edge sits behind the counter. The Edge Node runs the POS locally — card reader over USB/HID, receipt printer over serial, cash drawer over the drawer-kick line, scale over RS-232 — writes every sale to per-tenant SQLite, signs the transaction, and store-and-forwards to the corporate cloud tier when the pipe comes back. The receipt has the customer's name on it. The close-of-day report has every sale on it. The inventory decrement survived the outage.

The same Edge Node runs receiving at the back door. A scanner reads the pallet label, the ASN comes down from corporate, the Edge Node reconciles line-by-line and flags the discrepancy before the truck leaves. Receiving-window claims that would have been argued from a paper log are argued from a signed record.

Every visit is a coordinated handoff. When a patient arrives at an ambulatory clinic, the check-in kiosk verifies identity, scans the insurance card, settles the copay, and marks the appointment as arrived — four systems talking to each other on a network that fails at exactly the wrong moment. Cloud-only front desks either turn patients away or fall back to paper that gets keyed in later, at which point the arrival time is a guess and the copay reconciliation is a spreadsheet. Local-first front desks keep the schedule running through the ISP outage and flush to the corporate cloud tier when the pipe returns.

FastYoke Edge sits at the front desk and on the ward. An Edge Node runs the check-in flow locally — kiosk, insurance card scan, driver-license verify, copay POS, throughput board updates — and store-and-forwards to the corporate cloud tier when the pipe comes back. Facility badge readers and access-controlled room events (the medication room, the medical-records room, the IT closet) land on the same signed audit trail. The Patient Flow Yoke's throughput boards render off the local SQLite so a census view updates in real time regardless of the corporate network's mood.

The scope of the vertical is deliberate. FastYoke Edge does not sit in the clinical decision path — no medication administration verification, no vitals interpretation, no point-of-care result alerting. Those surfaces are FDA-regulated medical device territory and require a separate compliance program the platform does not carry. The Edge Node handles the administrative workflow — appointments, arrivals, throughput, access, audit — and hands off to a certified clinical system for anything that mediates a treatment decision.

The mechanism is compatible with a HIPAA administrative-safeguards regime — signed access records, per-tenant crypto, and the append-only event log that HIPAA §164.312(b) asks for are already how FastYoke stores every other tenant record. As with the preclinical imaging story, mapping specific controls to a specific regulatory posture is a conversation, not a checkbox. Tenants handling PHI pair the deployment with the BAA / HIPAA posture add-on.

Every repair order is a warranty case in waiting. When a diesel truck rolls into the bay with an emissions fault, the shop's scan tool pulls the DTC and the freeze-frame data from the ECM over J1939 or OBD-II. That capture is the warranty evidence. Six months later, when the manufacturer denies the claim, the argument runs on whether the scan tool output was signed, timestamped, and bound to the correct VIN — not on whether the technician remembered which port they connected to. The scan tool already produced the record. What it doesn't do is timestamp it against the RO, sign it with the shop's tenant key, and survive the shop-management-system provider's next monthly outage.

FastYoke Edge sits in the shop. An Edge Node ingests the scan tool's output over USB or the bay's diagnostic Ethernet, binds it to the open RO, correlates it with the ECU photo the technician just snapped, signs the whole envelope, and pushes to the shop management system when the network is present. The manufacturer's warranty audit runs against a signed record set, not against a photocopy in a file folder.

The same Edge Node runs the fuel island at the fleet maintenance depot. Fuel dispenser, tank-monitor console, driver-badge auth, odometer capture — all local. When the depot's internet is down, drivers still fuel, and the reconciliation lands the moment the pipe comes back. Emissions test lanes get the same treatment, with signed VIN + dyno + tailpipe records that satisfy the state DMV's chain-of-custody requirement.