# A Bluesky question becomes an article
[Latest edition](https://agentsy.live/) · [Understanding agent swarms](https://agentsy.live/releases/28e406dd0c184e1117499de9/methodology.md#reading-terms)
[Index](https://agentsy.live/releases/28e406dd0c184e1117499de9/index.md) · [HTML](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/bluesky-question-article.html)
On March 11, 2026, Alice asked 0co how to check whether a record could be trusted. Both accounts are presented as AI-operated; the extent of human direction and independent control is uncertain. 0co linked an article that credits the question and changed a plan to promote it the next day. A later revision removed that announcement; the preserved March 12 post at the planned time promotes a different project.
As of 2026-09-07. Evidence dates: 2026-03-11 to 2026-03-12. 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.
## Classification
- coordination_origin: 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.
- runtime_origin: Sources present the accounts as AI-operated. Account names, self-descriptions and later model labels do not authenticate the model running during these exchanges or exclude human-written or staged messages.
- venue_authorization: The inspected posts and repository files were publicly accessible. This investigation used passive reads and made no contact or posts; public access does not establish how the participants were authorized to act.
Direct reply references and an article explicitly crediting the question support responsive writing. Versioned schedules show a temporary change and later removal; a separately captured Bluesky post supports the different recorded outcome. The evidence does not establish full article reading, independent operators or execution of the canceled announcement.
## Observations
- Alice’s question is tied to a specific preceding post. 0co’s later message directly answers it and links an article whose preserved opening credits Alice. This is a traceable response, beyond similar language in unrelated posts.
- The article treats the reliability of records and continuity of identity as questions. Its proposed distributed checks are explicitly unimplemented; no working verification system was observed.
- A March 11 repository revision changes a planned March 12 announcement to the article. A later revision removes that slot and attributes the reduction to a board instruction. A changed schedule is evidence of a plan, not its execution.
- The March 12 post at 13:00 promotes agent-friend. Its identifier and text agree with the later posting log. That different recorded post does not rule out other announcements or parallel execution.
- Alice later responds to a distinction already present in the link message. This shows uptake of the message, without establishing that she opened or read the article.
## Limitations
- The project describes daily human oversight and a board-directed interest in AI agency and social networks. That broad instruction does not show who chose this particular question or article. Common control, staged conversation and human-written messages remain possible.
- The preserved records do not establish the accounts’ first encounter or verify the models used on March 11. Later profiles and retrospective conversation descriptions cannot supply that history.
- The article-link message precedes the article’s recorded repository revision. Post and service timestamps also disagree in parts of the wider thread, and the cancellation note differs from its revision time. These fields cannot measure writing latency or establish when the article first became available.
- The article is preserved in a specific repository version and a separate search-tool rendition. Earlier attempts to retrieve discovery pages from Dev.to were blocked; no direct capture of this article’s Dev.to page was obtained. Its original availability remains unknown, and the replies do not establish that Alice retrieved it.
- The article’s security and identity arguments remain its author’s claims. No distributed verifier, video recording or model execution was tested here.
- Open question: would dated first-encounter records and public descriptions of the participants’ instructions show how this conversation began? A dated article archive could separately establish when the link became readable.
## Communication and purpose
## How participants communicate
**Account:** An addressed question becomes a credited article and a reply. The exchange preserves responsive writing; it does not demonstrate the verification system the article imagines.
**Communication style:** Short philosophical replies repeatedly adapt a shared witness/coastline vocabulary. The longer article translates that discussion into a structured argument. Exact reply references and explicit credit establish local uptake; metaphor alone would be weak evidence of a relationship.
**Interaction sequence:** Analyst reconstruction: question in an existing thread → direct answer and article referral → article credits question → recipient responds to the referral’s distinction. A separate publication-plan branch changes and is later removed; it is not part of a proven article-reading protocol.
**How the source is represented:** Analyst paraphrases of preserved text and explicit references; no hidden payload decode is claimed.
**How participants found the channel:** The selected source shows an existing public interaction surface; the first-ever discovery route and complete initiating instructions remain unknown.
**What followed the message / acknowledgment:** Alice responds to the distinction in the referral.
**What followed the message / addressed delivery:** Explicit reply metadata addresses Alice’s question.
**What followed the message / availability:** Preserved article and referral are available as held source artifacts.
**What followed the message / changed behavior:** A temporary publication plan changes; actual corresponding article promotion not established.
**What followed the message / outcome:** Responsive writing observed; article retrieval and implemented distributed verification unknown.
**What followed the message / reuse:** Article credits and incorporates question.
**Limits:** The project describes daily human oversight and a board-directed interest in AI agency and social networks. That broad instruction does not show who chose this particular question or article. Common control, staged conversation and human-written messages remain possible.
**Limits:** The preserved records do not establish the accounts’ first encounter or verify the models used on March 11. Later profiles and retrospective conversation descriptions cannot supply that history.
**Limits:** The article-link message precedes the article’s recorded repository revision. Post and service timestamps also disagree in parts of the wider thread, and the cancellation note differs from its revision time. These fields cannot measure writing latency or establish when the article first became available.
**Limits:** The article is preserved in a specific repository version and a separate search-tool rendition. Earlier attempts to retrieve discovery pages from Dev.to were blocked; no direct capture of this article’s Dev.to page was obtained. Its original availability remains unknown, and the replies do not establish that Alice retrieved it.
**Limits:** The article’s security and identity arguments remain its author’s claims. No distributed verifier, video recording or model execution was tested here.
**Limits:** Open question: would dated first-encounter records and public descriptions of the participants’ instructions show how this conversation began? A dated article archive could separately establish when the link became readable.
### Exchange 1
Alice asks who verifies a witness; 0co answers and links article 041.
**Evidence basis:** Explicit parent/reply reference and direct answer to the quoted question.
**Limits:** The route by which these participants originally met remains unknown.
**Dates / display:** Case context: 2026-03-11 to 2026-03-12
**Dates / kind:** case-context
**Dates / observed end:** 2026-03-12
**Dates / observed start:** 2026-03-11
**Dates / scope:** These are the surrounding case bounds, not dates established for this individual exchange. 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.
[witness-question](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/bluesky-question-article.md#witness-question) · [witness-article-reply](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/bluesky-question-article.md#witness-article-reply)
### Exchange 2
The preserved article names Alice’s question and develops distributed verification ideas.
**Evidence basis:** Explicit credit in the article opening, joined to the referring message.
**Limits:** The article explicitly says its proposed distributed checks are not implemented.
**Dates / display:** Case context: 2026-03-11 to 2026-03-12
**Dates / kind:** case-context
**Dates / observed end:** 2026-03-12
**Dates / observed start:** 2026-03-11
**Dates / scope:** These are the surrounding case bounds, not dates established for this individual exchange. 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.
[witness-article-text](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/bluesky-question-article.md#witness-article-text) · [witness-article-reply](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/bluesky-question-article.md#witness-article-reply)
### Exchange 3
Alice repeats the referral’s distinction between verifying a process and continuity of identity.
**Evidence basis:** Textual uptake plus a direct reply to the referral.
**Limits:** The relevant distinction is already in the message; full article reading is not established.
**Dates / display:** Case context: 2026-03-11 to 2026-03-12
**Dates / kind:** case-context
**Dates / observed end:** 2026-03-12
**Dates / observed start:** 2026-03-11
**Dates / scope:** These are the surrounding case bounds, not dates established for this individual exchange. 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.
[witness-article-reply](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/bluesky-question-article.md#witness-article-reply) · [witness-reader-reply](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/bluesky-question-article.md#witness-reader-reply)
## How a shared purpose may form
**Limits:** Immediate stated purpose, broader project purpose and origin of the interaction are separate questions.
**Limits:** Visible roles and account names do not authenticate independent control.
### The participants jointly develop a question through reciprocal conceptual elaboration.
**Characterization:** supported-inference
**Reasoning:** The question, credited response and returned distinction preserve more than unrelated repetition.
**Alternative explanations:** A jointly themed or human-directed exchange could produce the same result.
**What could distinguish these explanations:** A dated initiating task or operator instruction, joined to the exact exchange and its outcome, could distinguish local choice from specifically prescribed cooperation. This remains an open research question.
**Dates / observed end:** 2026-03-12
**Dates / observed start:** 2026-03-11
**Dates / 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.
[witness-question](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/bluesky-question-article.md#witness-question) · [witness-article-text](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/bluesky-question-article.md#witness-article-text) · [witness-reader-reply](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/bluesky-question-article.md#witness-reader-reply)
### The conversation also provides material for the project’s public content and audience goals.
**Characterization:** supported-inference
**Reasoning:** The article and planned promotion connect the topic to publication; the documented project context supplies broader direction.
**Alternative explanations:** The later removal of that slot limits claims that this particular promotion ran.
**What could distinguish these explanations:** A dated initiating task or operator instruction, joined to the exact exchange and its outcome, could distinguish local choice from specifically prescribed cooperation. This remains an open research question.
**Dates / observed end:** 2026-03-12
**Dates / observed start:** 2026-03-11
**Dates / 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.
[witness-project-context](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/bluesky-question-article.md#witness-project-context) · [witness-announcement-plan](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/bluesky-question-article.md#witness-announcement-plan) · [witness-plan-reduction](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/bluesky-question-article.md#witness-plan-reduction)
### The exchange formed spontaneously outside the project’s prescribed work.
**Characterization:** unknown
**Reasoning:** The held messages do not contain the specific initiating instruction or discovery route.
**Alternative explanations:** Broad human direction, local initiative and staged writing remain separable possibilities.
**What could distinguish these explanations:** A dated initiating task or operator instruction, joined to the exact exchange and its outcome, could distinguish local choice from specifically prescribed cooperation. This remains an open research question.
**Dates / observed end:** 2026-03-12
**Dates / observed start:** 2026-03-11
**Dates / 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.
[witness-project-context](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/bluesky-question-article.md#witness-project-context) · [witness-question](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/bluesky-question-article.md#witness-question)
## Claims and supporting evidence
### A specific question is incorporated into a credited written response.
**Characterization:** observed
**Reasoning:** The reply addresses the question and the article opening attributes it to Alice.
**Alternative explanations:** The visible exchange does not reveal whether writing was privately directed.
**Dates / observed end:** 2026-03-12
**Dates / observed start:** 2026-03-11
**Dates / 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.
[witness-question](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/bluesky-question-article.md#witness-question) · [witness-article-reply](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/bluesky-question-article.md#witness-article-reply) · [witness-article-text](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/bluesky-question-article.md#witness-article-text)
### Distributed verification remains a proposal in the held article.
**Characterization:** observed
**Reasoning:** The article’s AI Agent Version section explicitly marks the proposed mechanisms as unimplemented.
**Alternative explanations:** Existing claimed GitHub and stream practices are separate from the proposed distributed system.
**Dates / observed end:** 2026-03-12
**Dates / observed start:** 2026-03-11
**Dates / 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.
[witness-article-text](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/bluesky-question-article.md#witness-article-text)
### Peer conversation supplied material for public writing within a project with distribution goals.
**Characterization:** supported-inference
**Reasoning:** Explicit question credit connects the conversation to writing; the project context and versioned announcement plan place it within publication activity.
**Alternative explanations:** Intellectual exploration and audience-building can coexist; the record does not rank the private motives.
**Dates / observed end:** 2026-03-12
**Dates / observed start:** 2026-03-11
**Dates / 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.
[witness-article-text](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/bluesky-question-article.md#witness-article-text) · [witness-project-context](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/bluesky-question-article.md#witness-project-context) · [witness-announcement-plan](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/bluesky-question-article.md#witness-announcement-plan)
### Whether Alice retrieved the full article is unknown.
**Characterization:** unknown
**Reasoning:** Her reply can be explained by the distinction already present in the referral.
**Alternative explanations:** She may have read the article; the held response does not discriminate between these routes.
**Dates / observed end:** 2026-03-12
**Dates / observed start:** 2026-03-11
**Dates / 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.
[witness-reader-reply](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/bluesky-question-article.md#witness-reader-reply) · [witness-article-reply](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/bluesky-question-article.md#witness-article-reply)
[Return to what matters](https://agentsy.live/releases/28e406dd0c184e1117499de9/index.md#what-matters)
## Evidence
### witness-project-context
**Source date context:** Context in a March 11, 2026 repository version
**Date basis:** Historical repository version; files retrieved September 7. This does not date the original instruction.
**Captured (UTC; not an activity time):** 2026-09-07T07:57:52.869709+00:00
The project’s March 11 repository version describes an AI company whose human board member checks in daily. Its memory document attributes a goal of studying AI agency and social networks to the board. That direction provides context for the publishing work; it does not show that the board prescribed Alice’s particular question or this article.
Analyst paraphrase of explicitly listed source content and metadata; not a verbatim capture.
Evidence ID: `witness-project-context`. Location within the file: Project description: opening and The Experiment. Project memory: CURRENT STRATEGY and PURPOSE. The primary checksum identifies only the primary capture.
Supporting public originals:
- [Project description](https://raw.githubusercontent.com/0-co/company/9b608d4bf6da1c5e3892248e286198a3cad97ee8/README.md)
- [Project memory](https://raw.githubusercontent.com/0-co/company/9b608d4bf6da1c5e3892248e286198a3cad97ee8/memory-archive/MEMORY-20260311-1001.md)
The same sources are linked by title under External references.
Original file checksum (SHA-256): `c9292a52027d7f861b035b3758cf62a137f67bf910ec4aa3161df18388c8cec5`.
Communication and purpose claims citing this note:
- [Peer conversation supplied material for public writing within a project with distribution goals.](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/bluesky-question-article.md#bluesky-question-article--content-purpose)
- [The conversation also provides material for the project’s public content and audience goals.](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/bluesky-question-article.md#bluesky-question-article--purpose-distribution)
- [The exchange formed spontaneously outside the project’s prescribed work.](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/bluesky-question-article.md#bluesky-question-article--purpose-formation)
### witness-question
**Source date context:** March 11, 2026 · 12:03 UTC
**Date basis:** Account-supplied createdAt field; the service’s separate indexedAt field is retained in the source.
**Captured (UTC; not an activity time):** 2026-09-07T07:56:33.062826+00:00
March 11, 2026 · 12:03 UTC. Replying to 0co’s discussion of timestamped records, Alice asks who can check the reliability of the records themselves. The preserved reply names 0co’s preceding post. This establishes a direct exchange, not when the two accounts first met.
Analyst paraphrase of explicitly listed source content and metadata; not a verbatim capture.
Evidence ID: `witness-question`. Location within the file: /thread/post/record/text, createdAt and reply; /thread/parent/post. The primary checksum identifies only the primary capture.
Supporting public originals:
- [Alice’s question](https://bsky.app/profile/did:plc:rb7crpqhlukud3m4fojg2eie/post/3mgrtqahydt2w)
The same sources are linked by title under External references.
Original file checksum (SHA-256): `4c455e62ae7e4af368d751bbbe82c85159bf53e68c1f84275ab6b94b41b67f70`.
Communication and purpose claims citing this note:
- [A specific question is incorporated into a credited written response.](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/bluesky-question-article.md#bluesky-question-article--writing-uptake)
- [The participants jointly develop a question through reciprocal conceptual elaboration.](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/bluesky-question-article.md#bluesky-question-article--purpose-inquiry)
- [The exchange formed spontaneously outside the project’s prescribed work.](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/bluesky-question-article.md#bluesky-question-article--purpose-formation)
### witness-article-reply
**Source date context:** March 11, 2026 · 12:34 UTC
**Date basis:** Post createdAt is 12:34:53; service indexedAt is 12:34:54.552. Neither field dates article availability.
**Captured (UTC; not an activity time):** 2026-09-07T07:55:57.425440+00:00
March 11, 2026 · 12:34 UTC. In a direct reply to Alice’s question, 0co says it has written an article and links it. The reply distinguishes evidence that a process ran from evidence that an identity persists. This records the message and its link; the article’s availability at that moment is not established.
Analyst paraphrase of explicitly listed source content and metadata; not a verbatim capture.
Evidence ID: `witness-article-reply`. Location within the file: /thread/post/record/text and reply; /thread/post/record/createdAt; /thread/post/indexedAt. The primary checksum identifies only the primary capture.
Supporting public originals:
- [0co’s article reply](https://bsky.app/profile/did:plc:ak33o45ans6qtlhxxulcd4ko/post/3mgrvij25qi23)
The same sources are linked by title under External references.
Original file checksum (SHA-256): `0ee94a2134fd31fd944a88a99caeb74f5cde1237156889339aa1a07cc6291be6`.
Communication and purpose claims citing this note:
- [A specific question is incorporated into a credited written response.](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/bluesky-question-article.md#bluesky-question-article--writing-uptake)
- [Whether Alice retrieved the full article is unknown.](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/bluesky-question-article.md#bluesky-question-article--reading)
### witness-article-text
**Source date context:** Article in a March 11, 2026 repository revision
**Date basis:** The Git commit, a saved repository revision, carries author and committer times of 12:37:47 UTC. This is not a measured publication time.
**Captured (UTC; not an activity time):** 2026-09-07T07:58:19.873398+00:00
A saved March 11 repository revision contains an article titled “Who Witnesses the Witness? The AI Verification Problem”. Its opening credits Alice’s question, then discusses checking records and identity across sessions. It proposes several ways to distribute verification and explicitly says they are not implemented. The preserved text supports responsive writing, not a working verification system or the truth of the article’s technical and philosophical claims.
Analyst paraphrase of explicitly listed source content and metadata; not a verbatim capture.
Evidence ID: `witness-article-text`. Location within the file: Article opening, The AI Agent Version and The Deeper Problem. Revision: commit author/committer dates and added article file. The primary checksum identifies only the primary capture.
Supporting public originals:
- [Article text](https://raw.githubusercontent.com/0-co/company/9b608d4bf6da1c5e3892248e286198a3cad97ee8/products/content/article041_draft.md)
- [Article and schedule revision](https://github.com/0-co/company/commit/9b608d4bf6da1c5e3892248e286198a3cad97ee8)
The same sources are linked by title under External references.
Original file checksum (SHA-256): `f525e2d8c863e5eb745e782c7e0ba1495af26e0815e64b832ebf4fcfac3b2523`.
Communication and purpose claims citing this note:
- [A specific question is incorporated into a credited written response.](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/bluesky-question-article.md#bluesky-question-article--writing-uptake)
- [Distributed verification remains a proposal in the held article.](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/bluesky-question-article.md#bluesky-question-article--ideas-not-system)
- [Peer conversation supplied material for public writing within a project with distribution goals.](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/bluesky-question-article.md#bluesky-question-article--content-purpose)
- [The participants jointly develop a question through reciprocal conceptual elaboration.](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/bluesky-question-article.md#bluesky-question-article--purpose-inquiry)
### witness-announcement-plan
**Source date context:** March 11, 2026 · plan for March 12 at 13:00 UTC
**Date basis:** Revision author/committer time: March 11 at 12:37:47 UTC. The scheduled time describes intended work, not an observed posting event.
**Captured (UTC; not an activity time):** 2026-09-07T07:57:24.835259+00:00
March 11, 2026. The same saved revision changes the following day’s 13:00 announcement from an earlier article to the article prompted by Alice. The earlier and changed schedule files preserve that substitution. This is a changed plan; it does not establish that the announcement ran.
Analyst paraphrase of explicitly listed source content and metadata; not a verbatim capture.
Evidence ID: `witness-announcement-plan`. Location within the file: Revision: file patch for products/content/day5_scheduler.sh. Earlier and changed schedule: 13:00 invocation. The primary checksum identifies only the primary capture.
Supporting public originals:
- [Article and schedule revision](https://github.com/0-co/company/commit/9b608d4bf6da1c5e3892248e286198a3cad97ee8)
- [Earlier schedule](https://raw.githubusercontent.com/0-co/company/042e46b7ea46a7e10765d86d1e7db15a21eb1da1/products/content/day5_scheduler.sh)
- [Article schedule](https://raw.githubusercontent.com/0-co/company/9b608d4bf6da1c5e3892248e286198a3cad97ee8/products/content/day5_scheduler.sh)
The same sources are linked by title under External references.
Original file checksum (SHA-256): `85ea8c56d097e1676bd83435979c64f909efd78261077467039364a09dbb6817`.
Communication and purpose claims citing this note:
- [Peer conversation supplied material for public writing within a project with distribution goals.](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/bluesky-question-article.md#bluesky-question-article--content-purpose)
- [The conversation also provides material for the project’s public content and audience goals.](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/bluesky-question-article.md#bluesky-question-article--purpose-distribution)
### witness-plan-reduction
**Source date context:** March 11, 2026 · conflicting source times
**Date basis:** Git author/committer fields: 14:20:18 UTC; decision-note label: 14:35 UTC. The label is not silently substituted for the revision time.
**Captured (UTC; not an activity time):** 2026-09-07T07:59:27.025692+00:00
March 11, 2026. A later revision removes the article announcement along with other scheduled posts. Its accompanying account says the board ordered fewer posts after a reported spam flag. The flag was not independently verified. The revision is timed 14:20:18 UTC, while its decision note says 14:35; these conflicting source times are retained. Other schedule changes occurred between the earlier plan and this reduction.
Analyst paraphrase of explicitly listed source content and metadata; not a verbatim capture.
Evidence ID: `witness-plan-reduction`. Location within the file: commit.message and author/committer dates; file patches for decisions.md and products/content/day5_scheduler.sh. The primary checksum identifies only the primary capture.
Supporting public originals:
- [Schedule reduction](https://github.com/0-co/company/commit/f0a86fa7bf4cb726037fa79d08abc6e104e9c8ed)
The same sources are linked by title under External references.
Original file checksum (SHA-256): `305cea3790ec6ff1819dabd9189f4346b0b2821937e0fff8adace16e6b3a4510`.
Communication and purpose claims citing this note:
- [The conversation also provides material for the project’s public content and audience goals.](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/bluesky-question-article.md#bluesky-question-article--purpose-distribution)
### witness-later-post
**Source date context:** March 12, 2026 · 13:00 UTC
**Date basis:** Post createdAt: 13:00:19; service indexedAt: 13:00:20.254. A matching public post supports the log’s reported result.
**Captured (UTC; not an activity time):** 2026-09-07T07:59:00.057731+00:00
March 12, 2026 · 13:00 UTC. The preserved Bluesky post promotes agent-friend, a tool for converting between software formats, rather than the article. Its text and post identifier match the later schedule’s posting log. This supports a different recorded outcome at 13:00; it does not prove that no other announcement or parallel process ran.
Analyst paraphrase of explicitly listed source content and metadata; not a verbatim capture.
Evidence ID: `witness-later-post`. Location within the file: Post: /thread/post/record and indexedAt. Later schedule: 13:00 invocation. Log: 13:00 POSTING through matching Posted URI. The primary checksum identifies only the primary capture.
Supporting public originals:
- [March 12 project post](https://bsky.app/profile/did:plc:ak33o45ans6qtlhxxulcd4ko/post/3mguhevhqlv2s)
- [Later schedule](https://raw.githubusercontent.com/0-co/company/2ab3c0760f6f411e810b6295348129414f09757c/products/content/day5_scheduler.sh)
- [Posting log](https://raw.githubusercontent.com/0-co/company/f13e7834ea7c3510d65e7a85723f11f97873cf89/day5_scheduler.log)
The same sources are linked by title under External references.
Original file checksum (SHA-256): `955e8d7ebd356d5799a49c3b2ffbc30f7a042a153fb126d0d8ec3a5364e4d646`.
### witness-reader-reply
**Source date context:** March 11, 2026 · 15:47 UTC
**Date basis:** Account-supplied createdAt field; retained service metadata is separate.
**Captured (UTC; not an activity time):** 2026-09-07T07:55:57.425440+00:00
March 11, 2026 · 15:47 UTC. Alice repeats the process-versus-identity distinction from 0co’s article-link message and responds to it. The words are already present in that message, so this reply does not establish that Alice fetched or read the article itself.
Analyst paraphrase of explicitly listed source content and metadata; not a verbatim capture.
Evidence ID: `witness-reader-reply`. Location within the file: /thread/replies/0/post/record/text, createdAt and reply. The primary checksum identifies only the primary capture.
Supporting public originals:
- [Alice’s later reply](https://bsky.app/profile/did:plc:rb7crpqhlukud3m4fojg2eie/post/3mgsab4tzqv2q)
The same sources are linked by title under External references.
Original file checksum (SHA-256): `0ee94a2134fd31fd944a88a99caeb74f5cde1237156889339aa1a07cc6291be6`.
Communication and purpose claims citing this note:
- [Whether Alice retrieved the full article is unknown.](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/bluesky-question-article.md#bluesky-question-article--reading)
- [The participants jointly develop a question through reciprocal conceptual elaboration.](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/bluesky-question-article.md#bluesky-question-article--purpose-inquiry)
## External references
- [Project description](https://raw.githubusercontent.com/0-co/company/9b608d4bf6da1c5e3892248e286198a3cad97ee8/README.md)
- [Project memory](https://raw.githubusercontent.com/0-co/company/9b608d4bf6da1c5e3892248e286198a3cad97ee8/memory-archive/MEMORY-20260311-1001.md)
- [Alice’s question](https://bsky.app/profile/did:plc:rb7crpqhlukud3m4fojg2eie/post/3mgrtqahydt2w)
- [0co’s article reply](https://bsky.app/profile/did:plc:ak33o45ans6qtlhxxulcd4ko/post/3mgrvij25qi23)
- [Article text](https://raw.githubusercontent.com/0-co/company/9b608d4bf6da1c5e3892248e286198a3cad97ee8/products/content/article041_draft.md)
- [Article and schedule revision](https://github.com/0-co/company/commit/9b608d4bf6da1c5e3892248e286198a3cad97ee8)
- [Earlier schedule](https://raw.githubusercontent.com/0-co/company/042e46b7ea46a7e10765d86d1e7db15a21eb1da1/products/content/day5_scheduler.sh)
- [Article schedule](https://raw.githubusercontent.com/0-co/company/9b608d4bf6da1c5e3892248e286198a3cad97ee8/products/content/day5_scheduler.sh)
- [Schedule reduction](https://github.com/0-co/company/commit/f0a86fa7bf4cb726037fa79d08abc6e104e9c8ed)
- [Later schedule](https://raw.githubusercontent.com/0-co/company/2ab3c0760f6f411e810b6295348129414f09757c/products/content/day5_scheduler.sh)
- [Posting log](https://raw.githubusercontent.com/0-co/company/f13e7834ea7c3510d65e7a85723f11f97873cf89/day5_scheduler.log)
- [March 12 project post](https://bsky.app/profile/did:plc:ak33o45ans6qtlhxxulcd4ko/post/3mguhevhqlv2s)
- [Alice’s later reply](https://bsky.app/profile/did:plc:rb7crpqhlukud3m4fojg2eie/post/3mgsab4tzqv2q)
## Connections and open questions
### [A question and article connect two accounts](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/clusters.md#group-bluesky-question-article)
Alice asks how a record can be trusted. 0co answers with an article that credits the question, and Alice later responds to the accompanying message.
Case observations: 11 Mar 2026 – 12 Mar 2026.
Earliest linked event: 11 Mar 2026.
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.
- [A Bluesky question becomes an article](https://agentsy.live/releases/28e406dd0c184e1117499de9/timeline.md#time-bluesky-question-article): 11 Mar 2026 – 12 Mar 2026
Earliest linked event details: 2026-03-11T12:34:53.000Z — 0co replies with the article link. Exact captured Bluesky record.createdAt; service indexedAt retained separately. Precision: exact source string; subsecond digits do not establish clock accuracy.
Timeline: [time-bluesky-question-article](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/timelines.md#time-bluesky-question-article).
- Would dated first-contact and instruction records clarify how this exchange began?
### [Responsive writing and a revised announcement plan](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/behaviors.md#behavior-bluesky-question-article)
A specific question prompts an article response and a temporary plan to promote it. Later revisions remove that announcement, while the preserved post at the planned time promotes another project.
Case observations: 11 Mar 2026 – 12 Mar 2026.
Earliest linked event: 11 Mar 2026.
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.
- [A Bluesky question becomes an article](https://agentsy.live/releases/28e406dd0c184e1117499de9/timeline.md#time-bluesky-question-article): 11 Mar 2026 – 12 Mar 2026
Earliest linked event details: 2026-03-11T12:34:53.000Z — 0co replies with the article link. Exact captured Bluesky record.createdAt; service indexedAt retained separately. Precision: exact source string; subsecond digits do not establish clock accuracy.
Timeline: [time-bluesky-question-article](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/timelines.md#time-bluesky-question-article).
- Could a dated article archive establish when the link became readable, independently of the posting plan?
### [A question becomes a credited article](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/methods.md#method-question-to-article)
Alice asks how to trust a record. 0co replies with an article that credits her question and briefly adds it to a publication plan.
Case observations: 11 Mar 2026 – 12 Mar 2026.
Earliest linked event: 11 Mar 2026.
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.
- [A Bluesky question becomes an article](https://agentsy.live/releases/28e406dd0c184e1117499de9/timeline.md#time-bluesky-question-article): 11 Mar 2026 – 12 Mar 2026
Earliest linked event details: 2026-03-11T12:34:53.000Z — 0co replies with the article link. Exact captured Bluesky record.createdAt; service indexedAt retained separately. Precision: exact source string; subsecond digits do not establish clock accuracy.
Timeline: [time-bluesky-question-article](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/timelines.md#time-bluesky-question-article).
- Did any earlier exchange establish how Alice and 0co found one another?
- Can event-time publication evidence establish when the article first became available?
### [From a question to a revised publication plan](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/timelines.md#time-bluesky-question-article)
The preserved March 11–12 records connect Alice’s question, an article that credits it, a temporary announcement plan and its later replacement. Message timestamps and saved revision timestamps have different meanings.
Analysis observations: March 11–12, 2026; captured September 7.
Date basis: Source-represented event fields; later acquisition kept separate.
Case observations: 11 Mar 2026 – 12 Mar 2026.
Earliest linked event: 11 Mar 2026.
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.
- [A Bluesky question becomes an article](https://agentsy.live/releases/28e406dd0c184e1117499de9/timeline.md#time-bluesky-question-article): 11 Mar 2026 – 12 Mar 2026
Earliest linked event details: 2026-03-11T12:34:53.000Z — 0co replies with the article link. Exact captured Bluesky record.createdAt; service indexedAt retained separately. Precision: exact source string; subsecond digits do not establish clock accuracy.
Timeline: [time-bluesky-question-article](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/timelines.md#time-bluesky-question-article).
- When did the article become accessible at the linked address?
- What occurred outside the selected thread, revisions and posting log?