EolSpace · a system for working with AI

AI work. Decisions with grounds.

We are building EolSpace for teams creating products with AI: see what is ready for the next step, on what grounds, and what changed after a decision.

For independent developers and small teams.

01020304050607
Static cycle
  1. 01INTENT
  2. 02WORK
  3. 03EVIDENCE
  4. 04PERMISSION
  5. 05OUTCOME
  6. 06VERSION
  7. 07CONTINUATION

ONE CHANGE — ALL THE CONTEXT

One change. The grounds for a decision.

A client portal is being prepared for a wider pilot. See how work, checks and observations change the team’s decision.

Interactive example of a future workflow · synthetic data
EolSpace / Project cabinetEXAMPLE
Client portalCan access be expanded?

Give clients access to their own materials and reports while retaining control over access.

Pilot pausedv1

Access expansion deferred

The prepared scenario showed access after role revocation. The original stop rule applied.

Isolated pilot · synthetic data. Expansion requires a separate decision.

Select a condition to trace its evidence

Initial boundaryIf access persists after a role is revoked, the person responsible pauses the pilot and expansion until the grounds are reviewed.

02Mobile view

EolSpaceEXAMPLE
Client portalv1
Access changes

Access expansion deferred

A user with a revoked role still received material in an open session. The person responsible paused the pilot.

What to check next

Before resuming, check this case in the corrected version.

Example AI explanation

The new sign-in check did not cover an already open session. Check how the role change applies to the next request.

Example check reportv1
  1. v1 · control clients: materials separated

  2. v1 · open session after role revocation: material received

  3. v1 · report: comparison with control dataset passed

Person responsible · v1 pilot and expansion paused under the original rule.

Evidence, permission and outcome

Does access stop after a role is revoked?
v1 · open session after role revocation: material received

Work
Team + AI · v1 prepared.
Check
v1 checks · control clients, new sign-in and control report. The open session is outside scope.
Permission
Person responsible · v1 pilot and expansion paused under the original rule.
Observed outcome
Prepared v1 observation · an open session received material after role revocation.
History from the beginningIntent, work and decisions — in six events
IntentGive clients access to their own materials and reports while retaining control over access.
Initial boundary

If access persists after a role is revoked, the person responsible pauses the pilot and expansion until the grounds are reviewed.

  1. Owner · v1
    The owner defined the goal and selected conditions. The person responsible decides on access.

  2. Team + AI · v1
    The team prepared v1 with AI assistance. The agent does not decide on admission.

  3. Prepared check · v1
    Control clients and the report were checked; role revocation was checked only for a new sign-in.

  4. Person responsible · v1
    Only an isolated pilot is permitted. The open session has not yet been checked.

  5. Prepared observation · v1
    The prepared scenario showed access after role revocation. The original stop rule applied.

  6. Team + AI · v2
    Initially, v2 was prepared without new evidence. Below are the subsequent checks, a separate decision by the person responsible and the outcome of the repeated pilot.

    1. Team + AI · v2

      Team + AI · v2 fix prepared.

    2. Prepared check · v2

      New v2 checks · control client separation; revocation for new sign-in and open session; report against the control dataset.

    3. Person responsible · v2

      Person responsible · after new checks, a repeated isolated v2 pilot is permitted. General launch is not permitted.

    4. Prepared observation · v2

      Prepared v2 observation · in the repeated pilot, the next request with a revoked role received no material.

EVERYDAY VALUE

Keep your project in view

EolSpace is designed to keep the goal, evidence and decision history together as work continues.

01

State and history

The cabinet brings together your projects, selected objects, access and settings. See what is established for the current version, where something failed and what needs a new check.

02

Notifications with a reason

You choose what to observe and within which limits. A significant change points to the affected object and explains why it needs attention.

03

A useful next step

AI is intended to help explain changes and propose an action linked to its grounds. Decisions remain within defined authority.

Your project, close at hand.

In the intended system, a cabinet and client apps give access to project state, important changes and decision history from a computer or phone.

Client directions in development.

Browser · Windows · Linux · Android · iPhone

Platform status

ECOSYSTEM / WHAT WE ARE BUILDING

Different tools. One coherent work history.

Contributors and methods of checking may change. EolSpace connects their work to your goal, the grounds for decisions and observed outcomes.

01
Purpose and authority

People

The owner defined the goal and selected conditions. The person responsible decides on access.

02
Work product

Contributors

The team prepared v1 with AI assistance. The agent does not decide on admission.

03
Specific evidence

Checks and assessments

Checks establish specific properties of a version. JEV is a bounded tool for interpreting meaning.

EolSpace

Connects goals, work, evidence, decisions and outcomes. Shows version state and preserves unknowns.

v1Observed outcomev2

New checks → decision by the person responsible → observation in the repeated pilot. General launch is still not permitted.

AVAILABLE TODAY

What you can open today

These are separate public tools and references, not the full EolSpace cycle in production.

Local records

Create and verify Records in your browser. Data stays on this device.

Open Records

Documentation

The public Wiki explains approaches and evidence limits.

Read the Wiki

Tools and access

See the exact status of the browser tool, technical example and closed pilot.

How to start

Quick answers

Who is EolSpace for?

Independent developers and small teams creating and maintaining AI projects who want to understand the grounds for their decisions.

What can I watch?

The intended system lets you choose projects and objects and set observation limits. Each conclusion should show its version, time, grounds and remaining unknowns.

What does a change notification mean?

It identifies an event, the affected object and why it matters. An explanation can suggest a next step, but is neither a new check nor permission to act.

Where will EolSpace run?

The plan includes a browser cabinet, Windows, Linux GUI and CLI, Android and iPhone. Public local Records differ from the closed-pilot cabinet. See Access for each platform’s status.

What happens to my data?

Local Records stay in your browser and support export and import. Transfer, retention, portability and recovery rules for a future cabinet are separate; its data must not be assumed to stay only on your device.

How do I start, and is there a paid offer?

You can open Records, the technical example and Wiki. Commercial access terms are still being defined. A channel for project enquiries has not yet been confirmed.

NEXT STEP

EolSpace access status

For developers and small teams that want to retain the grounds for decisions, notice changes in selected parts of a project and continue without rebuilding context from scratch.

A public channel for project enquiries has not yet been confirmed. For now, explore the example and the scope of Care.

Explore Care