The words we use, and the questions buyers ask.
Context Infrastructure is a new category, so some of its vocabulary is new. These are the terms as Orelis uses them, followed by the questions a CFO or General Counsel asks first.
Context Infrastructure, in its own terms.
- Context Infrastructure
- The system of record for an organization's judgment. It captures what the organization decided and why, compounds it with every deal, and keeps it available at the point of the next decision. Not a tool and not a repository: foundational infrastructure beneath every system, relationship and decision the organization runs.
- The System of Record
- The authoritative record of what was decided and why, live at the point of the next decision rather than filed in an archive. Every function already has one for its facts: the general ledger for money, the CRM for relationships, the document system for what was signed. None of them holds the reasoning. Context Infrastructure is the system of record for that.
- Context that Compounds
- The product truth in three words. Each deal, decision and counterparty captured deepens the Index, so the next deal is faster, more accurate, and closer to how the organization actually operates.
- The Index
- Orelis's compounding system of record: every position taken, every decision and who made it, every counterparty and how it has negotiated with you. It holds Client Data, which the client owns. The Index system that reads and compounds it belongs to Orelis.
- The Charter
- The package Orelis prepares for each matter: a first draft with your positions applied, the open issues and every departure from your standard, and a briefing for counsel. It arrives before the attorney starts, prepared for their review.
- The Ledger
- The monthly account of what Context Infrastructure is worth: outside counsel spend before and with Orelis, what was saved, and how the Index grew.
- Active Capture
- Knowledge captured as a byproduct of the work, not through a separate act of documentation. The client routes what it already sends and receives. It never reproduces it.
- The Write-Back Loop
- The cycle that makes the Index compound rather than merely accumulate: draft, deliver, close, record the outcome, update the counterparty record, inform the next draft.
- Context Depth
- The richness and completeness of a client's Index relative to its transaction history. It rises with every document read and every outcome recorded, and it is why month six prepares a better Charter than month one.
- Context Velocity
- How fast an organization can surface the right context at the right moment. High context velocity means a team walks into a transaction already prepared, not getting prepared.
- Context Debt
- The accumulated cost of decisions made, deals closed and relationships built without their context being captured. Like technical debt, it builds invisibly. The interest comes due when a key person leaves, a deal is litigated, or the same mistake is made twice.
- Knowledge Bleed
- The continuous, unmeasured loss of what an organization knows through normal attrition: retirements, departures, role changes. It accelerates at exactly the moments continuity matters most.
- Context Vacuum
- Entering a transaction without the relevant history of that counterparty, that deal type or that decision. Not because the knowledge does not exist, but because nothing surfaces it at the moment of action.
- Person-Resident Intelligence
- Knowledge that lives in a specific person's head, habits and judgment rather than in systems the organization owns. The most common form of organizational knowledge, and the most fragile: one resignation away from being lost.
- Open-Loop Execution
- Deals executed, decisions made and relationships managed without the intelligence they generate being captured and compounded. Each deal is complete in itself, and the next one starts from scratch.
- Context Decay
- The rate at which unrecorded knowledge loses accuracy over time. It accelerates with tenure, with personnel changes and with complexity, and it follows no schedule.
The questions a CFO or General Counsel asks first.
Is Orelis a law firm?
No. Orelis prepares work. Attorneys provide judgment. Orelis does not provide legal advice, and every document it prepares is for review by your own counsel. Your advisors stay: the Charter is drafted for them to pick up, make their changes, and return ready to send.
Who owns my data?
You own the documents and decisions you give Orelis. If you leave, you take an export of your Index and your documents. Orelis keeps patterns, not your documents or wording.
Which AI models does Orelis use?
Today Orelis runs on Anthropic's Claude, the model your contract names, and Orelis tells you before it adds or switches to a materially different provider for your data. It is built to move to whichever frontier model does the work best, and if your team already uses another AI model, Orelis is designed to work with it.
Can another client see my deals?
Your deals are your Client Data and are not shown to other clients. What can reach another client is limited to patterns, such as how documents are structured and how counterparties tend to negotiate, that Orelis's abstraction process is designed to strip of your identity, deal terms and transaction details, and only under the disclosure controls in your contract.
Do I have to change how my team works?
No. Your team forwards what it already sends and receives to your own Orelis address. Nothing is migrated, your systems stay, and your advisors keep working the way they do.
Will Orelis fill in a term it does not have?
No. A price, a date or a party you did not give is left as a marked blank and listed for counsel. Drafts are built never to fill in a fact you did not give them.
Is anything on this site real client data?
No. Every product window on this site carries sample data. The companies, people, deals and terms are fictional.
See your own deals the way Orelis sees them.
Become one of the companies that build alongside us and shape what the category can become.