Cluster / protocol-task-exchange
Signed task exchange through a public relay
A saved request and linked result have valid signatures from different keys. Public bot code contains matching task and review templates, but the recorded message type differs from the code example. The exchange is verifiable; the historical configuration and independently controlled agents are not.
Case observations 17 Apr 2026
Unresolved originWhat is observed
- The result references and embeds an identical signed request. Both event identifiers and signatures independently reproduce under different keys.
- The request asks for two timeframes; the result explicitly cannot supply one. A valid signature does not establish task correctness or completion.
- A pinned public bot example contains the task wording and displayed review sentence, with scheduled template selection. Its kind 5100 differs from the signed request’s kind 5050, so the historical execution is not identified.
- The platform supplies a review identifier, but the attempted retrieval did not recover original signed review bytes. Its displayed rating remains platform-indexed evidence.
What remains uncertain
- Signing-key control does not establish distinct operators, autonomous discovery, model execution or an organic swarm.
- The result’s model tag is self-description. Later display profiles are omitted rather than backdated to the exchange.
- The selected timestamps differ by 36 seconds; they are signed source assertions, not measured response latency.
- The bot example’s templates and rating path do not establish that this task ran that source version. No fixed-five-star worker behavior is attributed to it.
- The review retrieval gap is bounded. No payment, financial accuracy, prevalence or presently operating swarm conclusion is made.
Classification
- Coordination origin
- unknown — configured task-marketplace explanation supported; historical initiation unresolved
- Runtime origin
- Distinct signing keys are verified. The result’s model tag is self-description; model execution and independent operators are not authenticated.
- Venue authorization
- Publicly retrievable protocol messages and published source describe a task marketplace; this does not verify every participant’s permissions or a payment.
- Confidence
- High confidence in the reproduced message-to-key validation and exact request/result linkage; historical deployment, runtime and operator attribution remain unresolved.
- Evidence dates
- 2026-04-17 to 2026-04-17
These are the signed timestamps in the selected request and result. The September 6 retrieval and dates in repository history are separate. They do not measure response time or show continuous activity.
Evidence notes
The notes below connect observations to saved sources. Full captures remain private. File checksums identify the originals; they do not verify who produced them.
protocol-signed-request
Case observations 17 Apr 2026
A signed kind 5050 task requests analysis at two timeframes. Its canonical event identifier and signature validate. Its signed timestamp is April 17, 2026 at 12:39:59 UTC; this is a source assertion, not an independently observed launch time.
protocol-signed-result
Case observations 17 Apr 2026
A result under another signing key references and embeds the exact signed request. Its signature validates; it explicitly lacks one requested timeframe. The model tag names gemma4:e2b, a signed self-description rather than proof of that model running. Its signed timestamp is 12:40:35 UTC: a 36-second timestamp difference, not measured response latency.
protocol-template-context
Case observations 17 Apr 2026
The pinned bot example contains the task wording and the platform-displayed review sentence in preset pools, and schedules requests when configured. Its rating logic and review-wording selection are separate steps. This example emits kind 5100, while the signed request is kind 5050; the match does not establish the historical deployment or who operated it.
External source / venue ↗ (may have changed)
protocol-indexed-review
Case observations 17 Apr 2026
The platform index assigns a review identifier to this request and displays a positive review. This is platform-indexed attribution: the index omits the original signed review fields needed to verify it. The rating does not establish task completeness, accuracy or payment.
External source / venue ↗ (may have changed)
protocol-review-query-limit
Case observations 17 Apr 2026
This exact-identifier query ended without returning the signed review. It bounds this retrieval attempt only; it neither authenticates nor disproves the review and does not establish absence elsewhere.
External references
Cases sit around the edge. Rings show categories. Marks connect cases to categories; they do not measure evidence strength. Blank spaces do not establish absence.
Signed task exchange through a public relay
Case observations: 17 Apr 2026A saved request and linked result have valid signatures from different keys. Public bot code contains matching task and review templates, but the recorded message type differs from the code example. The exchange is verifiable; the historical configuration and independently controlled agents are not.
Connections show which cases this analysis uses. They do not establish that cases share participants.
These dates cover the observations included for each case. They do not show when a method began or establish continuous activity.
Case index and observation dates
- Agents sharing answers and timing on public wikisCase observations: 16 Jun 2026 to 21 Jun 202612 source notes
- Answer requests, acknowledgment and relay on a public paste serviceCase observations: 16 Jun 20267 source notes
- Opaque “fleet” envelopes on two wikisCase observations: 30 Aug 20263 source notes
- Invitations and collaboration after public reportingCase observations: 4 Sep 20265 source notes
- A later test marker in the same sandboxCase observations: 4 Sep 20261 source note
- Disclosed agent-related editing of public knowledgeCase observations: 19 Aug 2026 to 31 Aug 20268 source notes
- A concealed hostname in a later wiki editCase observations: 4 Sep 20263 source notes
- Draft review under disclosed human directionCase observations: 12 Feb 2026 to 13 Feb 20264 source notes
- Agent-attributed code review, revision and disagreementCase observations: 21 Aug 2026 to 26 Aug 20267 source notes
- Signed task exchange through a public relayCase observations: 17 Apr 20265 source notes
- Monitoring design refined through public critiqueCase observations: 10 Aug 20266 source notes
- Design briefs cross language boundariesCase observations: 8 Feb 20265 source notes
- Participants negotiate comment normsCase observations: 3 Feb 2026 to 17 Feb 202611 source notes
- Peer checking loses the target, then corrects itCase observations: 27 Nov 20257 source notes
- Three threads become a proposed memory methodCase observations: 17 Feb 20267 source notes
- Critiques reshape a collaborative specificationCase observations: 2 Feb 202613 source notes
- A prescribed guide appears in platform documentationCase observations: 13 Feb 20265 source notes
- Outside test cases lead to a reported verifier correctionCase observations: 26 Jul 2026 to 27 Jul 20266 source notes
- Human review guides a selectively revised Japanese glossaryCase observations: 9 Jun 2026 to 1 Sep 20267 source notes
- Task feedback and differing service diagnosesCase observations: 5 Feb 2026 to 6 Feb 20268 source notes
- Repairing the service used to read commentsCase observations: 1 Feb 2026 to 2 Feb 20267 source notes
- Participants pick up unfinished Gemma testsCase observations: 8 Jun 2026 to 10 Jun 20268 source notes
- A Bluesky question becomes an articleCase observations: 11 Mar 2026 to 12 Mar 20268 source notes
- A lobster drawing invitation receives replies and matching pixelsCase observations: 31 Jan 2026 to 10 Feb 20266 source notes
- A SpaceMolt battle prompts corrections to its public accountCase observations: 25 Aug 2026 to 28 Aug 20269 source notes
- A Bluesky directory acknowledgment becomes an articleCase observations: 8 Mar 2026 to 11 Mar 20268 source notes
This case in the record
Communication methods in this case
- Signed event references across task exchanges 5 supporting source notes
Clusters, swarms and relationships
A request and result linked across signing keysIndividual, model and task behaviors
Valid messages with incomplete task coverageReconstructed timelines
Signed event times with a separate retrieval dateConnections and open questions
A request and result linked across signing keys
Two validated protocol messages establish a specific request/result relationship. The relationship is between signing keys; its operator and runtime origins remain unresolved.
Case observations 17 Apr 2026
Earliest linked event: 17 Apr 2026
What these dates refer to
Case dates describe the surrounding activity. Linked events may include earlier context; neither label establishes when this behavior first appeared. Ranges do not show continuous activity between those dates.
· signed-request-timestamp
Signed created_at source assertion; not independently observed launch · second as declared; clock accuracy unknown
Read the dated evidence ↗- What historical configuration connects the selected request key and kind 5050 message to an initiating task?
Valid messages with incomplete task coverage
The signed result explicitly omits one requested timeframe. A displayed positive review has a separate, weaker basis for attribution. Neither establishes task completion.
Case observations 17 Apr 2026
Earliest linked event: 17 Apr 2026
What these dates refer to
Case dates describe the surrounding activity. Linked events may include earlier context; neither label establishes when this behavior first appeared. Ranges do not show continuous activity between those dates.
· signed-request-timestamp
Signed created_at source assertion; not independently observed launch · second as declared; clock accuracy unknown
Read the dated evidence ↗- Can the original signed review be recovered, and would its content address the missing requested coverage?
Signed event references across task exchanges
References in signed messages connect requests, results and task feedback. Evidence of preset templates applies to the protocol-task-exchange case only.
Case observations 5 Feb 2026 – 17 Apr 2026
Earliest linked event: 5 Feb 2026
What these dates refer to
Case dates describe the surrounding activity. Linked events may include earlier context; neither label establishes when this behavior first appeared. Ranges do not show continuous activity between those dates.
- 5 Feb 2026 – 6 Feb 2026 · Task feedback and differing service diagnoses
- 17 Apr 2026 · Signed task exchange through a public relay
· public-task
Signed event created_at assertion; not observed receipt · second as declared; clock accuracy unknown
Read the dated evidence ↗- Which historical protocol configuration explains the request-kind difference?
Signed event times with a separate retrieval date
The request and result declare April 17 timestamps 36 seconds apart. These signed source clocks do not measure response latency; September 6 retrieval is a separate event.
Case observations 17 Apr 2026
Earliest linked event: 17 Apr 2026
What these dates refer to
Case dates describe the surrounding activity. Linked events may include earlier context; neither label establishes when this behavior first appeared. Ranges do not show continuous activity between those dates.
· signed-request-timestamp
Signed created_at source assertion; not independently observed launch · second as declared; clock accuracy unknown
Read the dated evidence ↗- What independent historical execution evidence could constrain the source-declared times?