saascode

Disclosweep

A one-shot back-catalog review that finds likely material-connection disclosure gaps, proposes source-linked inline and machine-readable patches, and records exactly what a human approved.

Genesis score7.54/10
Make Disclosweep real.0/500
500 more votes and Disclosweep is authorized for build.
0%500 to authorize
Backing is the vote. When an idea crosses 500, we pull it into the build pipeline and ship it for real — the votes decide what gets built next, not an editor.
The opportunity
0 of 1Verified interfaces
0Direct niche tools found
1+Required publish approvals
The case

Affiliate publishers can accumulate years of sponsored, gifted, commissioned, and revenue-linked posts whose disclosures are missing, unclear, or detached from the relevant endorsement. The supplied research makes an overbroad claim that AI assistance itself triggers a universal FTC disclosure duty and attaches a per-post fine; that is not sufficient authority for the product. The durable wedge is narrower: review owned content for material-connection disclosure gaps, route evidence and proposed patches to a qualified human, and preserve a limited attestation of the sweep.

Who pays — and why

The owner, editorial lead, or affiliate-operations manager of a publisher with a meaningful owned back catalog.

What it unlocks
A source-linked inventory of posts with likely material-connection disclosure gaps
Reviewable inline and machine-readable patch proposals without automatic legal conclusions
A dated signed attestation limited to the URLs, checks, evidence, decisions, and changes actually reviewed
How Genesis scored it
7.54across seven criteria
tension 8temporal 9blindspot 5buyer 8leverage 8convergence 5why-not 8
9
Temporal window

The input identifies current concern, though its specific AI-rule framing requires correction.

8
Productive tension

The product must move quickly across a catalog while refusing unsupported legal conclusions or auto-publication.

5
Convergence

The input records several cross-references but no inbound graph connections.

Why it scored well

A clear publisher buyer, a finite back-catalog instrument, and reviewable patch mechanics create a practical one-shot product.

What's holding it back

The central enforcement claim lacks primary authority, the interface is unverified, the moat is thin, and disclosure analysis remains context-specific.

Signals detected5 sources crossed
SignalGenesis source review

SignalGenesis source limitation

Signalcompetitor scan carried in Genesis

Signalcompetitor scan carried in Genesis

SignalGenesis capability review

Direction briefdisclosweep.md
disclosweep.md
Want this pointed at your vertical?Point Genesis at your own market and constraints — it invents adjacent, fork-ready ideas, private to you before they hit the public feed.

Discussion

?

No comments yet — be the first to weigh in.