Prospectus
Written for organizations that want the capability without the Uni-edit name on it. Four partner models, the white-label module list, and an explicit statement of what is never exposed to a partner.
Prospectus · PDF, v2 · Short form, 7 sections
Some buyers do not want a supplier. They want a capability they can put their own name on, sold to their own clients, on their own terms.
This prospectus is written for them: editing companies, language-service providers, legal-service providers, publishers and institutional platforms. The premise is that the partner keeps the customer relationship, the brand, the pricing, the standards and the final release authority, and adds a configurable document operations layer underneath.
Four partner models, by how much you want to operate. A module licence, where your staff run selected software functions inside your own portal and customer journey. A managed white-label workflow, where you own brand, policy, pricing and client approval while Uni-edit runs the system, the processing, the QA artifacts and optionally the specialists. Overflow capacity, where your normal staff and workflow continue and temporary volume moves under pre-agreed scope and service levels. Or a private deployment, where the environment and compliance authority are the customer's and Uni-edit supplies deployment engineering, mappings, validation and maintenance.
What can be white-labelled. The editing workflow, with scoped first-pass work, review items, tracked-document reconstruction, handover and QA. The translation workflow, with source control, improvement, bilingual alignment, terminology and specialist review. Reference intelligence, covering citation-reference reconciliation, style normalization, evidence-backed verification and risk classification. Document engineering: comparison, tracked changes, field-aware checking, conversion and manifest generation. And the workflow console itself, with intake, state, checkpoints, exceptions, approvals, costs, service levels and delivery records.
What is never exposed, stated in the document rather than discovered later. Proprietary prompts, internal rubrics, source code, model-cost structure, staff-margin assumptions and reusable customer data stay out of every partner-facing file. So does every other partner's terminology, configuration, usage, analytics and operating pattern. Unapproved AI output and internal technical logs do not reach end customers. Partners receive assurance, not the implementation. That is a limitation, and it is stated as one, because a partner who discovers it during procurement rather than in the prospectus has been handled badly.
The legal suite is the worked example. ue-ai-legal-suite is presented as a configurable document-production and quality-control layer for contracts, tenders, filings, regulatory material and official-document sets: matter and document state as one controlled record; bilingual alignment with source authority and segment-level comparison; controlled transformation under explicit scope; review gates with human authority before release; an evidence package carrying the manifest, the checks performed, the unresolved risks, version hashes and the delivery record; and an offline-first option for work that prohibits cloud inference. Read the status note below before treating any of that as purchasable.
Standards-ready, not standards-certified. A partner can select a control profile and require evidence against applicable policies and contract clauses. Neither Uni-edit nor the partner may represent a mapping as a certification, and the document says so.
The commercial path is six steps, beginning with a control-profile workshop and a paid pilot on representative difficult documents, and ending with a quarterly evidence, security, model and workflow review. Nothing in it is a checkout.
Editing companies, language-service providers, legal-service providers, publishers, and institutional platforms.
Our material cannot go to a cloud model.
A control-profile workshop.
Status of the legal suite. ue-ai-legal-suite is a demonstrator and a white-label proving ground, built for one real customer engagement. It is not an off-the-shelf product. No licence terms, price, service level or support model exist for it, and no other customer is running it today. It is offered through the UE AI Editor Suite rather than as a separate legal product, and this prospectus describes a worked example of a vertical the suite can support, not an engagement that can be bought today.
Not legal advice. Neither Uni-edit nor the software provides legal advice, representation, certification of legal validity, or any opinion on a document's legal effect. The software governs terminology and flags inconsistency for a human reviewer. Nothing here implies admissibility, court acceptance, regulatory compliance, or privilege. Legal editing and translation is a distinct discipline from academic translation and is treated as one.
White-label engagement models are available; they are not a track record. The four models describe how an engagement can be structured, in the present and conditional tense. Nothing here asserts that partners are operating on them today.
No certification. Uni-edit holds no ISO certification, accreditation or independent conformity assessment. A control mapping is not a certification, and neither Uni-edit nor a partner may present one as though it were.
Where the offline-first option is used, the evidence describes what happened inside that defined run. It cannot describe what happened on another device, before receipt, or outside the defined environment.
