# Ultimus: Context Engineering, Served Both Ways

> Agents do not need more tools. They need better context. Adjective is a context engineering company. We serve context both ways: to agentic systems, and to the people who run them.

Canonical: https://www.adjective.us/ultimus

Agents do not need more tools. They need better context. Adjective is a context engineering company. We serve context both ways: to agentic systems, and to the people who run them.

Most stacks are organized by product. Ours is organized by where context comes from and where it goes. That is why nothing here is sold as a standalone name. Each piece is a module of Ultimus, and each one tears away.

## Where context comes from

- **Internal environments and codebases.** What is true about how you work. Architecture, constraints, dependencies, read across every codebase and system.
- **External sources.** What is true about the world. For each source you care about, we create a discrete feed: structured, scored, and live.
- **Ultimus' own activity.** Everything Ultimus does is collected, vectorized, and added back to our API and MCP layer. The next task starts with what the last one learned.

One layer manages and enriches all three. It signs and verifies what enters, routes it through a single API and MCP gateway, and keeps the record.

## Two readers, one record

Context flows out two ways. To agentic systems, as structured context over API and MCP. To people, as reports they can read, audit, and act on. Both consume the same resources, so both see the same numbers: token rates, cost, and environmental statistics like carbon. Both use them to adapt.

- Agents: An agent reads it to choose a cheaper path or a lighter model.
- People: A person reads it to change a workflow, a model, or a budget.

## Four perspectives

Ultimus sits in the center of four contextual perspectives. Every decision it makes is checked against all four.

- **Efficiency.** What the work costs, in tokens, dollars, and carbon.
- **Safety.** What it is allowed to do, signed and verified.
- **Reliability.** What is true, and whether the result holds up against your tests.
- **Utility.** What it is worth: whether the work moved the outcome that matters.

## The modules

Each module is tearaway. Add one to a deployment you already run, or take the whole of Ultimus. We can augment your current projects, or fully manage a standalone product.

### Internal Context Feeds

*Internal Environments & Codebases.* Agents cannot operate blindly. This is the context of your own environment. It reads across your codebases, documents, and systems, and emits structured, machine-readable ground truth about your architecture, constraints, and dependencies, so agents act on reality, not guesses.

[Internal Context Feeds](https://www.adjective.us/ultimus/environment-context)

### External Context Feeds

*External Sources.* Agents need continuous awareness. We create a discrete feed for each external source you care about. Today that means the open-source science and technology landscape, analyzed and scored in real time for agents to consider. At over 100,000 scored entities, it feeds your systems live, structured intelligence on what is defensible, what is moving, and what is risky. This feed helps continuously optimize resource utilization.

[External Context Feeds](https://www.adjective.us/ultimus/external-context)

### Context Management

*Authority & Gateway.* The control point. It manages and enriches the context between your internal environments and codebases, your external feeds, and Ultimus' own activity. It is the sign-and-verify authority, and the MCP and API gateway, for everything that emits from any of them. Every high-consequence action is signed into a mathematically unforgeable log, and exact token consumption, compute costs, and carbon intensity are tracked using zero-knowledge patterns, giving you audit-ready financial and ESG reporting without exposing proprietary data.

[Context Management](https://www.adjective.us/ultimus/context-management)

### The Ultimus Harness

*Sovereign Agentic Harness.* The execution layer. Ultimus makes sense of all the context and executes. It is a local-first, model-agnostic agent harness that runs tasks, validates its own work against your test suites, and operates strictly within the policy boundaries you define. It cannot wander, it is completely controlled by the governance you design.

[The Ultimus Harness](https://www.adjective.us/ultimus/harness)