--- title: "Resources: briefs, explainers, glossary — Ariesnet" description: "Briefs, explainers and procurement guidance on building context supply chains for enterprise AI." canonical: "https://ariesnet.com/resources" last_updated: "2026-09-11T10:52:28.854Z" --- Resources # The thinking, and the paperwork. Ariesnet originals are canonical here. Pieces marked as syndicated are canonical on aramai.net and appear here as excerpts with attribution. [See the engagements](https://ariesnet.com/products) Library ## Everything we have published 7 Ariesnet originals · 2 syndicated from aramai.net Ariesnet original ### [Why MCP agents fail on schema, not reasoning — and how to map it](https://ariesnet.com/resources/why-mcp-agents-fail-on-schema) When an MCP agent picks the wrong tool or the wrong field, the cause is usually two systems that never agreed on what a thing was. How schema disagreement produces the failure, and how to map it before it reaches production. Sep 5, 2026 Brief · Ariesnet original ### [The Context Supply Chain — a field guide for enterprise AI leaders](https://ariesnet.com/resources/context-supply-chain-field-guide) The whole argument in one document, written to be read by an architect and forwarded to an executive. Sep 5, 2026 Brief · Ariesnet original ### [One governed definition, end to end](https://ariesnet.com/resources/governed-definition-end-to-end) One definition followed from the model to the places it is rendered and the checks that keep them honest — the entry, its change log, the JSON Schema export, the warehouse view, the graph projection, and the gate. Every company, system, person, figure and date in it is fictional. Sep 5, 2026 Brief · Ariesnet original ### [Schema Landscape Map — a sample (fictional insurer)](https://ariesnet.com/resources/sample-schema-landscape-map) A sample of what the interview produces — every system, owner, figure and name in it is fictional. It shows the shape of the map: the schema landscape, what needs to plug in, the disconnect register, complaints and opportunities, stage placement, and remediation options ranked. Sep 5, 2026 Brief · Ariesnet original ### [The L0 to L5 context maturity model](https://ariesnet.com/resources/maturity-model) How each stage is placed during an assessment, and what each placement actually means in practice. Jul 15, 2026 Brief · Ariesnet original ### [Procurement guide: buying context supply chain work](https://ariesnet.com/resources/procurement-buying-guide) Written for the procurement reader: what you are buying, how it is priced, what you own afterwards. Jul 12, 2026 Ariesnet original ### [Why AI agents fail on context, not intelligence](https://ariesnet.com/resources/why-agents-fail-on-context) The model is rarely the weak link. What reaches it usually is — and unlike a model, that part is engineerable. Jul 5, 2026 Syndicated · aramai.net ### [Schema authority for enterprise AI](https://ariesnet.com/resources/schema-authority-for-enterprise-ai) Without a governed schema layer, every downstream consumer invents its own interpretation — and they disagree silently. Jun 28, 2026 · Originally published on aramai.net Syndicated · aramai.net ### [Look up before you make up](https://ariesnet.com/resources/look-up-before-you-make-up) The cheapest reliability discipline available to an agent system: check before you assert. Jun 20, 2026 · Originally published on aramai.net Glossary ## Terms as we use them **Conformance gateway** The control point where context is checked against conformance and efficiency protocols before it is allowed into retrieval or agent use. See also: Context supply chain **Context supply chain** The end-to-end path that sources, structures, validates, retrieves, and governs enterprise context so agents can act on material that is correct, current, and usable. The industry has a name for this work now — context engineering. The context supply chain is how we do it. See also: Maturity level, Retrieval quality **Context yield** The useful context delivered per unit of cost, latency, and operational effort—how much fit-for-purpose material the supply chain actually produces. See also: Context supply chain **Governed write-back** Controlled updates from agents into systems of record, with ownership, checks, and audit so automated actions do not silently corrupt trusted data. See also: Context supply chain **Grounding rate** The share of agent outputs that can be traced to approved, retrieved context rather than unsupported inference or stale material. See also: Retrieval quality **Learning loop** Stage seven of the supply chain: whether a failure observed in production results in a change to sources, structure, semantics or evaluation. Without an owner this stage decays silently, because nothing breaks when it stops running. See also: Retrieval quality **Maturity level (L0 to L5)** A six-point placement applied per stage: L0 Ad hoc, L1 Structured, L2 Semantic, L3 Validated, L4 Operational, L5 Self-improving. Stages are scored independently — a mature retrieval layer sitting on L0 sources is a common and diagnostic pattern. See also: Context supply chain **Retrieval quality** Whether what comes back is the right material, established by evaluation against known-correct answers rather than by inspection. Untested retrieval can return something topically related and confidently wrong, which is the failure mode hardest to notice in production. See also: Context supply chain, Learning loop **ROKA (return on knowledge assets)** A quarterly statement of what changed in a context supply chain, what operating it cost, and what it returned — reported with the basis for each figure attached so a finance reviewer can check the arithmetic. See also: Learning loop **Semantic layer** The shared meaning layer that aligns terms, entities, and relationships across systems so agents and people interpret the same business facts the same way. See also: Context supply chain Next step ## Find out what your context is actually costing you. We work with enterprise AI and data leadership teams. Thirty minutes, and you keep the map whether or not you go further. Not ready to talk? Read the field guide instead. [Request an interview](https://ariesnet.com/interview) [Get the field guide](https://ariesnet.com/field-guide) What happens next 1. The interview. Thirty minutes on your schema landscape — optional parts can extend it to forty-five. You leave with a map of the connectors you need and the wiring it will take to reach one governed Core Model — yours either way. 2. A written scope. Fixed price, fixed dates, named deliverables. Published bands; your fee is fixed in the written scope before we start. 3. A rung on the ladder. We recommend starting at the two-week audit. Ariesnet Inc Incorporated 1997 · Texas, United States 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. Contact - [info@ariesnet.com](mailto:info@ariesnet.com) - [+1 214-932-3900](tel:+12149323900) - Texas, United States Elsewhere - [CoreModels ↗](https://coremodels.io/) - [ARAMAI ↗](https://aramai.net/) © 2026 Ariesnet Inc. All rights reserved. · CoreModels® is a registered trademark. ARAMAI™ and Schematica™ are trademarks. · Elements of CoreModels are patent pending. ## Sitemap - [Sitemap in markdown](https://ariesnet.com/sitemap.md)