GENYRA Let’s talk
☰
CUSTOM AI / MANAGED OPERATION

Deployed is not finished.

Monitoring, versioning, change control, cost and incident handling for an AI system in use, with a named operator. Custom AI engagements are contracted with Genyra L.L.C-FZ, the separate Dubai company that operates genyra.ai. Genyra.com describes the practice; the agreement names the company doing the work.

Discuss the work
Illustrative engineering modelLocal / no external action
Request / illustrative workflow

Automate the rule.
Keep the judgement.

Computed decisionNeeds context

Collect the missing information before proceeding.

01Inside the work

Watch the system, not just the servers.

Operation covers the usual measures of an environment and the ones particular to an AI system: how often answers are sent back by reviewers, how often the system reports that the material holds no answer, which documents are retrieved and which never are. These are reviewed on a schedule with the organisation, and they are the first sign that something has changed.

Managed operation is contracted with Genyra L.L.C-FZ in Dubai, which operates genyra.ai; genyra.com describes the practice. The agreement names the operator and the responsibilities on each side.

02Inside the work

Models and prompts are versioned.

Every model build and every prompt in use has a version, and every logged answer records which versions produced it. A change to either is a release: tested against the organisation’s evaluation set, recorded, and reversible. No model or prompt changes quietly.

Matter M-2041 · illustrative · not a customer system
External public networks · shared model services No data leaves
Client environment one boundary · four workloads
  • Document store matter files · scans · PDFs
  • Retrieval index this organisation only
  • Model runtime build 2026.10-03 · no training
  • Audit log append-only · kept by the client
Boundary drawn · no crossing
Matter M-2041question received

Question · A. Reyes · 11:32

Which clauses limit assignment?

Scope: the three documents filed under M-2041. Processing inside the client environment. No outside service is called.

Retrieved passages3 of 3 · this matter only
  1. [1] MSA-2041.pdf · clause 14.2 Neither party may assign this agreement without the prior written consent of the other.
  2. [2] Schedule-3.pdf · clause 3.5 Consent is not required for an assignment to an affiliate, provided the assignor remains liable.
  3. [3] Amendment-2.pdf · clause 2.1 Clause 14.2 applies to any assignment arising from a change of control.
Draft answermodel 2026.10-03 · for review

Three clauses limit assignment. The agreement may not be assigned without the other party’s written consent [1]; an assignment to an affiliate needs no consent while the assignor remains liable [2]; and the consent requirement applies to an assignment arising from a change of control [3].

  • [1] MSA-2041.pdf · clause 14.2
  • [2] Schedule-3.pdf · clause 3.5
  • [3] Amendment-2.pdf · clause 2.1

Limits. Drawn only from the three documents above. Correspondence and any later amendment outside the matter file were not checked. Whether a change of control has occurred is for the reviewer.

Review and recordreviewer · A. Reyes
Decision · 11:40 ApproveSend back
Audit log · append-only
No.AtWhoRecord
04152026-10-14 11:32:04A. Reyesquestion · M-2041
04162026-10-14 11:32:05systemretrieved 3 · MSA-2041, SCH-3, AMD-2
04172026-10-14 11:32:09systemdraft · model 2026.10-03
04182026-10-14 11:40:51A. Reyesapproved · docs MSA-2041, SCH-3, AMD-2 · model 2026.10-03
Boundary, retrieval, citation, review. One line in the audit log is what an auditor reads.
03Inside the work

Change control that the organisation can see.

Changes to the model, the prompts, the retrieval index, the permitted documents or the boundary are proposed, reviewed, approved and recorded. The organisation decides who approves each class of change. The record shows what changed, when, by whom and what the evaluation showed.

04Inside the work

Cost and capacity, stated and watched.

A private deployment has a known capacity: the compute it runs on, the volume it can handle and what it costs to run. Usage is measured against that, growth is planned rather than discovered, and the organisation sees the figures before a change in capacity is made.

05Inside the work

Incidents have an owner and a record.

A wrong answer that reached a person, a document indexed that should not have been, a failed release or an outage is handled as an incident: contained, examined, recorded and reported to the organisation with what will change. The audit log and the version history are what make the examination possible.

06Inside the work

Who operates it.

The agreement names the operator. We can operate the system under the terms agreed, operate it jointly while the organisation’s team learns it, or hand it over with the runbooks, version history and records needed to operate it alone. In every case the organisation retains its data, its logs and its evaluation set.

CONTINUE THE EXPLORATION
Private AI deploymentCustom AI solutionsManaged infrastructure
A CLEARER NEXT STEP

Discuss managed AI operation

From an unanswered question
to an engineered possibility.

Discuss managed AI operation
Chat on WhatsApp