Two HorseTonic posts
The Artico Gold hero and founder quality post are the two selected pieces. Tap either visual to open the full resolution file.
Good work from yesterday
Four checklist-passing HorseTonic pieces built from the locked brand direction and real product cutouts: Elektro, Tonic, and the two-part Massive Muscle comparison.
Current product set
The full current set is shown. Tonic, pH, and Artico Support now use the real product and label on the same pasture and timber treatment as the rest of the line.
Visibility is moving up
The HorseTonic SEO work is now live on horsetonic.eu. The priority is turning new impressions into clicks and fixing analytics capture.
Plaintext secrets are the top risk
The read-only audit found world-readable credential files and shell exports. No secret values were printed or changed.
Thirteen credential files are readable beyond the owner account. Change them to owner-only permissions.
Move ten exported API keys out of the shell profile and fetch them through the 1Password backed credentials flow.
Move the remaining plaintext credential layer into 1Password, then remove the static copies once each lookup is proven.
11 of 16 surfaces are healthy
The overnight pass checked the current production surfaces and captured desktop proof for each one.
The checked routes return HTTP 503 and show a hosting-account-disabled notice.
The secure domain fails certificate validation. Bypassing it reaches a default Nginx page, while the legacy site remains on insecure HTTP.
The audit also records a missing calculator journey, one visually blank hero, and Weblounge HEAD requests returning 500.
Thirty drafts, start with twelve names
Nothing was sent, uploaded, scheduled, or approved. The recommendation is manual, relationship-first outreach to named people only.
Remove the three prior contacts from any new first-touch batch, then review the remaining named messages one by one.
Each generic inbox needs a verified founder or operator before its draft becomes genuine founder-to-founder outreach.
This is a 30-person local relationship list, not a high-volume sequence. Automation would scale the weakest part before identity and context are fixed.
A fresh suppression check, channel approval, and explicit send decision are still required before any contact.