# Publishing Sites Map

Last updated: 2026-05-25

## Purpose

This file defines Bert's publishing lanes so editors, agents, and future automation do not blur audiences, voice, confidentiality, or publication targets.

## Sites

### 1. Barely, But Here

- URL: https://berchman.substack.com
- Platform: Substack
- Primary role: Barely, But Here publication and world
- Editorial owner model: dedicated BBH-only editorial agent
- Publishing cadence target: 2x/week, Sundays and Thursdays
- Scope:
  - BBH essays/articles
  - BBH archive resurrection
  - BBH memory candidates
  - BBH voice continuity
  - BBH audience relationship
- Not for:
  - technical blog posts
  - software project details
  - general BertMahoney.com professional writing
  - personal-site miscellany unless it is explicitly BBH-world material

### 2. BertMahoney.com

- URL: https://bertmahoney.com/weblog
- Platform: WordPress
- Primary role: professional / technical blog
- Scope:
  - AI memory systems
  - Hermes / Open Brain / agent architecture
  - open-source and local-first workflows
  - technical process writing
  - professional positioning
  - technical product/service writing
- Tone target:
  - technical-public
  - practical and opinionated
  - manifesto energy allowed when tied to architecture, autonomy, ownership, open source, and avoiding platform lock-in

### 3. Berchman.com

- URL: https://berchman.com/berchman-artist-designer-technologist/web-log_stories_by_bert
- Platform: WordPress
- Primary role: personal long-running website since 1996
- Scope:
  - personal essays
  - artist/designer/technologist continuity
  - long-view identity writing
  - memoir/process/art/life notes
  - less technical but still allowed to be intellectually serious

### 4. Bert.forsale

- URL: https://bert.forsale
- Platform: WordPress + WooCommerce + Stripe
- Primary role: store / commercial hub
- Scope:
  - software sales
  - art sales
  - future products/offers
  - landing pages
  - product descriptions
  - checkout/support copy
- Special handling:
  - Commercial claims must be accurate.
  - Product pages for unreleased software must not leak details before launch.
  - Store operations require extra care with WooCommerce, Stripe, tax/shipping/payment settings, and customer data.

## Global confidentiality rule

Public writing may name technologies in use unless Bert says otherwise.

However, in-development software products must stay at the 100,000-foot level before launch:

- Do not publish product names.
- Do not publish repo names.
- Do not publish specific feature sets.
- Do not publish implementation details.
- Do not publish screenshots or architecture that reveal the idea.
- Do not publish monetization details or launch plans unless approved.

Safe phrasing example:

> I used Hermes and local agent workflows to move several small software projects into clearer next-step states.

Unsafe phrasing example:

> I used Hermes to improve [specific unreleased product name], a tool that does [specific idea].

## SEO baseline for all public posts

Each publishable piece should include:

- working title
- SEO title variant
- meta description / excerpt
- slug suggestion
- primary keyword
- secondary keywords
- tags/categories
- internal link opportunities
- external link opportunities if useful
- social/share blurb
- confidentiality check

## Future roadmap: agent-discoverable assets

Longer-term goal: make Bert's online assets discoverable by agents and humans.

Candidate future work:

- Create per-site content indexes.
- Publish machine-readable feeds/sitemaps where appropriate.
- Explore MCP servers over:
  - BBH catalog
  - BertMahoney.com posts
  - Berchman.com archive
  - store/product catalog
- Preserve permissions and privacy boundaries.
- Use provenance: every discoverable record should identify source URL, date, title, and canonical owner.