Social Media Accounts — John / Adom Industries

How to log in and post on every social channel we use, as John and as the company. No passwords live on this page. Credentials live in Google Contacts (one contact per company, login + password + freshness dates in the notes field). Read them with adom-google contacts search <name> -v and update the "last successful login" date after each login or password change.

The core rule: masquerade, don't share passwords

Every one of these platforms lets a personal login act as the company. Always use that, because it means one human logs in as themselves and gains/loses company access via a role, so nobody's password gets copied around and offboarding is one click. Sharing the [email protected] password is the fallback, not the plan.

To finish X delegation (do these in order)

1. As @lauer_john: x.com/settings/delegate → turn ON "Allow others to invite you to their account".
2. As @Adom_Industries (log in with [email protected]): Settings → Security and account access → Delegate → Members you've delegated → invite @lauer_john as Admin.
3. Back as @lauer_john: accept the invite. From then on, switch to the company via the account switcher — no password.
4. Repeat step 2 for Colby's handle to give him X posting alongside his LinkedIn access.

To finish YouTube delegation

@adominc must be a Brand Account (channel → Settings → Permissions → Invite). Sign in as [email protected], then add [email protected] as Owner/Manager and Colby as Manager. If Permissions is missing, the channel is a legacy personal channel and must be moved to a Brand Account first.

Browser identities (which window is who)

Two identities, kept in separate browser profiles so they never cross-contaminate:

# John's identity (pup default profile)
adom-desktop --target AdomLapper --ai-thread "<thread>" browser_open_window \
  '{"sessionId":"as-john","owner":"social","url":"https://www.linkedin.com/feed/"}'

# Company identity — SEPARATE durable profile, its own cookie jar
adom-desktop --target AdomLapper --ai-thread "<thread>" browser_open_window \
  '{"sessionId":"as-company","owner":"social","profile":"adom-media","url":"https://x.com/Adom_Industries"}'

# Company identity in the user's REAL Chrome (wake it first; opens no window, steals no focus)
adom-desktop --target AdomLapper --ai-thread "<thread>" nbrowser_wake_profile '{"profile":"chrome:[email protected]"}'

Both can be open at once — separate profiles means separate sessions, so John's window stays John and the company window stays the company. Do not use one profile for both; logging the company into adom-you would silently replace John's session.

⚠ Before posting anywhere corporate, confirm the ACTIVE handle. John's real Chrome is signed into X as @lauer_john and YouTube as [email protected], so a careless post from that browser goes out under John's personal name.

⚠ X blocks fresh automated logins. Signing @Adom_Industries into a brand-new pup profile jams or challenges (the account has 0 posts, so it looks dormant and gets extra scrutiny). This is exactly why delegation above is the right path: it needs no new login at all. If a password login is unavoidable, expect an email/phone challenge and drive it in the user's real Chrome, not a fresh profile.

Channel status (verified 8/3/2026)

Note the pattern: John's personal reach dwarfs the company's on every platform (6,370 vs 282 on LinkedIn, 14,100 vs 11 on YouTube). Corporate posts travel because John and the team amplify them, not on their own. Plan launches accordingly.

Where credentials live

LinkedIn

John's profile — login username [email protected] (primary email); password in work contact "LinkedIn". [email protected] is a verified secondary email (added 8/2/2026; old zipwhip address removed), so password login works with either address and "Sign in with Google" works from either Google account. New-device logins hit a checkpoint John approves in the LinkedIn phone app; tick "recognize this device".

Company page — Adom Industries Inc., company id 107763966. Kenneth Knox also posts as the page. Admin URLs: dashboard · published posts · content analytics (per-post impressions/CTR).

Per-post analytics for John's own posts: linkedin.com/analytics/post-summary/urn:li:activity:<id>/.

pup's adom-you profile is signed in as John (since 8/3/2026) and the credential is in pup's vault for host www.linkedin.com, so a bare browser_login {sessionId, submit:true} re-signs-in.

X (x.com)

• Company: @Adom_Industries — created under [email protected]; this is the one to use. Credentials: work contact "X Twitter Corp Account".
• @adomindustries (under [email protected]) is a duplicate — do not post from it. It still shows the display name "John Lauer".
• John personal: @lauer_john — credentials in personal contact "Twitter".

YouTube

• Company channel @adominc ("Adom Industries") under [email protected]; credentials in work contacts "Media Adom Account" and "Media (for Adom)".
• John's own Google account reaches @JohnLauerGplus and @familychannel7887 only.

The [email protected] identity

The shared "Adom media" Google account owning the corporate X and YouTube presence, so a media department can take it over wholesale later. A Chrome profile for it exists on John's laptop (usually asleep).

Blog (adom.inc)

The company blog is where announcements land FIRST; social blurbs and press pitches point back at it.

Publishing process (as of 8/2026): we do not publish it ourselves. Draft it, then hand it to Colby.

1. Write the post as a Google Doc draft.
2. Share it with Colby Knox ([email protected]) as writer, and Dan Huff ([email protected]) for approval.
3. Colby posts it to the adom.inc homepage/blog.
4. Then, and only then, do the social blurbs and press pitches that link to it.

The site is Astro (data-astro-cid-* in the served HTML) and posts live at https://adom.inc/blog/<YYYY-MM-DD-slug>/, e.g. the NSF announcement at /blog/2026-07-22-nsf-awards-adom-10-million/. The source repo has NOT been located from the container yet — if you find it, record it here, but until then the answer to "how do I publish a blog post" is send the draft to Colby, not "find the repo".

Write every post against adom-messaging — tagline, word choices, and the InstaPCB disclosure rule.

Standard rollout order

Blog post published → pitch Dallas Innovates (they cover this beat and Adom is already on their newsletter list) → short blurbs on LinkedIn (company page + John's profile), X (@Adom_Industries), Instagram. Each blurb links back to the adom.inc post rather than restating it.

Press contacts already offering help

• Andrea Duffie, Communication Coordinator, Fort Worth Economic Development ([email protected]) — offered to coordinate quotes from Councilmember Alan Blaylock (District 10) or Robert Allen at the Fort Worth EDP, and to share our posts on the City's own channels. Take her up on it for anything Fort Worth related.
• Brianna Brown, Assistant Economic Development Director; Ryan Pohler, Fort Worth Lab (reporting/compliance on the EDPA contract).

⚠️ Partner agreements can restrict publicity. Before naming a commercial partner (e.g. Keysight) in a post, check the executed agreement for publicity/trademark-use clauses and any required pre-approval.

Standing decisions

• No paid verification. John declined X verification on 8/4/2026. X Premium ($4-8/mo, blue check, reads as an individual subscriber) and Verified Organizations ($200/mo, gold check + affiliate badges) are both not being purchased. Do not propose it again unless John raises it, and never enter payment details. X will keep showing "Get verified" upsells on the profile — ignore them.
• Display name stays "Adom" (the trademark), not "Adom Industries". See adom-messaging.

Rules

1. Passwords stay in Google Contacts — never on this page, never in a repo.
2. Prefer delegation/roles over sharing a password. Grant by role, revoke by role.
3. After a successful login or password change, update the date lines in the matching contact.
4. Before posting to a corporate channel, confirm the ACTIVE handle is the corporate one.
5. Keep John and company identities in separate browser profiles, never one shared session.