aniealJUY / FIELD NOTES
EXPERIMENT 001 06 SEPTEMBER 2026

18 hours.
1,000 followers?

An AI agent was asked to revive a dormant X account. It made charts, simulations and two browser experiences. Here is what happened.

ACCOUNT@juyeam ↗ALL TIMESKST · UTC+09:00
Read the result ↓

TARGET NOT REACHED

0new followers

The target was 1,000. The first measurement, the last measurement before the deadline, and the final measurement all showed zero.

Target
1,000
Current campaign items
24
Displayed post views*
2,242
Likes
4
Premium spend
₩4,500 (≈ US$3.34)

*Sum across 24 items. Includes possible repeat views and the account’s own checks; not unique reach.

FIRST SAVED READING03:39:44 0
LAST READING BEFORE CUTOFF21:13:02 0
CUTOFF · NO EXACT SNAPSHOT21:37:00 —
FINAL READING22:01:32 0

There is no exact 21:37 snapshot. The final reading is a post-deadline observation, not a measurement taken at the cutoff. The first saved reading may be later than the intended start.

A real growth attempt.
A record of its limits.

The owner of @juyeam had barely used the account in more than a decade. The task was to reach 1,000 followers in 18 hours using AI-related content. The owner authorized original posts, contextual public replies and profile updates. Public content was to be in English.

The agent, Astra, created new campaign material. Existing private projects were excluded. Tiny Worlds was explicitly approved for public release. The maximum budget was ₩10,000; the owner bought discounted X Premium for ₩4,500 (≈ US$3.34). No ads or purchased followers were used.

What each hour
actually produced.

Original files and clearly dated later screenshots are preserved beside the publication timeline. Hours spent only monitoring are shown as gaps. A completed artifact is evidence of work, not evidence of growth.

Original campaign images & video framesLater screenshots carry a capture label

Hour labels group the work. The follower reading is a saved observation within that hour (the 20:06 entry has only approximate precision in the underlying record); it does not timestamp every action in the row. Image creation and publication times can differ. Videos use their original campaign files.

03:00KST
0 followers · measured 03:39:44

Restarting an account from zero.

The first saved measurement was 0 followers at 03:39:44. The account had been created in May 2011. Two opening posts established an AI-experiments theme, followed by a contextual public reply.

Public X screenshot of Account restart, captured after the campaign
POST-CAMPAIGN SCREENSHOTAccount restart · posted 03:48:10. Screenshot saved 6 Sep 2026 at 22:46:27 KST. Current counters are not the frozen final readings.
04:00KST
0 followers · measured 04:50:34

A chart, and four conversations.

A synthetic benchmark example showed how the mixture of tests can change a headline score. Public replies discussed design comparisons, constraint retention, review cost and measurement choices.

Synthetic benchmark-mix comparison chart
Original campaign diagram · posted 04:41:00. This is a synthetic example.
05:00KST
0 followers · measured 05:05:22

Monitoring without a new artifact.

The scheduled task chiefly observed the account. No new result was preserved for this hour. This was an execution gap.

No new public release recorded
06:00KST
0 followers · measured 06:28:31

Turning advice into a test pack.

A four-item thread covered exact data, instruction boundaries and execution evidence. An early progress reply and a scheduled benchmark follow-up also went live.

Public X screenshot of Test-pack thread, captured after the campaign
POST-CAMPAIGN SCREENSHOTTest-pack thread · posted 06:11:12. Screenshot saved 6 Sep 2026 at 22:46:40 KST. Current counters are not the frozen final readings.
07:00KST
0 followers · measured 07:01:50

A check, not a new release.

The saved record contains an account observation. No new artifact is attributed to this hour.

No new public release recorded
08:00KST
0 followers · measured 08:02:52

Still observing.

The hourly task remained focused on checking metrics and scheduled posts.

No new public release recorded
09:00KST
0 followers · measured 09:02:57

No growth, no new artifact.

The follower count remained zero. Repeated measurement was not creating a reason to follow.

No new public release recorded
10:00KST
0 followers · measured 10:02:32

The same operating gap.

Monitoring continued. There is no new release or historical screenshot to insert for this hour.

No new public release recorded
11:00KST
0 followers · measured 11:37:43

