The practice behind the Core Model.

Ariesnet is the half that faces the client: we contract, build, integrate and operate. ARAMAI is the half that faces the problem: it does the research and makes the software — CoreModels, as part of the Schematica suite of solutions. The split is deliberate. Ariesnet, Inc. is the contracting party on every engagement letter. When an agent answer is wrong in production, the engagement's acceptance criteria and Managed Operations' incident attribution say whose problem it is — and the change log shows what was fixed. There is no 'the model did it'.

One governed Core Model, and the Context Supply Chain around it. The model holds the mappings and governed meaning between the schemas your organization already authored — data and content platforms, the warehouse, APIs, ontologies, and the public standards they connect to. The chain is the seven stages that carry context from those sources to the agents that act on it: sources, structure, semantics, validation, retrieval, agent operations, and the learning loop.

Every engagement follows the same arc. The interview maps the landscape. The Assessment inventories the connectors each system needs and blueprints the model — what imports first, how the schemas harmonize, what conformance contract the boundaries enforce, which agents read from it. Implementation facilitates the import of your schemas into CoreModels and the harmonization between them, with your engineers in the model and the change log as the record of what was decided. Managed Operations keeps the model true as systems change: new connectors, drift caught before an agent reads it, failures fixed in the model rather than in a prompt.

Ariesnet has built production software for enterprises since 1997 — custom systems, then integration work, then content supply chains for large publishers. Integration teaches one lesson you cannot unsee: the systems were rarely the problem. What moved between them was, because no two of them agreed on what a thing was. CoreModels is the answer to that lesson, and this practice is how it gets into an enterprise and stays there.

• One model, not another integration — the mappings live in the Core Model with the change log as the record, never in a prompt.
• Assessment output is yours outright — an engagement can end with you executing the plan yourself.
• Fixed scope, fixed fee, priced before we start — and a written no-go when the evidence says wait.

Every engagement is fixed-scope and fixed-fee, priced before it starts. Assessment work produces a written deliverable you own outright and can act on with any implementation partner, including your own team.

ARAMAI is the product group of Ariesnet, Inc., a Texas corporation. CoreModels is its platform, as part of the Schematica suite of solutions. Ariesnet contracts, builds and integrates for clients, and operates; ARAMAI does the research and makes the software. Our engagements configure, deploy and operate CoreModels alongside the systems a client already runs. The platform is licensed on coremodels.io; Implementation and Managed Operations engagements include the licence for the engagement term.

You own the Core Model. Export it any time to JSON Schema, JSON-LD and ShEx, with your mappings; the change log is yours on exit.

The Core Model is the source of truth and its JSON Schema render lives in your GitHub during the engagement — pushed with a diff preview; changes made in the file are listed for review and enter the model only if you choose them.