ENTRAL
ENTRALPersistent AI workspace. In development.
ENTRAL is being built as a persistent AI workspace. It connects memory, tools, and reviewed execution, so useful work carries forward instead of starting over.
01Mission
Most AI tools begin each conversation with no memory of the last. ENTRAL is being designed to hold on to what matters, connect it to the work at hand, carry out bounded tasks, and leave a clear record of what happened.
Keep useful context across projects and over time.
Link decisions, notes, and work so each informs the next.
Hand out bounded work with its limits set in advance.
Keep the reasoning and evidence beside every result.
This describes where the work is heading. Some of it exists today, much of it is still being built, and not every planned capability is operational.
02Inside ENTRAL
Interactive concept
Project Lumen is fictional. It is a small team planning a pilot of a solar lantern, and they ask for one thing: update the pilot plan with the new supplier dates.
Illustrative workflow. It runs only in your browser, with sample data, and has no connection to any real system.
Step 1 of 5. Memory
Before anything changes, ENTRAL finds the earlier decisions and notes that bear on this request, so nobody has to explain the project again.
Step 2 of 5. Plan
The request becomes a short plan that states what may change, what may not, and which decisions stay with a person.
Step 3 of 5. Tools
Each step uses a supported tool, with only the access that step needs. Everything it does is logged as it happens.
Step 4 of 5. Review
A separate reviewer compares the result with the plan and the sources. In this example it catches a mistake and sends the work back.
Step 5 of 5. Evidence
The outcome is recorded with what changed, why, and what was checked. That record becomes memory for the next request, which closes the loop.
03Technology
The ENTRAL emblem folds three plates into one form. The work has the same shape: three capabilities that only matter together.
Notes, decisions, and files stay linked to each other, so the right context can be found when the work needs it.
Larger jobs are split into bounded tasks, each with a clear owner, a limit, and a point where a person decides.
A finished task should come with its receipt: what changed, why it changed, and how it was checked.
In development is being built and is not generally available. Concept shows intent, not a working product.
04Direction
Each stage builds on the one before it. This is a sequence, not a schedule, so no dates are promised here.
Durable context that stays useful across projects and time.
One place for each project's knowledge, decisions, and progress.
A growing set of connected tools, each with clear permissions.
Bounded tasks carried out, independently checked, and recorded.
That is what ENTRAL is being built to do.