Custom environment pilots for selected frontier AI teams
Environment engineering

From raw operating history to executable training worlds.

Sofitra preserves the structure that makes real work difficult (tools, state, permissions, dependencies, exceptions and expert review) and packages it into a resettable system for training and evaluation.

The design principle

An environment is not a folder of files with a question attached.

It is a living state machine: the model must inspect evidence, operate tools, make changes, obey hidden constraints, recover from errors and leave the world in a verifiably correct state.

Foundry architecture

Three layers. One traceable system.

Every task is connected to an authorised data source, an executable environment state and a measurable reward specification.

LAYER 01 / DATA UNIVERSE

What the world knows.

A privacy-safe, internally coherent information universe reconstructed from real company artifacts and histories.

  • Documents and source evidence
  • Structured tables and databases
  • Historical versions and corrections
  • Communication and decision context
  • Rights and lineage metadata
LAYER 02 / EXECUTABLE WORLD

What the model can do.

Tools, permissions, starting state, transitions and hidden dependencies required to reproduce the workflow.

  • Resettable application state
  • Document and spreadsheet tools
  • APIs, databases and message systems
  • Role-based permissions
  • Event and action logging
LAYER 03 / LEARNING SYSTEM

How progress is measured.

Tasks, trajectories, difficulty distributions, verifiers and model-failure feedback loops.

  • Task families and curricula
  • Gold and repair trajectories
  • Outcome and process rewards
  • Hidden holdouts and adversarial tests
  • Versioned failure taxonomy
Environment anatomy

Everything a model needs to experience the work.

The environment exposes only the information and tools available to the professional at that moment. The verifier sees more.

01 / STATE

World state

The starting condition, hidden facts and consequences that make each run meaningful.

  • Seeded initial data
  • Role and permission model
  • Hidden constraints and dependencies
  • Deterministic reset behaviour
02 / ACTIONS

Tool surface

The applications and operations the model can use to inspect, edit and submit work.

  • Files, workbooks and editors
  • Search, databases and APIs
  • Messages, approvals and handoffs
  • Auditable action interface
03 / OUTCOME

Success state

The condition the model must create, not merely the prose it must produce.

  • Correct artifacts and system state
  • Resolved source evidence
  • Constraint and policy compliance
  • Expert-quality decision output
Task production

Curricula built from real variation.

Instead of paraphrasing one problem repeatedly, Sofitra uses historical cases, corrections and failure patterns to vary the state itself.

01 / BASE CASE

Canonical workflows

Representative end-to-end tasks that establish the core skill and expected professional standard.

02 / EDGE CASE

Operational exceptions

Rare but consequential situations recovered from actual review and escalation histories.

03 / BROKEN STATE

Repair tasks

Partially completed or corrupted work that demands diagnosis rather than generation from scratch.

04 / AMBIGUITY

Judgment tasks

Cases with incomplete evidence, competing constraints or multiple defensible actions.

05 / ADVERSARIAL

Shortcut traps

Tasks designed to expose memorisation, template following, superficial citation and reward gaming.

06 / FRONTIER

Failure-derived tasks

New distributions generated directly from observed model weaknesses during evaluation and training.

Verification stack

Reward the result. Inspect the path.

A single scalar score can hide the reason a run failed. Sofitra exposes reward components and evidence at the level researchers need.

01 / DETERMINISTIC=

Rules and calculations

Formulas, reconciliations, database state, file structure, numerical tolerances and policy conditions.

02 / GROUNDINGSRC

Evidence validation

Citation resolution, source authority, claim coverage, temporal validity and contradiction checks.

03 / PROCESSLOG

Trajectory checks

Prohibited actions, required review steps, tool-use sequence, approvals and state-changing behaviour.

04 / JUDGMENTEXP

Expert rubrics

Domain-specific quality, materiality, escalation, communication and decision standards.

Anti-reward-hacking

The verifier is treated as an attack surface.

We test whether a model can earn reward without genuinely completing the task, and harden the environment against that path.

01 / HIDDEN

Private holdouts

Unseen data, rules and state checks prevent overfitting to the visible specification.

02 / CROSS-CHECK

Independent evidence

Critical outcomes are validated through more than one data source or calculation path.

03 / MUTATION

Adversarial variants

Inputs and environment state are mutated to test whether the strategy generalises.

04 / REPLAY

Action inspection

State transitions reveal destructive shortcuts, fabricated evidence and prohibited operations.

Delivery

Built to meet the lab where it is.

The same environment specification can be packaged for training, private evaluation, model comparison or internal research infrastructure.

01 / CONTAINERS

Containerised runtimes

Versioned images with reset hooks, seeded state and structured event output.

02 / INTERFACES

APIs and tool protocols

Model-agnostic action schemas compatible with existing agent harnesses.

03 / DATA

Task and trace manifests

Structured metadata, splits, trajectories, artifacts and verifier diagnostics.

04 / GOVERNANCE

Evidence and rights pack

Lineage, transformation, permitted use, environment cards and version history.

Environment pilot

Build the world your model needs to master.

Start with a task family, a model failure or a real workflow that is not represented in public data.