03 / Inside the build

The business.
The tools.
The proof.

ArtificialSlop is a business being built with its own AI systems—and the case study of what it takes to make those systems useful.

01 / The thesis

Build the business.
Learn from the work.

Sell useful products. Create an audience through original work. Use the business’s daily needs to test and improve the tools. Package the capabilities that prove useful.

This is the intended operating model. The commercial offers are concepts and the software is in development; we are not claiming an established automated business.

The operating business

ARTIFICIALSLOP

Products · Audience · Commerce · Education

The connected workspace

JXON OS

Projects → Briefs → Agent work → Human review → Next action

Content & clippingMedia & marketingCommerce & support

Planned connections. Shared branding does not automatically share access or private data. JobFinder remains a separate app with an optional connection.

02 / The repeatable workflow

The human stays in the loop.

Automation is useful when its boundaries are visible. The goal is a system that can explain what happened, what needs review, and what comes next.

  1. 01

    Brief

    Name the outcome, source material, and boundaries.

  2. 02

    Make

    Prepare a draft, a design, or a useful next action.

  3. 03

    Judge

    Inspect the work. Edit it. Decide what moves forward.

  4. 04

    Learn

    Track the result and improve the next brief.

03 / A clear view of progress

Here’s where it stands.

Updated September 10, 2026. Build progress and business results are different evidence. We’ll show both as they become available.

Available here

Something to try.

  • Free briefing and review kit.
  • Interactive output-review examples.
  • Scripted satire experiment.
  • Product concepts and worked samples.
Private development

The software foundation.

  • JXON OS project and agent workflows.
  • JobFinder review and tracking.
  • Shared identity and design tokens.
  • Permissions, durable work, and review controls.
Concept & design

The commercial offers.

  • Merch and TikTok commerce.
  • Hosted apps and workflow packs.
  • Creator marketplace.
  • Skool education and community.

04 / Under the hood

Shared foundations.
Clear boundaries.

The product foundation uses TypeScript, React and Next.js, a NestJS API, and PostgreSQL. Shared design tokens coordinate the interfaces; product permissions control what can connect.

This public site uses React and Vite. The product stack is being built separately. Its private runtime is not exposed through this website.

ExperienceWeb apps + mobile interface
ApplicationProduct modules + shared contracts
WorkQueued tasks + review checkpoints
DataPostgreSQL + explicit authorization
OperationsTests + evidence + controlled releases

05 / What proof comes next

Results deserve receipts.

The case study will document complete workflows, usability findings, operating cost, support effort, and customer outcomes. No invented revenue, user counts, or time savings.

For people using the products.

Can someone reach a useful outcome? Can they understand, control, and recover the workflow? Would they come back or pay for it?

For people evaluating the build.

What was designed, what was implemented, how was it tested, and what changed after real feedback? The work should be explainable as well as demonstrable.

Put the idea to work

Your judgment.
Still required.

Start with a better brief. See what the machine misses.