A map needs a next step

The first run had read two connected mailboxes and local coding sessions. It had saved more than three thousand mail bodies privately and mapped people, projects and skills. When we opened three of those mapped pages on a phone, the first screen made the run look less useful than it was.

The Person page showed a last-contact date. The Skill page showed recorded usage. The Project page put a local filesystem path in the largest type on the screen. The path was already in Facts. In all three, the command that would turn metadata into a source-backed memory sat below an 812px viewport. A user had to scroll past secondary context to learn what to do next.

We moved the mapped-page investigate action directly below the lead. The Project lead now states the observed session count and the limit of the map: the project's purpose and current state have not been investigated. The path remains in Facts and the full note, where it helps someone inspect the source. We also gave the phone's privacy action a full touch target inside the open Browse menu. It now keeps keyboard focus when its label changes, so Enter can hide and Space can immediately show again.

An independent AI review of the same frozen, private notebook measured the three phone copy buttons below the fold before the change. In the candidate, their 44px targets ended at y636, y735 and y682. The Project no longer opened on the path. We checked desktop and phone, navigation, Full memory, privacy, overflow and browser errors. The review covered a small sample of mapped pages. A separate model run is still needed to judge whether their eventual memories contain useful, well-supported findings.

Read the a29 preview notes for the exact install pin and trial limits, or explore co rem with an invented sample notebook.