Sculpture Sales and Marketing

← back to homework

Sell wind sculptures: find and reach buyers, price the work, and build a marketing presence. Scoped to the sculptures, not the book.

Folder: /mnt/datapool/hermes_workspace/projects/sculpture-sales-and-marketing · scaffolded

Start a session here (paste into a terminal):

cd /mnt/datapool/hermes_workspace/projects/sculpture-sales-and-marketing && hermes

What's in the folder

docs/
log.md

Project notes

Project: Sculpture Sales and Marketing (sculpture-sales-and-marketing)

Hermes: this file is the context for the Sculpture Sales and Marketing project assistant.

You are in /mnt/datapool/hermes_workspace/projects/sculpture-sales-and-marketing. Work from here unless told otherwise.

Objective

Sell wind sculptures: find and reach buyers, price the work, and build a marketing presence. Scoped to the sculptures, not the book.

Status

What "done" looks like

A working sales pipeline: a written audience and pricing model, a photo-and-story listing for at least one finished piece, and outreach actually sent to named galleries or buyers with replies tracked.

Paths (all under this project root)

```

/mnt/datapool/hermes_workspace/projects/sculpture-sales-and-marketing/

.hermes.md this file — auto-loaded project rules

README.md human quickstart (how to start THIS assistant)

src/ source code for the project

scripts/ runnable one-off scripts + generated tools

schemas/ JSON schemas for every custom tool (<name>.schema.json)

output/ generated artifacts, reports, exports

docs/ notes, decisions, references

venv/ per-project Python venv (created on demand)

```

Shared, project-independent facts (host, storage, runtime) live in

/mnt/datapool/hermes_workspace/ENVIRONMENT.md — read it instead of assuming.

Working rules

1. Save every generated script, schema, and output under /mnt/datapool/hermes_workspace/projects/sculpture-sales-and-marketing/ —

never leave artifacts in ~ or the scratch dir.

2. Every custom tool ships as two files in the same change:

scripts/<tool_name>.py and schemas/<tool_name>.schema.json.

Copy the working pair at /mnt/datapool/hermes_workspace/templates/example_tool.py +

example_tool.schema.json as the starting shape: pure function, stdin JSON →

stdout JSON, no side effects on import.

3. Test before marking anything complete. No Docker here: use

/usr/bin/python3 -m venv venv && ./venv/bin/pip install ... (bare python3

in a Hermes session is Hermes' own runtime and has no pip), or run the script

and show real output. Paste actual command output, never a description of it.

4. Keep terminal explanations to a single copy-and-pasteable command per step.

5. No outreach counts as done without a record of what was sent, to whom, and when — keep it in docs/outreach.md.

Tools, MCP & workgroup

Hermes + delegate_task subagents; web search for galleries, art fairs and pricing comparables; image generation for marketing imagery (confirm configured first); Google Workspace (Gmail/Drive) for outreach.

Outputs / deliverables

docs/audience.md, docs/pricing.md, listing copy and photos per piece, docs/outreach.md

Environment

Shared Environment — 3050 / T130 (single source of truth)

This block is injected into every project's .hermes.md by bin/new-project, so

host facts live in ONE place. Update here, not per project.

(cifs, vers=3.1.1, uid/gid 1000, rw). There is NO /mnt/t130_storage on this host.

⚠ Inside a Hermes session, bare python3 resolves to Hermes' own bundled runtime

(3.14.7) which has no pip — python3 -m pip install x fails with

"No module named pip". Always build project venvs explicitly:

/usr/bin/python3 -m venv venv && ./venv/bin/pip install ...

2.5.4 (cp314 wheel) and tokenizers 0.23.3 all resolve — the HF/MCP stack is fine

on this Python, no downgrade needed.

Version control & backup

mandatory on the SMB share, not cosmetic: core.filemode=false (the share forces

0755) and core.trustctime=false — CIFS ctimes are unreliable, and with them

trusted git add can treat a just-written file as unchanged and commit a **stale

blob**. Commit when a unit of work is finished:

cd /mnt/datapool/hermes_workspace && git add -A && git commit -m "...", then

confirm git status --short is empty — if it still lists files, re-add and commit

again before trusting the commit.

gdrive:3050-HOME/hermes_workspace (one-way up, .git included, so the

Drive copy is a real clonable repo). Script ~/.hermes/scripts/backup_hermes_workspace.sh,

log ~/.hermes/cron/output/hermes-workspace-backup.log. It prints nothing on

success and pings Telegram only on failure.

rclone sync against a missing mount would delete the Drive copy, so it gates

on the mount, a sentinel file, and a minimum file count, and caps deletions.

job (sync_to_drive.sh, which covers $HOME/{book,hermes-3050,agent-os,projects,bookapp}).

Two sync jobs touching one tree is how you get conflicts.

Verified against live command output 2026-10-30. Re-verify with:

hostname; ip -4 addr; mount | grep datapool; python3 -V; node -v; docker --version

Shared reference sites

Sites Mike flags as worth knowing live in one place for every project:

/mnt/datapool/hermes_workspace/REFERENCE-SITES.md.

Two are recorded as of 2026-11-08, and **both are channels and market evidence, not

sources of facts or prices**:

Décor-scale, so not a price comparison. It credits individual artists by name, which

makes it a possible place to be featured — confirm a submission route first.

dated installation log. Most useful thing in this project's file: it names real

buyer categories with real examples — public/municipal art, corporate campuses,

sculpture parks and museums, institutions (sometimes by donation). That is direct

evidence for the open question in docs/audience.md (who actually buys this?).

It also suggests a habit worth copying: treat every installation as news.

Neither has been used to reach anyone yet. Mike's rule holds: **no outreach counts as

done without a record of what was sent, to whom, and when.**

a channel. It is the blog of a stainless-steel sculpture factory** that sells kinetic

wind sculpture direct, including a "large metal kinetic wind spinners" line — the same

category Slow Bloom belongs to, at factory scale. **It is the most useful pricing

reference collected so far, and the one to check before putting a number on Slow Bloom.**

No price has been captured yet; **read their product pages and record a real figure

before this is cited anywhere.** Its taxonomy (wind / mechanical / light / interactive /

water / bio-kinetic) and its definition are usable language for describing the work.

Its history section is uncited marketing — do not reuse its dates.

Session handoff

When work stops: update Status (state + next step) in this file, then log one

line in /mnt/datapool/hermes_workspace/projects/sculpture-sales-and-marketing/docs/log.md with date + what changed + what's next.

Built live from your own files — nothing here is typed by hand.