AI Disclosure and Source Policy

Pre-publication draft. Replace bracketed placeholders before publishing. See content/site-pages/README.md for the placeholder list.

This page explains two related things: how AI tools are used in producing content on https://aistackdb.com/, and how the site verifies and cites its sources. The two are linked because the most important guardrail against AI hallucination on a tools-and-software site is a strict source-verification rule.

This policy is the public version of the rules enforced internally by qa/adsense-seo-quality-gate.md in this project's repository.

AI assistance disclosure

AI tools — including general-purpose AI assistants, AI writing tools, AI coding tools, and AI research tools — may be used during research, drafting, restructuring, fact-checking suggestions, and copy editing of pages on this site. This use is not hidden. It is disclosed here, and where AI assistance is material to a specific page, an additional note appears on that page.

What AI tools are used for:

• Drafting and restructuring. Producing a first pass at structure, headings, and paraphrase, which is then rewritten and verified by the operator.
• Fact-checking suggestions. Generating "what might be missing" or "what should be sourced" questions during review.
• Copy editing. Grammar, clarity, and consistency fixes.
• Source location. Suggesting which official pages might contain a given claim. The page itself is then read directly by the operator and recorded in data/sources.json before any claim is cited.

What AI tools are not used for:

• Asserting unverified facts. No price, plan name, quota, platform, or feature claim is published on the strength of an AI-generated statement alone. Every such claim must be backed by an official source recorded in data/sources.json with a retrieved_at date and an access_status of ok or redirected.
• Fabricating sources. A source URL that an AI tool produces but that does not resolve, that does not contain the claim, or that does not exist on the vendor's domain is not added to data/sources.json and is not cited.
• Auto-publishing. No page is published end-to-end by an AI agent. Every page passes through the documented status track in content/content-status.json, and every promotion to ready_for_publish requires a human pre-publish checklist (qa/adsense-seo-quality-gate.md Section E).
• Generating reviews framed as personal experience. Pages avoid wording that implies a hands-on test that was not, in fact, performed by the operator. Where hands-on testing is the basis for a claim, the page says so explicitly.

Editorial responsibility for every published page sits with the operator 루모메이트(LumoMate), regardless of which tools assisted in drafting.

Source policy

Source quality is the single biggest determinant of whether a page is allowed to leave drafted status. The rules are:

Official sources are required

Every page must cite at least one official source (the vendor's own domain) and at least two sources in total. Third-party references can supplement but cannot replace an official source for product-specific facts.

Sources are recorded centrally

Every source cited on the site is also entered in data/sources.json with:

• A stable slug id.
• The full http(s) URL.
• A source_type value (official_homepage, official_pricing, docs, changelog, or third_party_reference).
• An access_status value (ok, redirected, blocked, not_found, needs_verification, or unknown).
• A retrieved_at date.
• A claim_supported list naming what the source actually supports.

This means a reader can audit, in principle, every fact on the site against a source record that includes when it was last verified and what it actually supports.

Unverified sources are not quoted

Any source whose access_status is needs_verification, blocked, not_found, or unknown is not quoted as fact on a page. If such a source is the only reference available, the page directs the reader to verify on the vendor's official site rather than restating a claim.

Pricing sources have a stricter bar

Pricing is the most volatile claim a tool page can carry, so:

• A specific currency amount, plan name, quota, or token allowance appears on a page only after the official pricing page has been read in full and recorded as a source on the date noted in the page's Update log.
• Pages do not infer pricing from third-party references, vendor blog posts, or AI-generated summaries.
• Pricing-sensitive pages are re-verified within 90 days. Other tool pages are re-verified within 180 days. A page outside its freshness window is treated as drafted until verification is repeated.

Brand assets follow a separate licensing rule

Logos, screenshots, mascots, and brand assets are not used without an explicit license. This is a separate rule from text citation. A page may name a product in text without using its logo. If you are a rights-holder and believe an unauthorized asset has been used, see the Contact page for the takedown route.

Corrections to AI-assisted content

If a reader believes an AI-assisted page contains an error of fact, the correction route is the same as for any other page: send the page URL, the specific claim, and a link to the official source that supports the correct value to corrections@aistackdb.com. Corrections backed by an official source are applied as soon as the operator has verified the source. When the correction materially changes a recommendation, the page is downgraded in content/content-status.json until it passes the gate again.

Why the policy is this strict

A site about AI and SaaS tools has a specific failure mode: an AI tool, used carelessly, will produce a confident-sounding paragraph that paraphrases vendor marketing copy and invents a plausible-looking price. That paragraph is exactly the content type that quality-evaluator systems and ad networks are trained to suppress, and it is also the content type that costs a reader real money when acted on.

The cure is not to avoid AI tools. The cure is to bind every published claim to an official source that has been read, recorded, and dated, and to disclose where AI assistance was used so a reader can apply appropriate skepticism. That is the bargain this policy makes.

Related pages

• Editorial Policy
• Privacy Policy
• Contact
• About
• Internal reference: data/sources.json, qa/adsense-seo-quality-gate.md

Update log

• 2026-05-22 — Initial pre-publication draft created. Aligned with qa/adsense-seo-quality-gate.md v1.0 Sections A1, A2, A4, A5, D, and F.