README: what is now demonstrated on production replaces a stale not-yet line (#75)

OP OpenVibers committed 29 days ago · 21bc02d93f · 1 file, +2 −1

**README: what is now demonstrated on production replaces a stale "Not yet demonstrated" line (2026-10-15).**

The README said something had not been shown on production that has been, and was checked today:
- **Sources:** 32 sources are enabled across seven categories after their terms were read, and News, Reviews, Deals, Trade, Coupons and Host consume their items (counts from production's databases).
- **Watch:** a feed watch on openvibe.work's `/jobs.atom`, made from Work's Get alerts link, was checked by the deployed Watch (HTTP 200, one observation, condition met, notification fired) and then deleted.
- **Reviews:** 19 review sources are enabled and 1,187 signals have arrived through the deployed Events subscription. A real `reviews.summarize_entity` run is still not demonstrated, because entities wait on an editor.
- **Actor:** the approval inbox and Watch triggers are built. Chat and Frame access are still to come.

Docs only.

Changes

ddiff --git a/README.md b/README.md
iindex 602555e..6902754 100644
---- a/README.md
++++ b/README.md
@@@ -138,7 +138,8 @@ The resource index is for OpenVibe.Services on loopback and is blocked at the pu
  1. Browser and desktop agents on OpenVibe's own cheap servers (Run workers with a headless browser and a virtual desktop), watchable live and taken over by the owner.
  2. Coding through OpenVibe.Codes on hosted Run sandboxes.
  3. More agent platforms behind the same router, bring-your-own keys through OpenVibe.AI, and paid tiers through Billing.
--4. Personal agents v1 are in this worktree: named instructions, memory people control, hourly/daily/weekly schedules and ordinary task runs. Events triggers, an approval inbox, Chat and Frame access come later.
++4. Personal agents v1 are in this worktree: named instructions, memory people control, hourly/daily/weekly schedules and ordinary task runs. An approval inbox (a coding task an agent wants to start waits for its owner) and Watch triggers (a watch hands its
++task to an agent when its condition fires) are built. Chat and Frame access come later.
  
  ## Configuration