Application & agent code
Services, APIs, UIs, agent logic, tool adapters, and workflow orchestration implemented for your program.
IP Ownership
What you own when we hand over.
“You own the code” is a contractual and technical commitment, not a slogan. Here is the scope InheritX transfers on production AI engagements.
Perspective
Ownership is the point of the engagement
Many AI vendors accelerate pilots by keeping the valuable layer, orchestration, fine-tunes, evaluation, and workflow glue, inside a rented platform. InheritX is built the other way: we implement capability inside your estate and transfer what we create for you.
Exact transfer terms are defined in the statement of work and master agreement for each engagement. The lists below describe our standard intent for production build programs. A detailed IP schedule can be shared under NDA during diligence.
Capabilities
Typically transferred to you
Unless the contract states otherwise, production build engagements are designed so you retain:
Fine-tunes & adapters trained for you
Model weights/adapters fine-tuned on your approved data for your use, remaining your IP.
Prompts, policies, and evaluation assets
Prompt libraries, guardrail configs, offline eval suites, and runbooks created for your system.
Infrastructure-as-code for your estate
IaC and deployment definitions targeting your cloud accounts so your teams can operate and extend the system.
Capabilities
What you should not assume is “owned”
Third-party foundation models
Commercial model licenses (OpenAI, Anthropic, etc.) remain governed by those providers’ terms. We help you choose and integrate, they are not InheritX IP to transfer.
Your pre-existing systems & data
Your ERP/EHR data, brands, and prior codebases remain yours; we do not claim them.
InheritX accelerators reused across clients
Generic internal tooling may speed delivery. Anything material reused is disclosed in the SOW; customer-specific work product still transfers.
How we engage
Handover package (standard intent)
At go-live, production programs aim to leave your team with operable ownership, not tribal knowledge.
01
Source & environments
Repositories, CI/CD definitions, and environment documentation under your control.
02
Security & operations
Access model notes, secret locations, observability dashboards, and incident basics agreed for hypercare.
03
Evaluation & governance
Eval harnesses, approval-gate configuration, and policy docs for high-risk actions.
04
Enablement
Runbooks and walkthroughs so internal owners can operate, extend, and audit the system after we step back.
FAQ
Ownership questions
Customer-specific work product is not resold as a productized clone of your system. Contract language governs residual knowledge and any shared accelerators, ask for the IP schedule in diligence.
Assets created for your program are intended to transfer with the system so you can continue improving quality after handover.
Yes. We expect enterprise counsel to review ownership, data processing, and confidentiality terms before build begins.
Next step
Map this capability to your mandate.
A focused strategy conversation, constraints, systems, and what production readiness looks like for your organization.