
Sprint 55 · Aug 16–30, 2026
The mobile and web app applicants use to verify their identity.
Fixed an Android error that blocked uploading a captured photo ID during verification, and closed a login mix-up where scanning someone else's invite link could leave a user stuck mid-verification with no way to complete biometric consent.
The mobile app now gives a short vibration and chime when a liveness step (like a head turn) is successfully accepted, so users know it worked instead of repeating the step out of uncertainty — a top driver of negative feedback in recent reviews.
Closed a gap where the app let an applicant continue even when they didn't meet a client's minimum years-of-experience requirement.
Straightened misaligned text on the certification, trust-center, invite-code, and terms & conditions screens, and switched the biometric consent screen to a more readable font.
Also completed — internal testing & build reliability
The core system behind orders, background checks, and everything Cortex users touch.
Resolved auto-capture not triggering and back-of-ID scan failures — together the largest source of negative applicant feedback in July — along with a blinking-detection glitch that could reject a valid liveness check, and a specific Georgia driver's license that wouldn't scan.
An applicant's verification photo could previously be reached through a raw, unprotected link on the pass-verification page. That path is now closed.
Fixed the root cause of two mid-August slowdowns triggered by very large client organizations, resolved intermittent unresponsiveness during document scanning, and stopped one bad request from causing several unrelated requests to fail with the same error. Automated county and national criminal search processing is also more reliable, with fewer results delayed or missed due to timing issues. Underneath it all, we completed a major upgrade of Cortex's core database software for better long-term performance and stability.
CRAs can now submit an investigation request on an applicant's behalf, asking us to re-check an order when an applicant challenges their result. Available on request. Dispute outcomes now clearly state whether a dispute changed the report or not, instead of a single ambiguous "Resolved" label. Added one API call for partners to update an order's status and score together, and fixed signed disclosure documents that were failing to generate for a handful of legacy templates.
An order flagged for manual review due to a suspicious IP now shows the reviewer why. Running the same county search twice no longer returns inconsistent results. A criminal-search line item on reports was renamed for clarity, the verified user's name was added to the public credential-share page, and a Cortex order tied to a system-generated invite link that staff couldn't open is now fixed.
Also completed — client data investigations & internal config
What CRA staff, applicants, and clients see and click on the web.
Fixed several bugs where going "back" left the app in a broken state — including a completed order still showing prior screens, and a two-factor login attempt that could trap a user in an infinite loading loop. Also fixed the "Try Again" button on the service-unavailable screen, and modals that rendered broken on mobile.
When an applicant scans their ID with a phone while completing an order on desktop, a brief connection drop no longer strands the session. The two devices now recover and stay in sync automatically.
Fixed the biometric consent screen so text no longer runs off-screen and the required age checkbox is reachable on mobile. Fixed an overlapping share-link display and a horizontally scrolling contact page on mobile, and corrected address autofill so apartment/unit numbers populate properly.
Added a "Get Ready to Scan Your ID" screen before ID capture on web to reduce failed first attempts, added the verified user's name to the public wallet share page, and rolled out visible Databeamâ„¢ branding across the wallet-share and data-entry screens.
Also completed — internal tooling & design-system work
The engine that reads search results and decides what belongs on a report.
Expunged and sealed criminal records are now always withheld from reports, as required by law, and a Kentucky-specific record-suppression rule was added. A configurable rule now handles the salary threshold some states use to determine reporting eligibility. Fixed a case where a non-reportable code was incorrectly showing up as an offense, and improved name-matching so titles like "Mr." aren't mistaken for a first name. Cases with a date-of-birth mismatch are now flagged for human review instead of processed automatically.
Added direct links to county court websites alongside recommended searches, and made automated review flags and processing summaries easier for the operations team to interpret while working a case.
Case results that failed to reach Cortex due to a transient error now retry automatically instead of getting stuck, and a routing default for federal record searches was corrected and verified against real district mappings. Also verified, against real client-reported failures, that a batch of accuracy fixes for Advanced Reporting actually resolved them.
Also completed — internal engine rebuild & testing infrastructure
How Cerebrum's platform talks to client systems
Corrected how third-party review decisions update candidate status in a partner ATS integration, so candidates under review now show correctly instead of being auto-failed. Also corrected the mapping of a vendor's decision outcomes into Cortex order statuses, and fixed a state search sync that could leave results stuck instead of automatically retrying.
Professional license information collected from applicants is now passed through to the relevant background-check search automatically.