Workbench Repo Brand Uplift

Source Standard

• tactical telemetry over marketing copy;
• strong project name, short claim, visible proof, then navigation;
• industrial grid language: sparse sections, tight labels, mono metadata, restrained badges, sharp boundaries;
• public/private boundary stated clearly;
• evidence links before long narrative;
• no mascots, lore, fake momentum, private screenshots, raw logs, or internal run IDs in public docs.

When To Use

• README or repo-front-page polish;
• public repo metadata, topics, social-preview, examples, screenshots, or demo link updates;
• turning an internal workbench-quality repo into a public adoption surface;
• matching Evensong/Zonic visual and trust quality across multiple repos;
• "senior dev README uplift", "brand design", "make this repo public-ready", "adopt zonicdesign.art", or similar requests.

Brand Gates

Workflow

1. Inspect live repo state:

   pwd

   ,

   git status --short --branch

   ,

   git remote -v

   .
2. Read current

   README.md

   , package metadata, docs map, examples, and public assets only as needed.
3. Identify the strongest available proof. If proof is missing, add a clear "needs proof" residual risk instead of inventing one.
4. Draft the README around proof, not vibes:
   • name and claim;
   • status badges only if accurate;
   • public screenshot/demo/CLI evidence;
   • quickstart;
   • architecture map;
   • examples;
   • maturity and safety boundary;
   • contribution path.
5. Update adjacent public surfaces when relevant: package description, topics recommendation, docs links, examples, and public image references.
6. Run touched-path checks. At minimum:

   git diff --check

   , link/file existence checks for local docs, and repo-specific build/test commands if README quickstart changed.
7. If this is part of Workbench public docs or skill sync, route the patch through

   workbench-hermes-docs-sync

   .

Zonic GitHub Pattern

# PROJECT NAME

> One sentence: what it is, who uses it, and why it matters.

[status badges]

## Public Proof

- Live demo:
- Screenshot / CLI output:
- Latest verified command:

## Quickstart

```bash
...
```

## System Map

| Surface | Path | Purpose |
| --- | --- | --- |

## Maturity

| Surface | State | Notes |
| --- | --- | --- |

## Contributing / License

Verdict Contract

REPO_BRAND_UPLIFT
repo:
brand_dna_source:
target_audience:
public_surfaces_checked:
proof_used:
changed:
metadata_recommendations:
verification:
residual_risk:
next_repo_or_next_action:
VERDICT: PASS | FLAG | BLOCK

PASS

FLAG

BLOCK