Around twenty of our own sites, one person deciding what they say. You can keep writing every page by hand and drown politely, or you can build the thing that writes, checks and ships them, and then spend your evenings arguing with it instead. The next months go into the second option: one typed content pipeline, one design language across the sites, and a fact-check gate that is allowed to say no. This is a roadmap, not a victory lap. The design work is out in the world. The engine and the gate are still being built and tested.

Why stop writing posts one by one

Every site started as its own small kingdom. Its own CMS habits, its own idea of what a guide looks like, its own way of being slightly wrong. Fixing one meant fixing it nineteen more times, usually by memory, usually at night.

The interesting work is not the next article. It is the machinery that knows what an article on this site is allowed to contain, where it gets its facts, and who has to look at it before it goes out.

• Content gets a type and a schema, not a blank text box.
• Every generated field should carry where it came from.
• Publishing becomes a separate step with its own rules.
• Live content gets refreshed instead of quietly rotting.

Writing the twentieth guide by hand is not craft. It is a cry for help with good grammar.

The roadmap, in order (in progress)

1. Typed content storage so a review is a review and a glossary term is a glossary term.
2. Generation directed by that schema and every field keeps its provenance.
3. A publication step that talks to our own CMS and to WordPress or custom sites through adapters.
4. Autopilot per content type, only where the type has earned it.
5. Refresh of live pages and follow-ups only after publication is verified.
6. One design language rolled across the sites so the engine is not dressing each one by hand.

Before and the plan for after

The test case: artist bios that refuse to guess

DROP THE BASS is where the gate is being tested first. The artist bio pipeline we are building writes only bio fields and drops claims it cannot support. No invented residencies, no imaginary label history, no "legendary" unless something actually says so. It is not running in production yet. It is the place where we find out whether the gate is strict enough.

Spotify and YouTube matching by ID instead of by name is part of the same work. Plenty of artists share a name with someone who makes very different music, and matching by name is how a jungle producer ends up linked to a wedding band. An ID ends that argument.

The gate can say no

A fact-check that always passes is decoration. The bio gate we are testing drops unsupported lines and leaves the field shorter. A short true bio beats a long beautiful lie every single time.

One design language and many accents

This part is already out. VPNScoreLab, Brokeli, CoinFaro and ProxyLister got new design systems in the last weeks, and SpicaSEO got its own refresh. They should not look identical. They should feel like they come from the same workshop.

Brokeli now speaks eight languages, with calculators, lessons and a glossary. CoinFaro grew a real glossary and guides. That volume only makes sense if the engine underneath stays honest, which is exactly why the engine comes next.

Quality gates before anything goes live

• Every factual field has a source the engine can point to.
• Unsupported claims are dropped and not softened.
• External profiles are matched by ID and not by name.
• The page fits the site's design language.
• Publication is verified before any follow-up runs.
• A person can see what changed and roll it back.

What is honestly still in progress

The content engine in SpicaSEO and the new connector for our own CMS are in progress. Nothing here is shipped as a finished machine. Adapters come for our own CMS first, then WordPress and custom sites. Autopilot will be per content type and no type has earned it yet. The bio gate on DROP THE BASS is in testing, not in production.

A couple of new sites will grow up on this engine from day one. SpicaVPN is prelaunch with a waitlist. CryptoCardCompass is an early catalog with nothing published yet.

Every new site still gets a real review before it opens. The engine prepares. A person decides.

Why roadmap and not launch

We would rather publish where the engine is going and get corrected than announce a finished machine that still needs a babysitter. When pieces ship they go to the Friday Dev Log.

The bet

Fewer hand-made posts. More time on the engine and the gates. If it works, twenty sites stay honest with the same effort as two. If it does not, at least it fails loudly and in one place.

Originally published on the Spicanet blog: https://spicanet.dev/blog/build-the-engine-not-the-posts

Provider tags are hints, not truth

Streaming and event platforms come with genre tags. Some are good. Some are a marketing department's idea of DnB. Until recently an import could quietly overwrite a genre someone had chosen by hand, which is the data version of a stranger rearranging your record shelf while you sleep.

Now imports never wipe or overwrite genres, and a provider string never becomes a genre on its own. It gets read, interpreted and kept as a hint next to the real decision.

• Imports from Spotify or RA cannot overwrite a chosen genre.
• No new genre is created just because a provider typed a word.
• Provider terms are interpreted, not obeyed.

A tag from a platform is a rumor with metadata. Treat it like a rumor.

Provider tag versus our decision

Every label carries a paper trail

