START / 03 PATHS

Start where preserving context fits your work.

This page separates public tools, the closed pilot and planned clients. The project cabinet is distinct from local Records.

Create in browserView an example

ACCESS STATUS

What is available now

Each path has its own boundary. A closed pilot is not presented as a public release.

PlatformStatusWhat it means
Browser / websiteAvailablePublic pages and the example work in a browser; this is not a login to the full cabinet.
EolSpace cabinetClosed pilotProject state and history are intended for invited participants; general access is not open.
Local RecordsAvailableSelf-authored records stay in your browser; this separate tool is not the full cabinet.
Windows appPlannedNo public build or update channel has been confirmed.
Linux GUIPlannedThe graphical client is distinct from the CLI; no public build is confirmed.
Linux CLIClosed pilotA limited eol CLI for invited participants; the cabinet provides its install command.
Android / EolSpacePlannedA separate Records debug APK was checked locally; no public EolSpace Android client build or channel is confirmed.
iPhone / iOSPlannedNo public build, signing or installation channel has been confirmed.

Choose the result you need

The formats are not interchangeable. Start with the job you need to complete.

  1. Create and keep a record

    Runs in the browser, keeps a device-local library, and exports JSON or TXT.

    Open workspace

  2. Connect a project

    The eol CLI runs your checks on this machine and sends evidence to the closed pilot cabinet.

    How to install eol

  3. Review Records for Android

    A separate local Records debug APK can be reviewed in an authorised setting; it is not the EolSpace client.

    Records APK conditions

CLI / EOL

Install from the pilot cabinet

You need Linux x86_64, Python 3.12 or 3.14, and a Git project with unittest tests or the Node 24 profile with node:test. The pilot cabinet gives you the install command after an invitation: it checks the package SHA-256 itself and puts eol in ~/eol-cli.

  1. An invitation is required

    The pilot requires an invitation. External participant access is not open yet; there is no public joining route.

  2. Install eol from the cabinet

    The cabinet shows one command: it checks the package and puts eol in ~/eol-cli; the previous version stays alongside.

  3. Run it in the project folder

    Replace ~/my-app with your Git project folder. Three answers: your promise in one sentence, APPROVE, y. In the cabinet this command already carries the cabinet address and language.

    cd ~/my-app && ~/eol-cli/bin/eol start

  4. Accept the baseline in the cabinet

    Once evidence is sent, eol names the cabinet address: confirm the promise and accept the baseline there.

Read the result

Every eol stop ends with a next: line naming the command to type next. The first run writes the promise card into contracts/ and asks for a commit; the next run connects the cabinet with an 8-character code, runs the chosen checks, and sends evidence.

If a command fails

  • This folder is not a Git repository: eol needs the folder of an existing project with Git and unittest tests, not a new empty one. Go there and run eol start again.
  • Uncommitted changes: git status --short lists the files. Commit or stash them with your Git tool, then run eol start again.
  • No cabinet address: next: eol start --server https://<cabinet host>. The command from the cabinet already carries that address.

Which format goes where

A .json filename does not identify its contract.

FormatPurposeOpen with
Browser evidence packeol.demo-evidence-pack/1Up to 2 MiB / 500 records; creation, import, and local library.Workspace / demo
Evidence cycleevidence-cell.manifest/1 + evidence-cell.record/1Manifest and hash-chained records for local judgement.evidence-attestation validate
Attestation statementin-toto Statement v1 · predicate v0.1/v0.2Unsigned self-assessment bound to a commit and cycle.evidence-attestation verify

Careproof passports and release attestations have separate verifiers. None of these formats alone proves authorship or truth of intent.

ANDROID / REVIEW STATUS

Records for Android: local debug candidate

The separate Records APK passed local runtime checks on Android 16 / API 36. It is not the EolSpace client, a production signature, a store release, or a promise of compatibility with every device.

There is no public URL: publisher identity, production signing, and an update channel remain undecided. That is why this page has no download action.

APK
eol-records-0.2.0-debug.apk
Package
space.eolai.records.debug
Version
0.2.0-debug · versionCode 2
Android
min API 26 · target API 35
WebView
111 or newer
SHA-256
4b173f2cd15d1b4a92968ef7d8f433088bd37c40fabcdd7456af643ab0cd1507

How an authorized reviewer checks it

  1. Receive the APK through an approved local review channel and check the exact filename.
  2. Run the SHA-256 check below before installation.
  3. Confirm Android 8.0+ and Android System WebView 111+, then install the debug APK only in the allowed environment.
  4. Export important records before moving to a future production ID: a different applicationId will not update the debug app in place.
python3 -c "import hashlib,pathlib,sys; p=pathlib.Path('eol-records-0.2.0-debug.apk'); p.is_file() or sys.exit('File not found: ' + str(p)); actual=hashlib.file_digest(p.open('rb'),'sha256').hexdigest(); expected='4b173f2cd15d1b4a92968ef7d8f433088bd37c40fabcdd7456af643ab0cd1507'; print('SHA-256 OK') if actual == expected else sys.exit('SHA-256 mismatch: ' + actual)"

NEXT / NO INVENTED TERMS

The utility is visible. The commercial channel is still undecided.

Browser Records preserves context and checks record integrity.

The separate evidence-attestation CLI judges evidence cycles.

Project-check comparisons belong to Cabinet and the eol CLI; for now this is a closed, invitation-only pilot.

Tariff, payment, publisher, and public distribution channel are not established. We do not hide that boundary behind an inactive button.

Create a first record