# ConnectOnion 1.9.0a22 (preview)

New to REM? [Start a five-day first run](#install-this-preview) before opening
the reader.

## Reader and source checks

REM project pages now put a supported current finding first when one exists;
otherwise they lead with the sourced project purpose and say current work is
unconfirmed by the supplied session sample. The summary stays fully visible
on phones, and a partial
session-history pass says how many inputs were supplied. The reader uses a
plain placeholder when labelled passages fill an entire card, and project
status is visible beside the sticky name on a phone.

Project investigations can read the fixed, bounded repository source index
supplied by co rem. Their writing instructions require a distinctive link
between a coding-session request and this project; a shared working directory
or a generic release request does not establish one. When an explicit
investigation accepts a page, it privately retains only the live coding
inputs that page cites, so their originals can be opened even if an older map
had not archived them.

Each numbered row in **Sources** opens its own source dialog, including members
of a grouped citation. The dialog shows the retained original when available
and says when it is unavailable. Repository dialogs show up to 65,536 characters
of a retained source, with truncation marked. The source dialog still describes
an excerpt, not a validated claim span or proof of a test or deployment.
Cited mail bodies now show up to 4,096 characters so a reply request near the
end of a message can be checked; retained coding inputs use the same bound.
Hiding a labelled sentence also hides its
trailing punctuation.

A project page can no longer cite the generated candidate-file inventory or
the collector's coverage note as original evidence. A fact about files needs a
retained repository snapshot. Private trials exposed both gaps before
validation changed.
They also showed that a short unnamed follow-up can be gathered without an
earlier input that names a different product in the same session. Project
writing rules now leave such follow-ups unassigned unless supplied evidence
links them to the project. A source-code comment reporting tests is described
as a dated note, rather than an independently verified run.
The project collector also withholds unnamed follow-ups after an earlier user
input in the same coding session used another project folder. It reports how
many it withheld, so a shared working directory cannot silently make those
short lines evidence for this project. This deliberately leaves some current
work unknown when the session has no explicit project cue.
When no session input can be assigned, the writer and candidate check keep
`Insight` and `Open threads` Unknown. A dated repository note may still appear
as history, but cannot become a current finding. The reader shows zero supplied
inputs alongside the archived workspace count.
The [claim-to-source follow-up](https://github.com/openonion/connectonion/issues/2195)
tracks the evidence-selection boundary and broader fresh-page recheck.

## Skills source checks

Skill pages now cite retained run pieces and instruction snapshots. The reader
shows up to 4,096 characters of a cited run piece and 16,384 characters of a
cited instruction, with truncation marked. A new accepted investigation can
expand an older short instruction excerpt only when the source content hash is
unchanged. Validation rejects mutable run-summary and carried-page citations
as original evidence. Documented Skill behavior remains distinct from observed
execution.

## First-run trial and limits

An isolated 730-day metadata-only map completed in 989 seconds and found 382
person pages, with 326 still queued for investigation. Two sampled full person
pages were accepted; this does not verify every person or make the full first
run affordable. The default discovery window remains 90 days while
[#2176](https://github.com/openonion/connectonion/issues/2176) tracks
resumable historical coverage and a practical cost path.

## Install this preview

For a new notebook, pin this opt-in preview, connect a mailbox if you want
mail memories (`co auth google` or `co auth microsoft`), then investigate a
five-day sample before opening the reader:

```bash
python -m pip install --upgrade 'connectonion==1.9.0a22'
co auth google  # optional
co rem init --days 5
co rem open
```

If you already have a notebook and only want to read it, `co rem open` is
enough. See the [full first-run path](/rem#start) for source and schedule
choices.

## Independent review

The [independent AI founder/UI review](/evidence/v1.9.0a22)
records the actual sampled page types and interaction states, evidence,
remaining gaps and rechecks. The reviewer was an AI in that role, not a human
founder. Notebook screenshots use invented content; documentation screenshots
show public pages.

Stable remains **1.8.10**. This release is an opt-in alpha.