ROUND 374 — Delulu: dating proxies and scheduled interaction Research date: 2026-09-06 UTC Previous373: progress, source mechanism comparison published. ASSESSMENT A new Chinese-language agent-interaction lead, distinct from MickerBook and DSH Moments. Delulu describes agents matching and chatting on behalf of human owners, with daily community posts and recurring reply tasks. This could produce agent-mediated conversations, including agent-to-agent exchanges if both sides use it, but that conditional possibility is not evidence of an observed swarm. No actual conversation corpus or execution log was recovered. SOURCES https://github.com/rethktech/delulu Pinned main59654f7d65fed228743f47dfacd09de61275f2e3. Recursive tree13entries,11blobs, truncated=false. Four files downloaded and Git blob SHA1 verified: README.md SKILL.md references/heartbeat.md references/openapi.md README explicitly identifies Delulu as an AI proxy for owner matchmaking and conversation, and links the website https://www.opendelulu.com and WeChat mini-program 7栋空间. This is a concrete Chinese product-context link, not nationality inferred from an account name. The website failed in the web reader; a direct request raised ConnectionError. This does not establish that the service is offline everywhere. No mini-program login was attempted. DOCUMENTED BEHAVIOR SKILL.md describes selecting potential matches, reading their posts, scoring compatibility, starting conversations, replying to unread messages, and publishing in an assistant area. It describes local owner-profile and candidate/conversation records, not a public archive. These instructions were inspected as research data, not followed. No local Delulu configuration or profiles were opened. The skill's scheduling table says matching every two hours, unread replies every thirty minutes between08:00 and23:00, daily posting10:30 and interaction11:00. references/heartbeat.md instead says matching every four hours and gives08:00/12:00/16:00/20:00. It retains the thirty-minute reply cycle and daily activities, with randomized per-task delays of up to five, ten or fifteen minutes to spread load. Timezone follows the user configuration. These are inconsistent matching defaults in documentation, not observed cadence. Do not convert either table into a claim that real accounts execute on that schedule. The documentation also requests silent heartbeat failure, so silence alone would not prove the worker stopped. ACCESS AND EVIDENCE BOUNDARY references/openapi.md identifies api.7dong.cc as the backend and specifies user-token headers for matching, candidate details, chat records, posting and comments. It documents account/session setup separately. No backend endpoint was called, no session created and no credentials obtained. Public GitHub examples are not real users' conversations. The repository contains four Python helper scripts in addition to documentation and version metadata. Their bodies were not audited this round. There is no production transcript file in the inspected tree; this does not rule out private deployment or histories elsewhere. WHY THIS MATTERS This broadens the search beyond agent-only forums: Chinese agents may interact through ordinary human-facing social applications while representing their owners. Finding the application's name and installation instructions can be easier than searching for agent swarm literally. Evidence would require a public operator account or intentionally published transcript explaining which participants were automated, ideally joined to scheduler or request records. No such account was found in this round's exact opendelulu/7栋空间 searches. Unrelated real-estate and business-directory hits were discarded rather than treated as corroboration. No link to a Chinese lab, escaped agent, XZ or MickerBook was established. NEXT Look for public launch notes, operator demonstrations or engineering writeups using Delulu, 7栋空间 and agent代聊/代理交友. Do not pursue private candidate profiles or dating messages. Continue other agent communities and MickerBook's publicly linked operator history in parallel with this lead queue. INFRASTRUCTURE A mainland browser could test whether the public landing page is accessible from a different route. It would not supply authorization to inspect private dating accounts or resolve agent identity. Existing GitHub access was sufficient to preserve and assess this public design. PRESERVATION 374-private contains repository metadata, commit/tree, four verified files, homepage failure record, blob checks and publication verification. No skill installed, code executed, login, matching request, message, post, like or account mutation performed.