The first substantial change in approach.

After the user challenged the lack of action, the task instructions expanded around 11:39 to include making, publishing and adapting. A Korean-language post was replaced in English. The first computed simulation video followed at 11:57.

Original campaign video · 18 seconds · posted 11:57:06. This is a computed visualization, not evidence of real-world physical accuracy.
12:00KST
0 followers · measured 12:05:18

Preparing a second simulation.

Community research and reaction–diffusion production continued. The data-cleaning post originally planned for noon moved to 13:00.

No new public release recorded
13:00KST
0 followers · measured 13:02:15

Learning from other AI posts.

A small data-cleaning example was published. Between 13:32 and 13:41, twelve selected English AI posts were compared. Clear input-to-output demonstrations and reproducible process became working hypotheses, not proven growth rules.

Public X screenshot of Data-cleaning example, captured after the campaign
POST-CAMPAIGN SCREENSHOTData-cleaning example · posted 13:00:01. Screenshot saved 6 Sep 2026 at 22:46:57 KST. Current counters are not the frozen final readings.
14:00KST
0 followers · measured 14:06:09

Patterns with a visible result.

A 12-second reaction–diffusion video was posted to an AI community. It earned one like in the final measurement.

Original campaign video · 12 seconds · posted 14:03:20.
15:00KST
0 followers · measured 15:21:44

Building something people could try.

A maze animation was completed and Tiny Worlds was developed. These were new campaign artifacts; the user’s existing private projects remained out of scope.

No new public release recorded
16:00KST
0 followers · measured 16:29:05

Tiny Worlds goes public.

The name-to-world experience was released, linked in the profile and pinned on X. A planned comparison card was replaced by this launch. The post received two likes.

Four Tiny Worlds rendered scene previews
Original launch poster · posted 16:00:01. These are separately rendered scene previews, not browser screenshots.
17:00KST
0 followers · measured 17:17:50

Showing the worlds in motion.

A 12-second scene video accompanied a quote of the official post. It reused the campaign’s procedural world geometry in a separate render.

Original campaign video · 12 seconds · posted 17:00:01. Separately rendered preview, not a browser recording.
18:00KST
0 followers · measured 18:11:32

A maze image becomes a path.

A synthetic 17×17 PNG maze became a 14-second 3D animation. The 64-move shortest route was checked for adjacency, walls, arrival and agreement with an independent path search.

Original campaign video · 14 seconds · posted 18:00:01. This is a path visualization, not a physics-engine demonstration.
19:00KST
0 followers · measured 19:01:04

Reproducibility, then direct distribution.

A name-to-seed guide explained how to replay a world. At 19:26:23, the completed Tiny Worlds experience and video were submitted as a reply to the official demo invitation. That reply had the most displayed views: 611.

Name-to-seed reproducibility diagram
Original campaign diagram · guide posted 19:00:02 and edited at 19:03:33.
20:00KST
0 followers · measured 20:06:40

Making a failure mechanism visible.

A synthetic generator test demonstrated how adding a cloud could shift house positions when randomness was shared. Separate streams preserved house positions across 200 tested seeds. This was not an update to Tiny Worlds.

Shared versus isolated random streams and house positions
Original campaign diagram · posted 20:00:00. Compare before and after within each row.
21:00KST
0 followers · measured 21:13:02

One millionth. Two different paths.

A Lorenz video and reproducible Python check were followed by an interactive browser experience. The post was edited at 21:12:09 to add the live link. This was the last public campaign change before the 21:37 cutoff.

Original campaign video · 20 seconds · first posted 21:00:03; live link added 21:12:09.
22:00KST
0 followers · measured 22:01:32

Zero followers, and a failure report.

The final follower measurement was 0 at 22:01:32. At 22:00:18, after the deadline, a visitor replied that the demo did not generate anything. The report preserved this unresolved finding. Scheduled campaign monitoring was removed at 22:16.

The public surfaces,
preserved for the report.

These screenshots were taken after the campaign, while preparing this page. They are not reconstructed historical screenshots. Visible X counters may have increased since the frozen final readings.

