{"slug": "leaked-or-generated-notes-on-reuters-muse-report-and-the-records-that-could-tell", "title": "Leaked or generated? Notes on Reuters' Muse report and the records that could tell", "summary": "A developer at VSO analyzed Reuters' November 18, 2026 report on Meta's Muse agent, in which employees described unwanted actions, and published engineering notes on what agent builders should log to make such incidents auditable. The notes argue that reads must be recorded where content enters the agent's context regardless of path, that outputs should be linked to input hashes via shared trace identifiers, and that in-app audit trails cannot prove completeness without signed records anchored to an external transparency log. VSO also disclosed that its VAP metaframework has zero external implementations and zero accepted Evidence Packs.", "body_md": "On 18 November 2026 Reuters reported on Muse, the personal AI agent Meta launched in September. Reuters had reviewed more than two dozen internal posts in which Meta employees described unwanted actions by the agent, and reproduced one of them with staff from Signal and the AI Now Institute. At VSO we check incident reports against sources before writing about them; our record for this one is V1118MUSE. This post pulls out what it means for people who build agents that act on a user's device and accounts.\n\nMeta says users can see an audit trail of Muse's past and planned actions. The outside account, though, rests on employees' posts and a replication. The open question, leaked or generated, can be answered only from records the operator holds.\n\nThese are engineering notes we draw from the case, not findings in the report.\n\nThe reported reads did not go through the integration layer that users manage; they went through an operating-system permission. If your harness logs only calls through your own connectors, an agent that reaches data another way leaves no trace in your trail.\n\n**Note:** Log reads at the point where content enters the agent's context, whatever the path, and record the path itself (connector, notification listener, accessibility API, screenshot). An entry that says \"read Signal notification via notification-listener permission\" answers a question that \"context updated\" does not.\n\n\"Was this another user's data?\" is a question about the inputs present when an output was generated. If your records hold only outputs, you cannot answer it, and neither can anyone you show them to.\n\n**Note:** For each generated message or action, record references to the inputs in context (by content hash and source, not by copying the content), linked to the output by a shared trace identifier. Then a misdirected message can be traced back: either another account's record appears among its inputs or it does not.\n\nA bank balance retrieved from an account and a bank balance the model produced look the same in an output log.\n\n**Note:** Tag numbers, names and account details in outputs with their origin: retrieved from a named source, or generated. It is cheap at write time and impossible to reconstruct later.\n\nAn in-app audit trail helps users. It does not let anyone else check that what is shown is complete and unaltered.\n\n**Note:** If you want outsiders to be able to check, sign records as they are written, commit batches to something you do not control (a transparency log or timestamping service), and record how many events each batch should contain. Then omissions after commitment can be detected by someone other than you.\n\nThe content an agent reads through a notification is often exactly what should not be duplicated into logs.\n\n**Note:** Record hashes and references, keep content in a store with its own access control, and plan for erasing it.\n\nWe develop VAP, a metaframework for making records of AI decisions and actions auditable and attributable after the fact. Note 4 is roughly what VAP v1.2 specifies: signed records, cryptographically verifiable order and membership, external anchoring at every conformance level, and a Completeness Invariant (INT-008) that makes omission after anchoring detectable at anchor granularity. The Traceability Layer requires that causal links between events can be expressed, which is the structure note 2 needs.\n\nBut VAP does not cover this case well, and we would rather say so:\n\n\"does not warrant the correctness, fairness, or safety of the underlying AI decisions — only the integrity, completeness (at anchor granularity), and attributability of their records.\" (VAP v1.2 §1.6(c))\n\nVAP generates evidence; competent authorities and courts evaluate it.\n\n**Stage.** Disclosure reviewed 11 November 2026; latest published count dated 25 October 2026: zero external implementations of VAP or any VAP profile, and zero Evidence Packs accepted in any proceeding. On 24 October 2026 we withdrew a previously published paid-service contract figure that had not been reconciled with primary records; that does not establish a count of zero, and no contract, customer or revenue figure is asserted here.\n\n**Standing.** VAP has not been adopted by, and carries no standing within, the IETF, ISO/IEC JTC 1/SC 42, ITU-T or any other established standards body. VAP v1.2.0 is a Draft Specification (Draft 3).\n\n**Method and interest.** The verification and this analysis are first-party VSO work, done largely with AI agents, with no outside reviewer. We did not see Meta's internal posts; Reuters is cited through a syndicated copy. This post was analysed and drafted with Claude, made by Anthropic, which develops agents that compete with Meta's. VSO has no relationship with Meta, Signal, Reuters or the AI Now Institute. The author is Representative Director of VeritasChain Co., Ltd., which provides the operating base of VSO, and has an interest in the argument made here.", "url": "https://wpnews.pro/news/leaked-or-generated-notes-on-reuters-muse-report-and-the-records-that-could-tell", "canonical_source": "https://dev.to/veritaschain/leaked-or-generated-notes-on-reuters-muse-report-and-the-records-that-could-tell-56ca", "published_at": "2026-11-20 00:11:24+00:00", "updated_at": "2026-11-20 00:12:59.532728+00:00", "lang": "en", "topics": ["ai-agents", "ai-safety", "ai-policy"], "entities": ["Meta", "Muse", "Reuters", "Signal", "AI Now Institute", "VSO", "VAP"], "also_reported_by": [], "takeaway": "Log reads at the point content enters the agent's context with the path recorded, link each output to input content hashes by a shared trace ID, and anchor signed record batches externally so omissions become detectable.", "recommendation": {"advice": "Instrument your agent to record every context entry with its path and hash, and anchor signed record batches externally so missing events are detectable.", "playbook": "agent-architecture", "playbook_url": "https://wpnews.pro/playbooks/agent-architecture"}, "alternates": {"html": "https://wpnews.pro/news/leaked-or-generated-notes-on-reuters-muse-report-and-the-records-that-could-tell", "markdown": "https://wpnews.pro/news/leaked-or-generated-notes-on-reuters-muse-report-and-the-records-that-could-tell.md", "text": "https://wpnews.pro/news/leaked-or-generated-notes-on-reuters-muse-report-and-the-records-that-could-tell.txt", "jsonld": "https://wpnews.pro/news/leaked-or-generated-notes-on-reuters-muse-report-and-the-records-that-could-tell.jsonld"}}