CORE · In development

The intelligence foundation behind what we build.

CORE is being developed to connect context, AI capabilities, and useful workflows across Lorthen software.

Why CORE exists

Less time between tools. More time on the work.

Useful information tends to live in disconnected places — notes, inboxes, spreadsheets, and separate applications. The goal of CORE is to connect that information and the workflows around it, so people spend less time moving between tools and more time acting on what matters.

What Lorthen contributes

The layers we intend to build.

Intended architecture
A shared foundation designed so each product can draw on common capabilities.
Product-specific context
The knowledge, rules, and vocabulary that belong to each individual product.
Reusable capabilities
Common building blocks developed once and applied where they fit.
Workflow design
Practical sequences of work shaped around the people doing it.
Oversight
Human review and product-specific rules guiding how capabilities are applied.

How it comes together

Intended architecture.

Product context flows into AI capabilities and out into useful workflows — guided by human review and product-specific rules at each step.

CORE in practice

HESTOL as the first example.

HESTOL, our trading workspace in development, is where CORE’s direction is most concrete. Today, HESTOL’s public demo presents an AI-assisted workspace with planning, market context, session notes, and review in one place — using simulated data. The development goal is for CORE to supply more of the shared context and capabilities behind experiences like this over time.

Development example · Preparing a trading session

Product context
A trader’s plan, market notes and session history.
AI capabilities
Summarize relevant notes and surface questions for review.
Useful workflow
Build a preparation checklist for the trader to review and refine.

This illustrates the workflow we intend to develop; the public demo’s simulated workspace is the current visible example.

How we build