Each genre on an artist, release or label now records where it came from. A human editor. A provider hint. A proposal from the engine that someone accepted. If a label is wrong you can see exactly how it got there, and fix the cause instead of the symptom.

The full taxonomy is visible on the genres page, so the decisions are public and arguable. That is the point. Names in a scene should be argued about by people who care, not settled by whichever API answered first.

How a label is allowed to happen

1. Propose: the classifier or the label engine suggests a genre.
2. Evidence: the suggestion must point to eligible first-party text written or approved by a person.
3. Review: an editor sees the proposal with its evidence.
4. Accept: only a person turns a proposal into a label.
5. No evidence means no proposal and no model call at all.

No evidence, no model call

The classifier is review-only and its switch is off by default. Only human-written or approved first-party text may reach a model. Spotify text is blocked in code. If nothing eligible exists the system makes zero model calls instead of guessing.

Start from the labels

Editors describe record labels. The engine then proposes genres for the artists and releases connected to them. Evidence is counted once per source so one loud page cannot vote ten times, and derived proposals never feed further guesses. Every proposal can be reviewed and rejected.

It is a small rule with a big effect: the machine can widen what an editor knows, but it cannot invent a chain of its own assumptions.

Before a machine may label anything

• The evidence is first-party text a person wrote or approved.
• The source is recorded on the label.
• Provider tags are stored as hints and never as decisions.
• A derived guess cannot become evidence for the next guess.
• A person accepts or rejects every proposal.
• There is a kill switch and it starts off.

The same rule outside music

Naming is one case of a wider habit: do not serve what is not true. VPNScoreLab stopped showing synthetic lab speeds. Its unpublished articles now actually return 404 instead of living on in cache. CoinFaro does the same for missing incidents with a real 404 and noindex rather than a cached page that says everything is fine.

A missing page that admits it is missing is more useful than a confident ghost.

A name like liquid funk is not a database value. It is a name a scene made, and we just have to write it down correctly.

Tell us

If we got a name wrong, we would rather hear it now than after the next import.

Originally published on the Spicanet blog: https://spicanet.dev/blog/naming-things-is-editorial-work

The keys are not the hard part

Turning on automation is one switch. Living with it is the hard part. A site on autopilot with no brief, no search data and no budget is not autonomous. It is just unsupervised.

So in SpicaSEO the switch now sits behind a hand-over checklist. Every item links straight to the screen where you fix it. Full Autopilot can only be turned on by the owner, and only after the list is done.

Before a site runs itself

• The site connector works.
• Publishing works end to end.
• There is a written site brief.
• The editorial team is set up.
• A News section exists.
• Search Console and Bing are connected.
• There is a keyword strategy.
• There is an AI budget.

What never goes on auto

Outreach stays on approval. Sending a message to a real person needs a real person to press send, and no checklist changes that.

Risk caps and the first-review rule still apply after hand-over. And every Monday the owner gets a digest of what the site did, so judging it is a habit and not an archaeology project.

Where the line sits

News without making things up

Each site now gets a daily news scan. Search answers are treated as leads, never as sources. Every cited page is actually fetched, and a story only counts if the quote is literally on that page. Stale or blocked sources get rejected.

It is slower than trusting a summary. It is also the difference between news and confident fiction.

How a story earns its place

1. A search answer suggests a lead.
2. Every cited page gets fetched.
3. The quote must appear on that exact page.
4. Stale or blocked sources are dropped.
5. Only then does it become a story.

AI faces, honest labels

Each site can have an AI editorial team, with roles taken from its brief. They can have portraits, and the portraits say what they are: an AI editorial persona, not a real person.

What they cannot have is a fake life. Invented credentials, employers and years of experience are refused. If a site has real people, they are imported read-only and never rewritten. Pictures come from free-licence libraries first, and generation is the fallback.

The hard line

An AI persona can have a face and a role. It cannot have a made-up degree or a made-up career.

Meanwhile across the fleet

The groundwork is already landing on our own sites.

• Team and author pages plus news sections rolled out to ProxyLister, VPNScoreLab, CoinFaro, Brokeli, Samui Love, Trip2Fest and DROP THE BASS.
• Several sites got redesigns from the new design canvas.
• Zomia 1.0 left invite-only beta with open registration and an honest pricing page: no paid plans, fake tiers removed.
• A shared platform update rolled across the repos.

A site that runs itself is only worth having if you can still read what it did on Monday morning.

Next weeks

Switch Autopilot on site by site, only after each checklist is done, and judge every one by its weekly digest.

Originally published on the Spicanet blog: https://spicanet.dev/blog/handing-a-site-over-to-software-honestly