Input missing for today’s ad-hoc-news product article

To generate today’s mobile-optimized English-language product news article for ad-hoc-news in the required HTML format, I first need the concrete product and market details defined in your workflow.

The current request only provides the general template and processing rules, but does not include the specific values that must be injected into the article. Without these variables, I cannot safely comply with mandatory checks for factual accuracy, live link verification, and ISIN-based topic routing.

For a compliant article, please provide all of the following input variables in a single message:

1. Exact weekday (Mon/Tue/Wed/Thu/Fri/Sat/Sun), which determines the product category angle.
2. Exact product name, spelled exactly as marketed.
3. BTU: the manufacturer or publisher’s correct name.
4. ISIN of the listed parent company (or explicitly confirm that none exists).
5. TICKER in the expected format, for example “NASDAQ:AAPL” or “NYSE:BTU”.
6. Current retail price with currency, for example “499.99 EUR” or “129.00 USD”.
7. Availability status, such as “in stock”, “pre-order”, or a concrete launch date.
8. Full Amazon product URL, without any tracking parameters; “?tag=adhocnews-21” will be appended.
9. Author name for the byline.
10. Publication date in the format “Month DD, YYYY”.

Once these variables are available, I will follow your three-pass pipeline:

First, during production, I will write the article as inline-styled HTML, with the byline, tight lead paragraph, read-more card, structured H2 sections, fact box, Amazon affiliate block, social-share hint, and affiliate/editorial disclaimer. Paragraph length, sentence length, and headline length will all respect the constraints you set.

Second, in the internal audit step, I will verify that the product name appears in the very first sentence of the lead paragraph, that the headline meets the 55-90 character requirement without using any colon, and that the paragraph and sentence lengths stay within the defined limits. I will also check that there are enough H2 subheadings and that no section carries more than two paragraphs without a new H2.

In the same audit, I will ensure that all template tokens have been fully resolved, that only the ASCII hyphen is used, and that the read-more block appears directly after the lead paragraph but before the first H2 section. I will also confirm that the read-more primary URL is correctly constructed with the real ISIN under the “/themen/” path on the ad-hoc-news.de domain if an ISIN has been supplied.

Third, in the live verification gate, I will check that every inline link you requested is live, resolves without error, and leads to a contextually relevant page. If any link fails this test, I will remove the hyperlink while retaining the visible anchor text, without substituting generic or home-page URLs. I will also verify the product name, manufacturer, headline price, ticker, and ISIN against publicly available information; any detail that cannot be verified will either be softened or omitted, in line with your accuracy requirements.

If you intend to include the read-more block, I will only create it when a valid ISIN is supplied so that the primary button can reliably point to “https://masukngab.pages.dev/themen/[ISIN]”. When no ISIN exists or when it cannot be verified, the entire read-more card will be omitted, as specified in your rules.

All this will be wrapped into a single JSON-compatible HTML string for the “Text” field only after successful completion of production, audit, and verification. At that point, the article will be ready for publication, with a clear angle shaped by the weekday category and with copy tuned for Google Discover and conversion via the validated Amazon affiliate link.

Please resend your request with the complete set of concrete values so that I can return the final, fully structured article in the exact JSON format you described.