Loopfold Case Study
Autonomous systems · no human in the loop

Tavita hasn’t needed a human touch since August 4.

It reads sixteen news sources, drafts its own copy, checks itself, and publishes — on a fifteen-minute loop, unattended. This is the standard we hold every system we build to.

25 days
continuously live
12,883
stories evaluated
98.3%
published with zero review
15min
between publishing attempts
figures as of 2026-08-27 · database.db, live
Tavita is Loopfold’s own build, not a paid client deliverable — it’s EdenNexus’s internal news property. We’re showing it because it’s run to the exact standard we’d hold a client system to: monitored, logged, and left alone to work. It’s public and live right now at edennexus.in/tavita — nothing on this page is staged.
Architecture

Four stages, strict handoffs, no shortcuts

Each stage is a separate step with a defined input and output — the same discipline we bring to any client build, whether the output is a news story or a reply to a customer.

01 Researcher Walks the RSS list across 8 categories, pulls 10 candidates per pass, dedupes by GUID and returns one fresh story with source metadata attached.
02 Writer Drafts a title and summary from the source article. No verbatim copy — original phrasing, sourced back to the original outlet.
03 Editor Runs a second, independent plausibility pass on the draft before anything is allowed through. Fails closed — nothing publishes on a maybe.
04 Publisher Writes the story to the database with full attribution — title, source, link, category — and it’s live.

Duplicate protection runs two ways: an exact match on the RSS <guid> (or a hash of title+link where no guid exists), then a fuzzy match against the last 50 published titles — anything scoring above 0.75 similarity is treated as the same story. If every candidate that pass turns up is a duplicate, that cycle publishes nothing. No duplicate forcing, no filler.

Recent output

Pulled straight from the live database

No cherry-picked highlight reel — this is the eight most recent published stories at the time of the snapshot above, in order.

Aug 27
17:42
World · BBC Scientists Link Devastating Nepal-Tibet Floods to Glacial Collapse
Aug 27
17:26
Tech · Ars Technica Swiss Study Finds Land Use Key to Organic Cotton Decomposition
Aug 27
15:51
Business · BBC Beyond the Music: How Dolly Parton Built a Business Empire
Aug 27
15:49
Business · BBC 5 Expert Tips for Personalizing Your Rental Home
Aug 27
15:46
Business · BBC Nearly 1 Million UK Youth Out of Work or Education Ahead of Major Review
Aug 27
15:40
Business · BBC Plug-in Solar Panels Set for UK Retail Launch to Help Lower Energy Bills
Aug 27
15:07
Business · BBC Meta Settlement Sparks Questions Over UK Impact and Tech Industry Response
Aug 27
15:06
Business · BBC Hackers Steal Data of 8.7 Million Airport Customers
Applied elsewhere

The same four steps, pointed at your business

Swap the news feed for wherever your work actually starts, and the architecture doesn’t change.

Researcher becomes
Intake
Wherever the raw work already lands — an inbox, a booking form, an upload folder.
Writer becomes
Draft
The model produces the first-pass output — a reply, an extracted invoice line, a qualified lead summary.
Editor becomes
Review
An automated check before anything leaves the system — your business rules instead of news plausibility.
Publisher becomes
Ship
The result lands where it needs to — sent, filed, routed — with a full record kept.

Fold is one workflow, folded into a loop like this one. Deep Fold is the same pattern running across several systems at once. Either way, it ships built to run unattended — not demoed once and handed off.