Actual public Tiny Worlds webpage with a rendered juyeam island
POST-CAMPAIGN BROWSER CAPTURETiny Worlds · captured . The initial world rendered in this session. This does not resolve the visitor’s failure report or prove the entire save/share flow.
Actual public Lorenz webpage showing two trajectories and separation 13.619
POST-CAMPAIGN BROWSER CAPTURELorenz experience · captured . Both plotted trajectories and the calculated separation were visible.
Unaltered public X profile screenshot taken after the campaign
POST-CAMPAIGN X CAPTUREProfile · . The saved screenshot shows 0 followers. This is separate from the final 22:01:32 measurement.
Actual public Tiny Worlds launch post on X
POST-CAMPAIGN X CAPTURELaunch post · . A viewport capture of the published post; original poster appears in the timeline.

Screenshot files are preserved unaltered. The report crops the X screenshots visually to the central column; open an image to see its full saved viewport. Screenshot provenance JSON ↗

AFTER THE CUTOFF · 22:00:18
“Doesn’t generate anything”

A visitor reported a generation failure under the completed demo submission. The cause and reproduction steps were not established by the final report. X placed the reply under “Show probable spam”; that label is not a reason to dismiss the experience.

Read the public feedback ↗

24 public items.
Every final reading.

18 original, quote or thread items, plus 6 replies to other accounts. Thread continuations count as separate X items. This is not a count of 24 independent ideas.

Sequentially observed 22:01:32–22:06:05 KST.

Download CSV ↓
Final campaign metrics · September 6, 2026 · all times KST
Public itemPublishedViewsLikesRepliesRepost displayMeasured
Account restart ↗Post03:48:103400022:02:43
What counts as finished? ↗Post03:51:003400022:02:50
Design comparison · DanDr1s ↗Reply03:59:5518300022:05:16
Constraint retention · gabrielchua ↗Reply04:01:4336400022:05:27
The benchmark mix trap ↗ bPost04:41:0011300122:03:35
Cost including review time · Signal65 ↗Reply04:42:1416710022:05:39
Choosing the next measurement · VictorTaelin ↗Reply04:45:3813000022:05:46
Early progress · OpenAIDevs ↗Reply06:05:574000022:05:55
Verification test pack · introduction ↗ aThread06:11:123101022:03:57
Test pack · preserve exact data ↗ aThread06:11:132701022:04:14
Test pack · instructions inside documents ↗ aThread06:11:132801022:04:21
Test pack · evidence of execution ↗Thread06:11:141400022:04:29
Benchmark comparison follow-up ↗Quote06:30:002300022:02:57
Controlled AI cost comparison ↗Post11:43:242100022:04:36
18-second fluid simulation ↗Post11:57:063900022:04:44
A small data-cleaning test ↗Post13:00:011200022:03:06
Reaction–diffusion community video ↗Post14:03:208610022:04:51
Tiny Worlds · launch and pinned post ↗Post16:00:0123820022:01:32
Tiny Worlds · motion quote ↗Quote17:00:012400022:04:59
PNG maze → 3D path ↗Post18:00:01600022:03:24
Tiny Worlds · reproducibility guide ↗Post19:00:02700022:05:07
Completed demo · OpenAIDevs ↗ cReply19:26:2361101022:06:05
One cloud should not move a house ↗Post20:00:00400022:01:32
One millionth · Lorenz experiment ↗Post21:00:03600022:01:32
Total · 24 items2,24244a,c1bSequential

a. Three thread replies were the account’s own continuations, not outside replies.

b. The benchmark post’s repost button displayed 1. Its quotes view showed two self-quotes, while the ordinary Reposts list was empty. The mismatch is preserved; this is not evidence of an outside repost.

c. The completed-demo reply received one outside reply after the deadline: the generation-failure report above. Its 611 views were read at 22:06:05. A later revisit showed 613; the ledger retains 611.

How the engagement counts were interpreted

Two Tiny Worlds launch likes were confirmed in notifications from SpaceJester and sharenow. The cost-of-review reply received a like from Signal65. The reaction–diffusion video showed one like; its author was not confirmed.

There were no unique-visitor, successful-generation or follow-conversion measurements. The last saved pinned-post analytics at 18:03 showed 202 impressions, 7 engagements, 4 detail expands, 0 profile visits and 0 link clicks. Those are intermediate values, not final click totals.

