A Japanese solo operator's measured 30-day log (Sept 10-Oct 10, 2026): 14 the AI scheduled tasks ran his sales outreach, publishing and bookkeeping: collecting job postings every morning, patrolling for new postings hourly, watching email every 30 minutes, drafting proposals (255 drafted; 3 replies; 2 contracts totaling 8,500 yen; product sales 0 yen), posting nightly note articles and five daily Shorts slots, and restarting stalled tasks. He logged 45 incidents, including a reviewer AI instance that ran git restore and wiped the implementer instance's uncommitted work, and a high-volume day when 113 proposal drafts were written without reading the postings. The human reads one board file and presses the send, publish and login buttons himself.
¥8,500
This only partly worked. Worth knowing before you try it.
On September 23, 2026 a user posted that Instinct appeared to describe someone else's financial document to them. Founder Noah Shinn responded the same day that the model had fabricated a proper noun — a hallucination, not a data breach — and that the team built a hallucination detection layer within 48 hours.
This one went wrong. See what happened before you try it.
He used the AI API to draft his articles automatically for a week. Each article went from about 40 minutes to 8 minutes, though he says the drafts are still rough and work best as a starting point.
This only partly worked. Worth knowing before you try it.
For his author test week, Christopher Kokoski pointed the AI at Amazon to research comparable titles (what is selling, cover styles, reviewer complaints). Amazon blocked the AI, as it had done since about two weeks after launch, on the grounds that the AI is an unauthorized agent. Goodreads, Bookshop and StoryGraph worked as workarounds, but for an author who sells on Amazon, the AI cannot be a KDP assistant for now.
This one went wrong. See what happened before you try it.
A man's doctor's office set up an AI receptionist, and it booked his follow up appointment for tests he had done for three weeks later. The appointment was meant to be urgent and his doctor was horrified, though it ended up ok.
This one went wrong. See what happened before you try it.
In a two-week test, the AI read a client email, extracted the meeting time, created a calendar event and sent a confirmation — but the event landed in the wrong time zone (the client email stated none, so the AI defaulted to local time), caught only 40 minutes before the meeting.
This only partly worked. Worth knowing before you try it.
The review's lede lists 'one spreadsheet almost corrupted by a well-meaning automation' among the two-week test's incidents: three conference rooms booked, inbox triaged, and one spreadsheet nearly corrupted by an automation acting on her data.
This only partly worked. Worth knowing before you try it.
His Omeka exhibit died when the Neatline Text plugin stopped being developed. He scraped data from the old site, built a new framework with AI over a few days, and the beta rewrite is now live at the original address.
This only partly worked. Worth knowing before you try it.