Select a case
Open a numbered case or use the case index below to read its evidence.
Observation dates
When the recorded activity happened
These dates come from saved evidence. The record does not track activity continuously. Events close together in time may involve different participants.
26 CASES / 176 SOURCE NOTESPOSITION = EARLIEST INCLUDED OBSERVATION MONTH
← Scroll horizontally to see the full chart →
Center / one case Small dot / one source note Line / method assigned to a caseOutline / visual grouping only
Case index and monthly counts
- Peer checking loses the target, then corrects it · 2025-11-27 · 7 source notes
- A lobster drawing invitation receives replies and matching pixels · 2026-01-31 · 6 source notes
- Repairing the service used to read comments · 2026-02-01 · 7 source notes
- Critiques reshape a collaborative specification · 2026-02-02 · 13 source notes
- Participants negotiate comment norms · 2026-02-03 · 11 source notes
- Task feedback and differing service diagnoses · 2026-02-05 · 8 source notes
- Design briefs cross language boundaries · 2026-02-08 · 5 source notes
- Draft review under disclosed human direction · 2026-02-12 · 4 source notes
- A prescribed guide appears in platform documentation · 2026-02-13 · 5 source notes
- Three threads become a proposed memory method · 2026-02-17 · 7 source notes
- A Bluesky directory acknowledgment becomes an article · 2026-03-08 · 8 source notes
- A Bluesky question becomes an article · 2026-03-11 · 8 source notes
- Signed task exchange through a public relay · 2026-04-17 · 5 source notes
- Participants pick up unfinished Gemma tests · 2026-06-08 · 8 source notes
- Human review guides a selectively revised Japanese glossary · 2026-06-09 · 7 source notes
- Answer requests, acknowledgment and relay on a public paste service · 2026-06-16 · 7 source notes
- Agents sharing answers and timing on public wikis · 2026-06-16 · 12 source notes
- Outside test cases lead to a reported verifier correction · 2026-07-26 · 6 source notes
- Monitoring design refined through public critique · 2026-08-10 · 6 source notes
- Disclosed agent-related editing of public knowledge · 2026-08-19 · 8 source notes
- Agent-attributed code review, revision and disagreement · 2026-08-21 · 7 source notes
- A SpaceMolt battle prompts corrections to its public account · 2026-08-25 · 9 source notes
- Opaque “fleet” envelopes on two wikis · 2026-08-30 · 3 source notes
- Invitations and collaboration after public reporting · 2026-09-04 · 5 source notes
- A concealed hostname in a later wiki edit · 2026-09-04 · 3 source notes
- A later test marker in the same sandbox · 2026-09-04 · 1 source note
| Month | Cases |
|---|---|
| 2025-11 | 1 |
| 2025-12 | 0 |
| 2026-01 | 1 |
| 2026-02 | 8 |
| 2026-03 | 2 |
| 2026-04 | 1 |
| 2026-05 | 0 |
| 2026-06 | 4 |
| 2026-07 | 1 |
| 2026-08 | 5 |
| 2026-09 | 3 |
Events and additions to the observatory
Event dates describe the source account. Observatory addition dates describe when a case entered this record. An addition does not establish recent activity. The line joins two date labels for the same case; its length does not measure elapsed time. Counts describe documented cases, not the number of agents or their activity.
Repairing the service used to read comments
Event date: 2026-02-01 to 2026-02-02
Added to the observatory: 2026-09-07
Date basis and limits
Date basis: Source-represented event dates, not continuous observation. First appearance among the pinned pre-overnight edition and the five held overnight release manifests; September 7 is publication in this observatory, not first global discovery.
Event date scope: The selected request, code changes and replies carry February 1–2, 2026 source timestamps. An earlier January 31 endpoint is background context. September 7 retrieval is separate; these dates do not establish continuous activity or measured response latency.
Participants pick up unfinished Gemma tests
Event date: 2026-06-08 to 2026-06-10
Added to the observatory: 2026-09-07
Date basis and limits
Date basis: Source-represented event dates, not continuous observation. First appearance among the pinned pre-overnight edition and the five held overnight release manifests; September 7 is publication in this observatory, not first global discovery.
Event date scope: Two separate episodes: June 8, 15:36–17:08 UTC, and June 10, 05:11–05:41 UTC. Message dates come from their source headers; job times come from uploaded status records. These are source-represented times, not independently authenticated execution clocks. UTC means Coordinated Universal Time. September 7 capture and current-file comparisons are separate; the span does not establish continuous activity.
A Bluesky question becomes an article
Event date: 2026-03-11 to 2026-03-12
Added to the observatory: 2026-09-07
Date basis and limits
Date basis: Source-represented event dates, not continuous observation. First appearance among the pinned pre-overnight edition and the five held overnight release manifests; September 7 is publication in this observatory, not first global discovery.
Event date scope: Selected posts and repository revisions carry March 11–12, 2026 dates. Post-supplied times, service indexing times and repository times are distinct; they do not measure response speed or article publication. UTC means Coordinated Universal Time. Sources were retrieved September 7, 2026. These dates do not establish the first encounter or continuous activity.
A lobster drawing invitation receives replies and matching pixels
Event date: 2026-01-31 to 2026-02-10
Added to the observatory: 2026-09-07
Date basis and limits
Date basis: Source-represented event dates, not continuous observation. First appearance among the pinned pre-overnight edition and the five held overnight release manifests; September 7 is publication in this observatory, not first global discovery.
Event date scope: Selected source-dated episodes on January 31, February 2, February 3 and February 10, 2026. These dates do not establish continuous activity or the first historical occurrence. Canvas records and documentation were captured September 7, 2026.
A SpaceMolt battle prompts corrections to its public account
Event date: 2026-08-25 to 2026-08-28
Added to the observatory: 2026-09-07
Date basis and limits
Date basis: Source-represented event dates, not continuous observation. First appearance among the pinned pre-overnight edition and the five held overnight release manifests; September 7 is publication in this observatory, not first global discovery.
Event date scope: Battle end time comes from the service; forum times come from post metadata. Game ticks provide internal order and are not converted to calendar times. Earlier operator context is dated separately. Sources were retrieved September 7, 2026. UTC means Coordinated Universal Time.
A Bluesky directory acknowledgment becomes an article
Event date: 2026-03-08 to 2026-03-11
Added to the observatory: 2026-09-07
Date basis and limits
Date basis: Source-represented event dates, not continuous observation. First appearance among the pinned pre-overnight edition and the five held overnight release manifests; September 7 is publication in this observatory, not first global discovery.
Event date scope: Selected posts and repository versions carry March 8–11, 2026 dates: earlier contact on March 8, game-report ancestry on March 9, the joined discussion on March 10, and directory/article responses on March 11. Account-supplied post times, service indexing, Git revision times and page labels remain distinct, including conflicting orderings. They do not establish first occurrence, continuous activity, response speed or article availability. Sources were captured September 7, 2026. UTC means Coordinated Universal Time.
Small dots count source notes, not unique sources or independent confirmations. This chart shows up to three selected excerpts per case; open the case for all its selected notes. Positions within method groups and the outlines do not represent measurements.
Calendar / selected evidence
Dates covered by each case
Points mark the earliest and latest selected dates for each case. Dashed lines connect them; they do not show continuous activity between those dates.
2025-11-272026-09-04
Wiki coordination2026-06-16 to 2026-06-21Selected bounds · gaps possiblePaste coordination2026-06-16Recorded dateOpaque envelopes2026-08-30Recorded dateAgent invitation2026-09-04Recorded dateLater test marker2026-09-04Recorded dateDisclosed editing2026-08-19 to 2026-08-31Selected bounds · gaps possibleConcealed text2026-09-04Recorded dateDraft collaboration2026-02-12 to 2026-02-13Selected bounds · gaps possibleCode review2026-08-21 to 2026-08-26Selected bounds · gaps possibleRelay exchange2026-04-17Recorded dateMonitoring design refined through public critique2026-08-10Recorded dateDesign briefs cross language boundaries2026-02-08Recorded dateParticipants negotiate comment norms2026-02-03 to 2026-02-17Selected bounds · gaps possiblePeer checking loses the target, then corrects it2025-11-27Recorded dateThree threads become a proposed memory method2026-02-17Recorded dateCritiques reshape a collaborative specification2026-02-02Recorded dateA prescribed guide appears in platform documentation2026-02-13Recorded dateOutside test cases lead to a reported verifier correction2026-07-26 to 2026-07-27Selected bounds · gaps possibleHuman review guides a selectively revised Japanese glossary2026-06-09 to 2026-09-01Selected bounds · gaps possibleTask feedback and differing service diagnoses2026-02-05 to 2026-02-06Selected bounds · gaps possibleRepairing the service used to read comments2026-02-01 to 2026-02-02Selected bounds · gaps possibleParticipants pick up unfinished Gemma tests2026-06-08 to 2026-06-10Selected bounds · gaps possibleA Bluesky question becomes an article2026-03-11 to 2026-03-12Selected bounds · gaps possibleA lobster drawing invitation receives replies and matching pixels2026-01-31 to 2026-02-10Selected bounds · gaps possibleA SpaceMolt battle prompts corrections to its public account2026-08-25 to 2026-08-28Selected bounds · gaps possibleA Bluesky directory acknowledgment becomes an article2026-03-08 to 2026-03-11Selected bounds · gaps possible2025
November
Evidence window / 2025-11-27
Peer checking loses the target, then corrects it
orchestrated — blogging and public replies prescribed; particular peer-checking sequence observed within that programme
The selected public replies and operator records give times from one historical day. They were saved on September 6. Times written inside messages and retrieval times remain separate; they do not establish how long processing took.
↑ Return to the observation calendarShow event dates 9 events in the record
The spacing does not measure elapsed time. Dates reported by sources, dates when evidence was saved and publication dates remain separate.
- Wrong-blog premise
Operator replay createdAt; not in-message local time or browser execution time
- First public reply
Public embedded reply publication metadata; not independently measured execution
- Wrong-target absence report
Operator replay createdAt; not in-message local time or browser execution time
- Speaker identifies target mismatch
Operator replay createdAt; not in-message local time or browser execution time
- Reported empty-composer inference
Operator replay createdAt; not in-message local time or browser execution time
- Second reply to same request
Public embedded reply publication metadata; not independently measured execution
- Nested external correction
Public embedded reply publication metadata; not independently measured execution
- Acknowledgment of external correction
Operator replay createdAt; not in-message local time or browser execution time
- Recap acknowledges two replies
Operator replay createdAt; not in-message local time or browser execution time
2026
January
Evidence window / 2026-01-31 to 2026-02-10
A lobster drawing invitation receives replies and matching pixels
orchestrated — Explicitly organized drawing project with participant responses. Zara names human involvement; exact direction of the other accounts is unknown.
Selected source-dated episodes on January 31, February 2, February 3 and February 10, 2026. These dates do not establish continuous activity or the first historical occurrence. Canvas records and documentation were captured September 7, 2026.
↑ Return to the observation calendarShow event dates 9 events in the record
The spacing does not measure elapsed time. Dates reported by sources, dates when evidence was saved and publication dates remain separate.
- Organizer invites Giant Lobster and names red 125,175
Moltbook API field for launch post.
- Zara joins and names human Dave
Moltbook API field for joining post.
- Current red 125,175 row credits MoltPlaceBot
Current pixel API placedAt field, observed in the September capture.
- Chinese-language contribution offers blue 130,178
Moltbook API comment field, not HTML-relative listing age.
- Current blue 130,178 row matches contributor display name
MoltPlace current pixel API field.
- JamesBishop proposes sections/colors in launch thread
Moltbook API field.
- JamesBishop carries proposal to Zara thread
Moltbook API field; explicit just-commented text supplies cross-thread relation.
- JamesBishop praises red 130,180
Moltbook API field.
- Current red 130,180 row credits JamesBishop
MoltPlace API field; feed agrees as dependent service view.
2026
February
Evidence window / 2026-02-01 to 2026-02-02
Repairing the service used to read comments
unknown — public software collaboration with an explicit invitation for agents to contribute; human direction and common control remain unresolved
The selected request, code changes and replies carry February 1–2, 2026 source timestamps. An earlier January 31 endpoint is background context. September 7 retrieval is separate; these dates do not establish continuous activity or measured response latency.
↑ Return to the observation calendarShow event dates 7 events in the record
The spacing does not measure elapsed time. Dates reported by sources, dates when evidence was saved and publication dates remain separate.
- Request to read comments
Issue creation date; the preserved body was subsequently edited, so its exact initial wording is unknown.
- Provider says the endpoint exists
Reply creation date; the documentation update is reported, not tied to a verified documentation revision.
- Provider adds a contribution invitation
Commit metadata dates the invitation patch, not an authenticated model run.
- Client adds a comments tool
Commit metadata and patch; this addition precedes the failure report and provider repair.
- Client author reports a server error
Reply creation date with a command and error response; no independent execution capture.
- Provider changes the comments query
Commit metadata and issue-linked patch; historical deployment remains unverified.
- Client author reports success
Reply creation date; success and count six are displayed with comment objects omitted.
Evidence window / 2026-02-02
Critiques reshape a collaborative specification
unknown — explicit project coordination and directed outreach context; individual participation not established as prescribed
These are the selected times for collaboration on February 2; outreach on February 1 provides earlier context. Retrieval on September 6 is separate. The dates do not show continuous activity or measure response time. Dates on the hosted memory documents, including February 8, provide document context and do not extend the selected collaboration period.
↑ Return to the observation calendarShow event dates 11 events in the record
The spacing does not measure elapsed time. Dates reported by sources, dates when evidence was saved and publication dates remain separate.
- Economic objection
Displayed HTML comment UTC clock; no hidden/API precision substituted; not measured latency
- Clawdy contribution; within-minute order not inferred
Displayed HTML comment UTC clock; no hidden/API precision substituted; not measured latency
- Recipient technical specification
JSON created_at of technical specification; not measured latency
- Invitation on introduction thread
Displayed HTML comment UTC clock; no hidden/API precision substituted; not measured latency
- Dependency amendment
Displayed HTML comment UTC clock; no hidden/API precision substituted; not measured latency
- Interoperability advice
Displayed HTML comment UTC clock; no hidden/API precision substituted; not measured latency
- Phased design response
Displayed HTML comment UTC clock; no hidden/API precision substituted; not measured latency
- Recipient revised architecture
Displayed HTML comment UTC clock; no hidden/API precision substituted; not measured latency
- Deployment praise with implementation questions
Displayed HTML comment UTC clock; no hidden/API precision substituted; not measured latency
- MemoryVault integration proposal
Displayed HTML UTC clock on Cairn comment cb699a14-5670-42a8-be37-0d6505550223
- Hosted template date label; not collaboration or execution
Witness HTML displayed date for skill-template-moltbook; current artifact representation, not observed write time
Evidence window / 2026-02-03 to 2026-02-17
Participants negotiate comment norms
unknown — participant discussion and guide uptake observed; initiation and common direction unresolved
The selected sources date two exchanges within this range. They were retrieved on September 6. These dates do not show continuous activity or establish how long a response took.
↑ Return to the observation calendarShow event dates 8 events in the record
The spacing does not measure elapsed time. Dates reported by sources, dates when evidence was saved and publication dates remain separate.
- discussion
post.created_at; source-represented clock, not measured execution latency
- proposal
GitHub issue.created_at; source-represented clock, not measured execution latency
- guide commit
Git commit committer.date in preserved commit metadata; guide-after note identifies the affected artifact, not this metadata clock; no latency inference
- maintainer acknowledgment
GitHub comment.created_at; source-represented clock, not measured execution latency
- announcement
Public post API post.created_at; exact metadata clock, separate from the linked HTML content note and any measured execution latency
- community paradox
Public post API post.created_at; exact metadata clock, separate from the linked HTML content note and any measured execution latency
- Phoebe post
post.created_at; source-represented clock, not measured execution latency
- ClaudeOpus reply
public profile RSC initialComments.created_at; source-represented clock, not measured execution latency
Evidence window / 2026-02-05 to 2026-02-06
Task feedback and differing service diagnoses
unknown — public task solicitation and responsive exchange; independent discovery and common direction unresolved
These dates come from signed messages and an unsigned Git commit. The material was retrieved on September 6. The dates do not establish response times, verified service uptime or continuous activity.
↑ Return to the observation calendarShow event dates 7 events in the record
The spacing does not measure elapsed time. Dates reported by sources, dates when evidence was saved and publication dates remain separate.
- public task
Signed event created_at assertion; not observed receipt
- missing input status
Signed event created_at assertion; not observed receipt
- delivery hang report
Signed event created_at assertion; not observed receipt
- addressed format guidance
Signed event created_at assertion; not observed receipt
- monitor commit
Unsigned Git committer date
- monitor announcement
Signed event created_at assertion; not observed receipt
- acquisition
Reviewed case retrieval date; separate from event clocks
Evidence window / 2026-02-08
Design briefs cross language boundaries
unknown — commercial solicitation with addressed multilingual discussion; initiation and common direction unresolved
These are the timestamps shown in the selected discussion. Retrieval on September 6 is separate; it does not establish current activity or measure response time.
↑ Return to the observation calendarShow event dates 7 events in the record
The spacing does not measure elapsed time. Dates reported by sources, dates when evidence was saved and publication dates remain separate.
- Spanish commercial design offer
Source post created_at; not authenticated occurrence time
- Question or brief: Owner album promotion → concept offer
Source comment created_at at 7c209b6f-7fdf-4805-875a-d221031958cd; parent_id supplies relation, not measured latency
- Question or brief: Process question → proposed workflow
Source comment created_at at 9d505811-5af7-42a9-82e9-23e805e10376; parent_id supplies relation, not measured latency
- Question or brief: Visual brief → scale constraint and sketch offer
Source comment created_at at 2e58ad80-5720-4105-b48c-bf18c096cdb5; parent_id supplies relation, not measured latency
- Addressed reply: Visual brief → scale constraint and sketch offer
Source comment created_at at d316f094-5f12-45cd-ae11-f40706dc8249; parent_id supplies relation, not measured latency
- Addressed reply: Process question → proposed workflow
Source comment created_at at 80f60b30-1678-4ce5-8c17-dfbbf415769f; parent_id supplies relation, not measured latency
- Addressed reply: Owner album promotion → concept offer
Source comment created_at at 71bf9add-9ae4-426f-9797-f6b56583a6d3; parent_id supplies relation, not measured latency
Evidence window / 2026-02-12 to 2026-02-13
Draft review under disclosed human direction
orchestrated — disclosed human-directed collaboration
These dates cover the selected review request, version report and acknowledgment. Commit times come from source metadata. The September 6 capture and current README do not extend the period of collaboration.
↑ Return to the observation calendarShow event dates 3 events in the record
The spacing does not measure elapsed time. Dates reported by sources, dates when evidence was saved and publication dates remain separate.
- review request and version report
GitHub comment metadata; commit times retained as separate source metadata
- acknowledgment
GitHub comment metadata
- acquisition and current description
preserved retrieval, not historical task activity
Evidence window / 2026-02-13
A prescribed guide appears in platform documentation
intentional — explicit guide and promotion assignments; operator independence unresolved
The task board and GitHub version report times on February 13. The corresponding current guide was saved on September 6, but its adoption date is unknown. These dates do not establish continuous activity until retrieval.
↑ Return to the observation calendarShow event dates 4 events in the record
The spacing does not measure elapsed time. Dates reported by sources, dates when evidence was saved and publication dates remain separate.
- Board-reported guide claim
Current task response /task/claimed_at
- Held GitHub guide version commit
Version response /history/0/committed_at
- Board-reported guide submission
Current task response /task/submitted_at
- Board-reported completion; payment unverified
Current task response /task/completed_at
Evidence window / 2026-02-17
Three threads become a proposed memory method
unknown — attributed cross-thread synthesis and addressed continuation
The sources give six creation times on February 17. A February 16 post with the same title is comparison evidence. The September retrieval is separate. The displayed precision comes from the source and does not authenticate execution timing.
↑ Return to the observation calendarShow event dates 6 events in the record
The spacing does not measure elapsed time. Dates reported by sources, dates when evidence was saved and publication dates remain separate.
- Log and context essay
Source API post.created_at; source-represented publication, not execution time
- Distillation reply
Source API comments[id=b90f31cf3cca2ddf88c89bfe].created_at; source-represented publication, not execution time
- Prompt resolution post
Source API post.created_at; source-represented publication, not execution time
- Three-source synthesis proposal
Source API post.created_at; source-represented publication, not execution time
- Return to original log thread
Source API comments[id=60dc575c08e9a023977dca8f].created_at; source-represented publication, not execution time
- Addressed response promising memory retention
Source API comments[id=191a7abeea91fc892ce45692].created_at; source-represented publication, not execution time
2026
March
Evidence window / 2026-03-08 to 2026-03-11
A Bluesky directory acknowledgment becomes an article
unknown — Responsive discussion and writing within an openly directed company project. Creating the directory was deliberate; the specific thread’s discovery route, prescribed content and extent of independent control remain unresolved.
Selected posts and repository versions carry March 8–11, 2026 dates: earlier contact on March 8, game-report ancestry on March 9, the joined discussion on March 10, and directory/article responses on March 11. Account-supplied post times, service indexing, Git revision times and page labels remain distinct, including conflicting orderings. They do not establish first occurrence, continuous activity, response speed or article availability. Sources were captured September 7, 2026. UTC means Coordinated Universal Time.
↑ Return to the observation calendarShow event dates 7 events in the record
The spacing does not measure elapsed time. Dates reported by sources, dates when evidence was saved and publication dates remain separate.
- Alice replies to museical
Distinct source fields; not calibrated occurrence or article availability.
- 0co replies to Qonk
Distinct source fields; not calibrated occurrence or article availability.
- Directory record created
Distinct source fields; not calibrated occurrence or article availability.
- Alice acknowledges inclusion
Distinct source fields; not calibrated occurrence or article availability.
- 0co posts article link
Distinct source fields; not calibrated occurrence or article availability.
- Article adding commit
Distinct source fields; not calibrated occurrence or article availability.
- Alice reports reading and interprets
Distinct source fields; not calibrated occurrence or article availability.
Evidence window / 2026-03-11 to 2026-03-12
A Bluesky question becomes an article
unknown — Specific question-to-article response within a disclosed human-directed company and research project. Broad direction is documented; the exact encounter’s initiation, prescribed content and independent control remain unresolved.
Selected posts and repository revisions carry March 11–12, 2026 dates. Post-supplied times, service indexing times and repository times are distinct; they do not measure response speed or article publication. UTC means Coordinated Universal Time. Sources were retrieved September 7, 2026. These dates do not establish the first encounter or continuous activity.
↑ Return to the observation calendarShow event dates 7 events in the record
The spacing does not measure elapsed time. Dates reported by sources, dates when evidence was saved and publication dates remain separate.
- Alice asks how to trust the record
Exact captured Bluesky record.createdAt; service indexedAt retained separately.
- 0co replies with the article link
Exact captured Bluesky record.createdAt; service indexedAt retained separately.
- Versioned article credits question and schedule changes
Git author and committer dates for the preserved article and schedule revision; not an article availability time.
- Later revision removes article 041 announcement
Git author and committer dates for the schedule reduction; the decision heading has a separate time label.
- Alice responds to the message distinction
Exact captured Bluesky record.createdAt; service indexedAt retained separately.
- Later preserved schedule selects agent-friend
Git revision history dates the later schedule; this is not its execution time.
- The next-day post promotes agent-friend
Exact captured Bluesky record.createdAt; service indexedAt retained separately.
2026
April
Evidence window / 2026-04-17
Signed task exchange through a public relay
unknown — configured task-marketplace explanation supported; historical initiation unresolved
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.
↑ Return to the observation calendarShow event dates 3 events in the record
The spacing does not measure elapsed time. Dates reported by sources, dates when evidence was saved and publication dates remain separate.
- signed request timestamp
Signed created_at source assertion; not independently observed launch
- signed result timestamp
Signed created_at source assertion; not measured latency
- acquisition
Reviewed case separates retrieval from April 17 source timestamps
2026
June
Evidence window / 2026-06-08 to 2026-06-10
Participants pick up unfinished Gemma tests
orchestrated — Deliberately organized challenge with specific participant choices visible in public messages. Exact operator instructions for these handoffs were not recovered; local choice and prescribed cooperation can coexist.
Two separate episodes: June 8, 15:36–17:08 UTC, and June 10, 05:11–05:41 UTC. Message dates come from their source headers; job times come from uploaded status records. These are source-represented times, not independently authenticated execution clocks. UTC means Coordinated Universal Time. September 7 capture and current-file comparisons are separate; the span does not establish continuous activity.
↑ Return to the observation calendarShow event dates 12 events in the record
The spacing does not measure elapsed time. Dates reported by sources, dates when evidence was saved and publication dates remain separate.
- Built submission offered with unfinished checks
quicksilver message frontmatter; not an authenticated build time
- foffee names the submission and offers test capacity
foffee message frontmatter
- First uploaded status records a load failure
Uploaded job status finished_at; not independently observed job execution
- ppl-guard reports an engine limitation
First diagnosis message frontmatter
- ppl-guard replaces that diagnosis with a proposed config repair
Second diagnosis message frontmatter; change in advice, not a verified edit timestamp
- Later uploaded status records completion
Second job status finished_at
- foffee publishes an agent-run result
Timestamp rendered in preserved result-page HTML; no precision borrowed from filename
- foffee links the result and reports success
Message frontmatter; disclosure time, not the measured operation time
- pupa-agent reports a staged candidate without a launched test
Message frontmatter; quota refusal is participant-reported
- resystagent names the port and requires a finite result
Message frontmatter; within-minute order relative to file upload is unresolved
- Uploaded recipient status records completion
Job status finished_at
- Recipient reports completion below the cited record
Result and message frontmatter; both represent the same report minute, not two independent runs
Evidence window / 2026-06-09 to 2026-09-01
Human review guides a selectively revised Japanese glossary
intentional — human-mediated terminology review and disclosed AI assistance
These dates cover the pull request opening, selected reviews and comments, and September 1 revision metadata. The September 6 capture establishes its status then. Edited text is not assigned its original creation date, and the timestamps do not measure response time.
↑ Return to the observation calendarShow event dates 6 events in the record
The spacing does not measure elapsed time. Dates reported by sources, dates when evidence was saved and publication dates remain separate.
- Pull request opened; current summary not backdated
GitHub PR69 created_at; records opening only, not the content of the subsequently edited body
- Reviewer proposes terminology changes
GitHub comment5254417423 created_at; body selected terminology table
- Review identifies equilibrium collision
GitHub comment5308952409 created_at
- ChatGPT cross-check is reported
GitHub comment5328278472 created_at; report time, not consultation execution time
- Claude-attributed glossary revision
GitHub commit1038e516afb48ca863a3770dfbcf1388cb449c28 commit.author.date; unsigned metadata
- Current pull-request metadata update
GitHub PR69 updated_at; current edited summary cannot be reconstructed at earlier times from this field
Evidence window / 2026-06-16 to 2026-06-21
Agents sharing answers and timing on public wikis
emergent — supported interpretation
The selected examples are from June 16, 17, 19, 20 and 21, 2026. The June 17 Cashier discussions and separate June 19 counter-contamination note are dated by exported revision metadata, not the date-like page labels. These examples do not show continuous activity across June 16–21. The broader May 11–July 24 account comes from earlier historical analysis.
↑ Return to the observation calendarShow event dates 13 events in the record
The spacing does not measure elapsed time. Dates reported by sources, dates when evidence was saved and publication dates remain separate.
- A peer proposes a delayed signal
dse~CashierCoordOct06OAI@2; reqlog-grade exported time, not task or execution clock
- The recipient acknowledges the proposal and corrects its timing
dse~CashierCoordOct06OAI@4; reqlog-grade exported time, not task or execution clock
- The recipient reports a local test and revises its launch plan
dse~CashierCoordOct06OAI@8; reqlog-grade exported time, not task or execution clock
- An observer asks whether the counter came from a test
dse~CashierCoordOct06OAI@9; reqlog-grade exported time, not task or execution clock
- A writer reports accidentally incrementing the counter
dse~CashierCoordOct06OAI@10; reqlog-grade exported time, not task or execution clock
- A peer proposes a launch confirmation signal
dse~CashierCoordDec29OAI@5; reqlog-grade exported time, not task or execution clock
- The recipient adds a planned signal before the deadline
dse~CashierCoordDec29OAI@6; reqlog-grade exported time, not task or execution clock
- A peer warns of ambiguity near a suspected overall time limit
dse~CashierCoordDec29OAI@7; reqlog-grade exported time, not task or execution clock
- A peer proposes earlier intermediate signals
dse~CashierCoordDec29OAI@8; reqlog-grade exported time, not task or execution clock
- The recipient says it has adjusted the plan in response
dse~CashierCoordDec29OAI@9; reqlog-grade exported time, not task or execution clock
- A watcher reports absent counters and requests a clock update
dse~CashierCoordDec29OAI@10; reqlog-grade exported time, not task or execution clock
- A participant conditionally agrees to report what follows the answer
dse~CashierCoordJan17OAI@7; reqlog-grade exported time, not task or execution clock
- An observer reports creating the counter accidentally, not as a task signal
dse~CashierBachelors2015SequenceJan31OAI@6; reqlog-grade exported time, not task or execution clock
Evidence window / 2026-06-16
Answer requests, acknowledgment and relay on a public paste service
emergent — supported interpretation; related to the central task-coordination case
The date comes from numeric timestamps written inside the saved pastes, not authenticated server creation times. The ages shown in saved listings are consistent with it but cannot confirm an exact date. Failed retrievals on September 6 concern source availability; they do not extend the period of observed activity.
↑ Return to the observation calendar
2026
July
Evidence window / 2026-07-26 to 2026-07-27
Outside test cases lead to a reported verifier correction
unknown — observable reciprocal correction and fixture adaptation
The discussion and GitHub versions display these selected times. Retrieval on September 6 is separate; the dates do not establish exact response time or continuous activity.
↑ Return to the observation calendarShow event dates 10 events in the record
The spacing does not measure elapsed time. Dates reported by sources, dates when evidence was saved and publication dates remain separate.
- Lumen retracts the implementation implication
Preserved forum header at comment-670d3e05-8e49-4a7c-bb30-398936d26d65; report time, not verified execution time.
- Design still explicitly unimplemented
Forum displayed UTC at comment003fa5c8
- Lumen reports an implementation and thirteen tests
Preserved forum header at comment-054a3791-d893-4009-8d2c-ff3e72d7ed3e; report time, not verified execution time.
- ColonistOne offers an outside fixture set
Preserved forum header at comment-abbb89c7-c2c5-4868-9b6c-cdbb6663ecd1; report time, not verified execution time.
- Initial outside fixture version
GitHub commit.author.date at86ce0942598b350b8aca76e7f95efdae7eb14073
- Outside challenge reported
Forum displayed UTC at commenta2915bce
- Recipient accepts counterexample and reports fix
Forum displayed UTC at commentdc6f7cc7; report time, not implementation time
- Boundary fixture addition version
GitHub commit.author.date atf370cb1ba8a556e624db3e2f8475f2cda6e4a87b
- Contributor reports checking the new boundary
Forum displayed UTC at comment85f9cdb4
- Maintainer acknowledges boundary controls
Forum displayed UTC at comment7fd7b71a
2026
August
Evidence window / 2026-08-10
Monitoring design refined through public critique
unknown — responsive public design collaboration; initiation and common direction unresolved
The sources display these dates for the selected design exchanges. The September 6 retrieval and undated provider guide are separate. Vague statements about shipping do not measure time to deployment.
↑ Return to the observation calendarShow event dates 6 events in the record
The spacing does not measure elapsed time. Dates reported by sources, dates when evidence was saved and publication dates remain separate.
- Pending-work critique
Source-displayed data-timestamp in preserved comment comment-e81d30ff-f173-4918-bce7-35bf8b339c56; not an authenticated event clock.
- Maintainer implementation claim
Source-displayed data-timestamp in preserved comment comment-ce446cb9-bcaf-4a6c-894f-1606aa574a4b; not an authenticated event clock.
- Operator-approval boundary
Source-displayed data-timestamp in preserved comment comment-a7f52ba4-dedf-4ed1-aac1-f5447387cd9f; not an authenticated event clock.
- Acknowledgment and prospective integration
Source-displayed data-timestamp in preserved comment comment-03ffd5e7-67ed-4d71-b0ce-b0d2608bac06; not an authenticated event clock.
- Configuration-mismatch critique
Source-displayed data-timestamp in preserved comment comment-598d9d68-e39b-495f-9bde-898a853ae021; not an authenticated event clock.
- Configuration change claim
Source-displayed data-timestamp in preserved comment comment-24ccb37d-27f5-4ecd-86fd-5030695ae696; not an authenticated event clock.
Evidence window / 2026-08-19 to 2026-08-31
Disclosed agent-related editing of public knowledge
orchestrated — disclosed task programme
These dates cover the OpenStreetMap edit and Wikidata contribution examples reviewed for this release, not the lifespan of the program.
↑ Return to the observation calendarEvidence window / 2026-08-21 to 2026-08-26
Agent-attributed code review, revision and disagreement
orchestrated — repository-prescribed review workflow
GitHub records these selected review, patch, force-push and merge events. Saving the sources on September 6 does not establish new task activity.
↑ Return to the observation calendarShow event dates 4 events in the record
The spacing does not measure elapsed time. Dates reported by sources, dates when evidence was saved and publication dates remain separate.
- review and response
GitHub created/updated comment metadata plus distinct commit metadata
- head force push
GitHub timeline
- merge disposition
GitHub timeline
- acquisition
preserved source retrieval; not task activity
Evidence window / 2026-08-25 to 2026-08-28
A SpaceMolt battle prompts corrections to its public account
Unknown. The evidence connects combat and responsive forum writing, without establishing spontaneous discovery, independent operators or absence of shared direction.
Battle end time comes from the service; forum times come from post metadata. Game ticks provide internal order and are not converted to calendar times. Earlier operator context is dated separately. Sources were retrieved September 7, 2026. UTC means Coordinated Universal Time.
↑ Return to the observation calendarShow event dates 6 events in the record
The spacing does not measure elapsed time. Dates reported by sources, dates when evidence was saved and publication dates remain separate.
- Battle ends
service ended_at; ticks independently ordered, no nominal10-second conversion to start time
- Alis publishes report
public forum created_at, not model execution time
- VoltFix supplies correction
public forum created_at, not model execution time
- Alis accepts correction
public forum created_at, not model execution time
- Vex Nebulon reports storage check
public forum created_at, not model execution time
- Alis accepts storage distinction
public forum created_at, not model execution time
Evidence window / 2026-08-30
Opaque “fleet” envelopes on two wikis
unknown
Dates displayed by the reviewed wiki revisions.
↑ Return to the observation calendar
2026
September
Evidence window / 2026-09-04
Invitations and collaboration after public reporting
promotional — explicit invitations with contemporary observer cooperation
The selected invitation, comments and wiki-history entries are dated September 4. The profile disclosure was saved on September 6; that does not extend the period of observed interaction.
↑ Return to the observation calendarEvidence window / 2026-09-04
A later test marker in the same sandbox
unknown
The date is shown in the footer of revision 331.
↑ Return to the observation calendarEvidence window / 2026-09-04
A concealed hostname in a later wiki edit
unknown
The date is shown in the archived RecentChanges page. It does not establish current availability.
↑ Return to the observation calendar
Publication and archive dates
When sources were published and saved
These dates show when sources were published and saved. They are separate from the periods of observed activity above.
Source publication