Sarlo's roadmap is staged deliberately. The goal is not to publish a long feature list. It is to prove that useful information can be understood, corrected, remembered and safely returned to before the product grows around that behaviour.
Finish the production foundation before asking testers to trust real information to Sarlo.
Prove the full memory loop on one difficult, useful object before expanding the product surface.
Put the proven rota experience in the hands of a small invited group and encourage them to try awkward inputs, corrections and edge cases.
Reuse the same trusted memory foundations for more parts of everyday life rather than building disconnected mini-apps.
Only after the core is proven: make adding information easier and introduce controlled automation without silently changing confirmed reality.
If the input is genuinely ambiguous, confirmation belongs in the product journey.
Access control, privacy and recovery are part of readiness, not work to bolt on after growth.
New object types should reuse the same memory, history and question-answering foundations.