Nace AI publishes Drex Technical Report on RLAF for open-source decision models
Nace AI has positioned its Drex Technical Report as a developer-facing disclosure of how state-of-the-art open-source decision models are trained with RLAF, framed alongside a Console sign-in entry point described as a data intelligence suite for AI agents and builders. Third-party TestingCatalog surfacing routes attention via a syndicated X quote while sending readers to the primary Console link. The company describes a 51-page treatment of how Drex, open-weight models that pick answers from fixed lists, was trained, citing roughly 1.15 million verified decision examples for Drex v1.5 spanning tasks such as reading contracts. Practitioners gain a stated window into training methodology; the packet does not independently verify metrics or supply technical detail beyond what Nace asserts in its announcement thread.
Nace AI publishes Drex Technical Report on RLAF for open-source decision models
Nace AI states it is publishing the Drex Technical Report for developers and points to open-source decision models trained with RLAF in the same announcement thread. The TestingCatalog surface highlights the item while routing readers through the syndicated X quote and primary Console link.
Key takeaway
Nace is packaging Drex training disclosure alongside Console access and multi-channel syndication, so adoption and scrutiny hinge on the report and tooling, not headline claims alone.
What happened
According to the packet, Nace AI states it is publishing the Drex Technical Report for developers and, in the same announcement thread, points to open-source decision models trained with RLAF, while TestingCatalog highlights the item and routes readers through a syndicated X quote and the primary Console link.
Attributed text in the corpus reports that Nace AI published a 51-page account of how it trained Drex, describing open-weight models that pick the most likely answer from a fixed list of options and stating Drex v1.5 was trained on 1.15 million example decisions with verified answers, including tasks such as reading contracts.
Evidence
Nace AI ties the Drex Technical Report publication to RLAF-trained open-source decision models in the announcement thread.
Nace · attributed
Nace AI states it is publishing the Drex Technical Report for developers and points to open-source decision models trained with RLAF in the same announcement thread. The TestingCatalog surface highlights the item while routing readers through the syndicated X quote and primary Console link.
The Console entry page is presented as Nace.AI sign-in with a data intelligence suite framing for AI agents and developers.
Nace · attributed
Sign in to Console by Nace.AI. Data Intelligence suite for AI agents and developers.
The announcement text invites developers to discover how state-of-the-art open-source decision models are trained with RLAF and points to an external build link.
Nace · attributed
Today, we are publishing the Drex Technical Report for the developer community! 🚀
Discover details on how the State-of-the-art Open-Source decision models are trained with RLAF.
Build more at: https://t.co/fm3GXfjaqx (try for free)
Nace describes Drex as open-weight decision models trained on a large set of verified examples across tasks including reading contracts.
Nace · attributed
Nace AI has published a 51-page report on how it trained Drex, its family of open-weight AI models that pick the most likely answer from a fixed list of options.
Drex v1.5 was trained on 1.15 million example decisions with verified answers, covering tasks from reading contracts
Why it matters
Open-weight decision stacks affect procurement, compliance workflows, and reproducibility expectations when vendors publish training detail alongside product entry points.
Limits and uncertainties
The packet does not provide independent verification of the 51-page report contents, the 1.15 million-example figure, or task coverage beyond Nace’s attributed statements.
The primary URL resolves to a Console sign-in page, not a direct document landing page, so readers cannot confirm report access mechanics from this packet alone.
TestingCatalog routing and the syndicated X quote are described as distribution mechanics without third-party editorial assessment of technical accuracy.
Practical implications
Operators evaluating Drex should treat the technical report as the primary artifact for methodology review while treating Console access as a separate product onboarding step.
Builders comparing RLAF-trained decision models need to map stated training data scale and task mix to their own evaluation suites before relying on fixed-option answering behavior.
What to watch
Whether Nace publishes the Drex Technical Report through a direct, stable document URL independent of Console authentication.
Independent benchmarks or red-team results on Drex v1.5 across contract-reading and adjacent tasks cited in the packet.
Changes to how TestingCatalog or the syndicated X surface summarize or link the announcement relative to the Console entry point.