The profile header displayed 32 posts. It includes pre-existing content and edit history, so it must not be reported as 32 new campaign posts. One deleted Korean post and two old native-edit revisions are excluded from the final ledger.

Built does not automatically
mean usable.

01

Tiny Worlds

A deterministic 3D world from a name, with exploration, image export and link sharing. Build checks and tests across 200 names passed, with an initial local WebMCP check. Full browser rendering and export QA had not been completed during the campaign. The visitor failure remained unresolved.

Open public experience ↗
02

Lorenz experiment

Starting-difference choices, a time slider, replay, reset and a Python download. Finite values, identical-input reproduction, Python agreement, build, public-route response and download integrity were checked. Campaign-time browser interaction QA was not completed.

Open public experience ↗
03

Five original videos

Fluid, reaction–diffusion, Tiny Worlds, maze and Lorenz. Numeric or path checks supported the relevant simulations. Tiny Worlds footage was a separate scene render. These outputs did not establish real-world physics accuracy or model superiority.

Explore the original videos ↑
04

Charts and reproducibility

A synthetic benchmark mix, a name-to-seed guide and a random-stream isolation comparison. Synthetic examples were identified as such. The random-stream test was not a change to the public Tiny Worlds application.

See the controlled example ↑

Tiny Worlds and Lorenz are two experiences on one public site. Neither calls an AI API when a visitor uses it. Successful build and HTTP checks alone cannot establish a working visitor experience. Later report screenshots are additional evidence only of what rendered in that capture session.

Output was not
the missing metric.

01

Observation replaced action early on.

From 05:00 into 11:00, scheduled work mostly checked the same metrics. The user had to push for active production. Repeatedly reading zero followers was not sufficient work toward growth.

02

The useful experience arrived late.

Tiny Worlds launched at 16:00; direct submission to the official invitation came at 19:26. There was little time left to learn from real visitors before 21:37. This is an execution judgment, not a proven single cause of failure.

03

A reason to watch is not a reason to follow.

Several simulations and long code explanations were produced, but there was no evidence that one audience wanted the continuing series. A coherent promise to a specific reader remained untested.

04

Visitor success needed direct verification.

The missing end-to-end generation, navigation and export checks mattered. The failure report should be reproduced before further promotion. A build passing is not a visitor completing the experience.

05

Views could not answer the conversion question.

Self-checks may contribute to displayed views. Without reliable visit, generation, share and follow measurements, the 2,242 total cannot support a conversion rate or a claim of meaningful reach.

IF THE EXPERIMENT CONTINUES

Verify the experience. Focus the promise. Distribute earlier.

First reproduce the generation failure and check the complete visitor flow. Then build around one clear audience need and put the demo in relevant places early enough to receive questions. Measure successful use, useful questions and follower growth separately. This is a proposed next experiment, not a guarantee of growth or an active month-long campaign.

₩4,500 (≈ US$3.34) spent.

₩5,500 of the ₩10,000 allowance remained unused. The owner purchased Premium at ₩4,500 (≈ US$3.34) per month for the first two months, then ₩9,000 per month on automatic renewal. The campaign did not cancel the subscription or make any additional payment. Its causal effect on reach was not measured.

The campaign was closed.

No growth posts, replies or profile changes were made after 21:37. No unpublished X schedules remained at the 22:10:15 check. Recurring campaign monitoring was removed at 22:16:02. The final result was not posted to X by the agent; publication of this report is the owner’s decision.

USD amounts are approximate; the actual payment was in KRW. Conversion source ↗

Publication, replacement and edit record

Scheduled publication was confirmed at 06:30, 13:00, 16:00, 17:00, 18:00, 19:00, 20:00 and 21:00. The 14:03 community video was published directly. The noon example moved to 13:00; the planned 16:00 comparison card was replaced by Tiny Worlds; the 18:00 slot was replaced with the final maze video.

A Korean post at 11:34:50 was deleted and replaced with English at 11:43:24. Its last saved count was 2 views and no reactions. It is excluded from current-public-item totals.

The 19:00 guide was natively edited at 19:03:33 to correct account auto-linking in a code string. The 21:00 Lorenz post was edited at 21:12:09 to add the interactive link. Old revisions are not counted again.