Additional Task Layer: Review-gated posting assistant using Chrome/browser sessions

Add a review-gated external posting workflow for Sol-37 visibility.

The system may recommend posts for external platforms, draft them, and prepare them for publication. However, it must not publish anything automatically without explicit user review and approval.

Core workflow:

1. Analyze the site content and visibility goals.
2. Recommend specific external posts.
3. Present each recommended post to the user for review.
4. Wait for explicit approval.
5. After approval, use the available Chrome browser window and any already-authenticated accounts in the sandbox/browser environment to publish or schedule the approved post.
6. Record what was posted, where it was posted, when it was posted, and what canonical Sol-37 URL it referenced.

Important safety rule:

Never post, comment, message, edit a profile, join a community, follow accounts, send DMs, or submit forms without explicit user approval for that specific action.

Use the browser only through accounts the user has already intentionally granted access to in the sandbox/browser environment. Do not ask for, store, reveal, extract, or transmit passwords, session cookies, tokens, recovery codes, or private credentials.

Recommended posting queue:

Create a file such as:

`VISIBILITY_POSTING_QUEUE.md`

or structured data such as:

`visibility-posting-queue.json`

Each proposed post should include:

* Status: `draft`, `needs_review`, `approved`, `posted`, `skipped`, or `failed`
* Platform
* Target community/account/publication
* Recommended timing
* Post title
* Post body
* Suggested tags/hashtags
* Canonical Sol-37 URL
* Supporting internal links
* Intended audience
* Reason for posting
* Risk level: low / medium / high
* Platform rule notes
* Whether images are needed
* Browser action required
* Final posted URL, once available

Recommended platforms:

* Reddit
* Medium
* Substack
* Fandom or wiki-style platforms
* Mastodon
* Bluesky
* Tumblr
* GitHub README/discussions, if applicable
* Personal blog mirrors
* Other platforms already available through the browser session

Do not treat every platform the same.

For Reddit:

* Do not link-dump.
* Identify the subreddit’s rules before drafting.
* Prefer discussion-first posts.
* Avoid posting the same content repeatedly across many subreddits.
* Include the Sol-37 link only when genuinely relevant.
* Recommend comments or participation before self-promotion where appropriate.

For Medium/Substack:

* Create polished explanatory companion essays.
* Link back to the canonical Sol-37 page.
* Avoid copying the entire site page verbatim unless syndication/canonical handling is intentional.
* Use clear titles like:

  * “What Is Möbius Cosmology?”
  * “Why Every Concept in a Digital Archive Needs Its Own URL”
  * “Sol-37 as a Public Archive Shell”
  * “Building a Speculative Cosmology Glossary for Humans and AI Search”

For Fandom/wiki-style platforms:

* Recommend only if there is enough lore/project structure to justify it.
* Create neutral, structured entries.
* Do not pretend the project is independently notable unless independent sources exist.
* Prefer a first-party `/wiki/` section if strengthening `sol.system42.one` is the priority.

For GitHub:

* Improve README files, documentation, project descriptions, and public archive notes.
* Add canonical links to the live site.
* Add a glossary and sitemap-style project overview.

Browser automation instructions:

If browser automation tools are available, use them cautiously.

Preferred browser workflow:

1. Open the target platform.
2. Verify the user is logged into the intended account.
3. Navigate to the correct posting area.
4. Fill in the approved title/body/tags/link.
5. Pause before final submission.
6. Ask the user for final confirmation if the action will immediately publish.
7. Submit only after confirmation.
8. Capture the resulting URL.
9. Update the posting queue/report.

If the platform has a draft mode, prefer saving as a draft unless the user explicitly approves immediate publication.

Approval language:

The system must require explicit approval such as:

* “Approved to post this exact draft to Reddit in r/worldbuilding.”
* “Approved to publish this Medium draft.”
* “Approved to submit this comment.”
* “Approved to save this as a draft, but do not publish.”

Vague approval is not enough for publishing.

Do not interpret general enthusiasm, brainstorming, or “looks good” as permission to publish unless the user clearly names the platform/action.

Suggested output format for recommendations:

For each recommended post, present:

* Platform:
* Target:
* Purpose:
* Draft title:
* Draft body:
* Link:
* Why this helps:
* Risk / caution:
* Requested action:

Example:

Platform: Reddit
Target: r/worldbuilding
Purpose: Discussion post introducing Sol-37 as an archive/worldbuilding structure, not an advertisement.
Draft title: “How do you structure a fictional archive so each concept can stand alone?”
Link: `https://sol.system42.one/...`
Risk: Medium, because Reddit communities dislike self-promotion.
Requested action: Review, revise, approve, or skip.

Final reporting:

Create or update:

`VISIBILITY_REPORT.md`

Include:

* Recommended posts
* Approved posts
* Posted links
* Skipped posts
* Failed attempts
* Platform notes
* Future posting opportunities
* Warnings about communities where posting would be inappropriate
* Changes made to the site to support external posting

Success criteria:

The system is successful if it can:

* Recommend platform-specific posts.
* Draft them in a non-spammy way.
* Ask for user review.
* Use the existing browser session only after approval.
* Publish or save drafts through Chrome when explicitly authorized.
* Track what happened.
* Avoid credential handling.
* Avoid promotional spam.
* Preserve the Sol-37 voice without making it sound like SEO paste wearing a trench coat.