STARLO OSDownload upon request
EVIDENCE DESK 1.0 / PRIVATE ALPHA

From a claim
to something checkable.

This release adds an evidence workflow to the existing StarloOS runtime. It is not a bootable OS, a financial advisory service, or an activated token economy.

1. Use it immediately in your browser

Create a research file, add a public source URL, paste a snapshot, and add another snapshot when that source changes. Quotes and changes are computed locally. Files are stored in this browser's IndexedDB, not synchronized or secretly uploaded. Browser data can be cleared; export what you need. The example contains fictional Atlas Protocol data.

2. Review the evidence

Keep source assertions, inferences and open questions separate. Quote matching checks literal presence in a saved snapshot, not truth. Accept or reject each assertion with a note. A final acceptance requires current source snapshots, your chosen source/freshness thresholds and explicit human acknowledgment. Editing the evidence invalidates prior final acceptance.

3. Connect for public-page collection

Use an authenticated local runtime or configure the hosted private workspace's storage and owner password. Existing credentials and invite codes work. Approve each exact HTTPS URL. The reader respects robots rules, rejects private IP ranges, pins DNS results, enforces bounded response sizes, refuses cross-origin redirects in this research workflow, and never executes page scripts. JavaScript-only and logged-in sites may not be readable. The source receives a server request. Never put private tokens in a source URL.

4. Optional AI synthesis

A model connection and internal credit allocation are required. You explicitly approve sending the question, saved instructions and bounded source excerpts. At most six sources and 850 characters per source are included. The existing four-specialist workflow requests brief.md, sources.csv and unknowns.md; it does not establish factual truth or automatically pass the final human review. Run progress and approvals are in Command center → Missions. A local worker can advance jobs; cloud jobs require the open command center or a separately configured dispatcher.

5. Cost visibility

Deterministic evidence processing makes no model call. Hosting and storage still have costs that this view does not meter. Optional model missions expose actual returned token counts and internally charged / reserved credits. Those credits are neither STARLO tokens nor a verified provider dollar invoice. Your model provider bills your account.

6. Export and verification

Export brief.md, source and claim CSV files, evidence.json, execution.json and a SHA-256 manifest. The JSON companion can be verified in the browser for matching content hashes. Optional server signing uses an operator-configured Ed25519 private key. Use the included offline verifier and a separately authenticated public-key fingerprint to establish signer trust. An embedded key alone proves no identity; a signature proves no fact or financial safety.

7. Limits and release status

Private pilot limits: 20 research files per storage location, 8 sources per file, 6 snapshots per source, 12,000 characters per snapshot, 60 claims and an 800 KB research-file limit. Histories are not automatically purged to fit: export and remove unreferenced material. Activity events retain the most recent 160 with a truncation flag. Files are private to an authenticated workspace but this is not a team collaboration, immutable audit, or production security certification.

Token payment settlement, live trading links, public contract address and native installer validation are not activated by this release. The download button remains an availability notice and collects no requests.

Open Evidence Desk ↗Full release status ↗

Verification scope

Read this edition’s actual test scope and limits →