The need is clear. What kills the engagement is the door: too big a commitment to start, or too slow a procurement to matter.
Four pathways into the same firm — a bounded pilot, a defined program, a multi-year institutional engagement, and procurement pathways built for federal acquisition teams. The entry point is sized to your risk tolerance and your contracting reality; the standard behind every door is identical.
Institutions rarely fail to engage because the need is unclear. They fail at the door. The vendor's only offer is a commitment too large to justify before there is evidence — so the decision waits, and the need does not. Or the engagement is right-sized and the procurement is not: by the time a vehicle exists, the moment that demanded the work has passed.
So the firm maintains four doors instead of one. A pilot exists so that evidence can precede commitment — bounded in scope, fixed in duration, and deliberately scopeable for streamlined acquisition. A program exists for the defined mandate. A multi-year engagement exists because most Afghan-language exposure is not a project but a standing condition, and standing conditions deserve standing capability. And a procurement pathway exists because federal buyers do not need persuasion; they need a partner whose registrations, documentation, and capability evidence make the acquisition itself straightforward.
What does not vary is everything behind the door. Each model runs on the same Orchestration Model, draws on the same Lapis Stack, and passes the same five gates. The size of the engagement changes. The standard does not.
Engagement Models are the four pathways into Ariana Nexus: a bounded Pilot that puts evidence before commitment, a Program for a defined mandate, a Multi-Year Institutional Engagement for standing exposure, and Sole-Source & Set-Aside Procurement Pathways maintained for federal acquisition teams. The entry point is sized to the institution's risk and contracting reality; behind every door run the same Orchestration Model, the same Lapis Stack, and the same Five-Gate Validation Protocol.
The entry point changes. The standard does not.
Pilot, program, multi-year, or a federal vehicle — the same orchestration, the same stack, the same five gates behind every door.
A bounded first engagement: fixed scope, a defined deliverable, weeks to a quarter — gated like everything the firm ships.
The standard engagement: a full program of work against a stated outcome — a language-access stand-up, a compliance program, a model-validation campaign, a data build.
The firm as an institutional layer: continuous capacity, continuous compliance, and measures that compound year over year.
The firm maintained as a procurement-ready partner — so that the vehicle, not the vendor, is the only open question.
The models differ in scope, term, and vehicle — and in nothing else. A pilot is not a discount product staffed by a junior bench; it is the full system at small scale. A sole-source award is not a shortcut around the gates; it passes the same five. The point of the architecture is precisely that entry size never determines quality, because quality is not negotiated per engagement. It is the system.
The only-one-responsible-source authority (FAR 6.302-1) is the agency's determination, made on the agency's market research. The firm's role is to make that research straightforward: validated operational coverage of all 24 Afghan languages, the Five-Gate Validation Protocol™, the published method registry, and 41+ Trust Center documents — capability evidence maintained for exactly this file.
De-risking facts: Washington, D.C. headquarters · primary operations in Virginia · no in-country presence in Afghanistan · ISO/IEC 27001- and GDPR-aligned posture · briefings under NDA.
The Federal Acquisition Regulation is undergoing structural revision (2025–2026 model deviations); figures above reflect the October 1, 2025 inflation adjustments. Confirm current thresholds and your agency's adopted deviations before drafting.
For program owners scoping a first engagement and acquisition teams building a file. Briefings are conducted under NDA, in Washington, D.C. or virtually.
Request a confidential briefing