Design Protection

← back to homework

Protect the wind sculpture designs: run prior-art and design-patent searches, document each original design with dates, and prepare filings for a licensed attorney. Research and preparation only — never legal advice.

Folder: /mnt/datapool/hermes_workspace/projects/design-protection · scaffolded

Start a session here (paste into a terminal):

cd /mnt/datapool/hermes_workspace/projects/design-protection && hermes

What's in the folder

docs/
log.md

Project notes

Project: Design Protection (design-protection)

Hermes: this file is the context for the Design Protection project assistant.

You are in /mnt/datapool/hermes_workspace/projects/design-protection. Work from here unless told otherwise.

Objective

Protect the wind sculpture designs: run prior-art and design-patent searches, document each original design with dates, and prepare filings for a licensed attorney. Research and preparation only — never legal advice.

Status

What "done" looks like

Each design documented well enough to hand to an attorney: an inventory with dates and photos, a prior-art search record per design, and a written recommendation on which designs are worth protecting and by which route (design patent, copyright, trade dress, or nothing).

Paths (all under this project root)

```

/mnt/datapool/hermes_workspace/projects/design-protection/

.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/design-protection/ —

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. Never give legal advice and never file anything. Output is research and preparation for a licensed attorney, and every recommendation must say so plainly.

6. A prior-art search never proves a design is free to use. Record what was searched, when, and what could not be searched.

Tools, MCP & workgroup

Hermes + delegate_task subagents; web search of USPTO and Google Patents and Copyright Office records; image search for prior art; Google Drive for the design portfolio.

Outputs / deliverables

docs/design-inventory.md, a prior-art search record per design, protection recommendations

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

Session handoff

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

line in /mnt/datapool/hermes_workspace/projects/design-protection/docs/log.md with date + what changed + what's next.

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