Skip to content

brand: use the selected Open Herd icon-only organization avatar #18

Description

@PeterGuy326

Current decision — R2: Open Herd icon only (2026-09-09)

The owner explicitly selected the icon from bytefolk-concept-c-open-herd.svg: the open-herd-mark group, without the ByteFolk wordmark. This direction supersedes R1's minimal monochrome horned B. The attempted R1 restoration earlier on 2026-09-09 was an assistant source-selection error, not an owner request to revert the design.

Status: in-progress. The owner authorized the live avatar correction directly. Canonical repository assets and reproduction instructions must now follow this selection; no further restoration from the old black B asset is authorized by R1.

R2 requirements

  • REQ-001: Use the exact Open Herd icon geometry from the owner's selected SVG. The existing bytefolk-concept-c-open-herd-mark.svg is the icon-only equivalent: 4 paths and 5 rectangles, with no text element.
  • REQ-002: Preserve the selected blue #1677ff, purple #722ed1, ink #141414, and white #ffffff; do not redraw, recolor, or stretch the mark.
  • REQ-003: Export an opaque white 1024 × 1024 PNG with proportional scaling, centered padding, and no wordmark. Apply that PNG as the centralized organization avatar under the owner's direct instruction.
  • REQ-004: Correct canonical export documentation and validation so they cannot silently restore the superseded black B. Preserve all unrelated organization settings and profile copy.

R2 acceptance criteria

  • AC-001: XML comparison proves all 9 icon elements equal the selected source after expanding fill variables; the avatar SVG contains no text.
  • AC-002: The upload PNG is opaque RGB, 1024 × 1024, with a white background and the original icon's aspect ratio and palette. Visual inspection confirms no lettering and sufficient crop padding.
  • AC-003: Repository source, raster artifact, render command, documentation, and validation agree on Open Herd. Governance checks and whitespace validation pass on the candidate head; normal review and CI apply before merging repository changes.
  • AC-004: The owner-settings UI confirms successful upload. Download and inspect the public avatar after the change; record actual hashes and dimensions. GitHub may keep the same avatar URL and resize/re-encode the image, so neither URL change nor pixel equality to the 1024 px source is asserted.
  • AC-005: Record before/after protected public organization fields and verify no unrelated fields changed. Keep this issue open until remaining repository alignment and product acceptance are complete.

Source identity

Repository alignment: PR #31, head 94766dca09dcc30c1bbbe0fd0f788a1a48866fdd. The original Open Herd SVG, icon-only SVG, and exact uploaded PNG are now published in that candidate. They are not yet merged to main.

Icon-only SVG SHA-256: f7d58df169d6270ff40da11b038d64d6f7c5f7435851eb32f2fe1554c578f32a.

R1 material below is retained as historical evidence only. Its old asset selection and monochrome requirements do not govern current avatar operations.

Historical R1 — superseded by R2

Problem

ByteFolk now has an approved public name and organization profile, but the GitHub organization still lacks an intentional, repository-backed avatar. The selected visual direction is the minimal one-color horned B symbol. Without a canonical asset and usage rules, the live organization image can drift from the brand source or become unreadable across light and dark surfaces.

Desired outcome

The ByteFolk organization uses one simple, recognizable avatar everywhere GitHub renders the centralized organization profile picture, and the .github repository contains the exact scalable source, upload artifact, reversed variant, horizontal lockup, and concise usage rules needed to reproduce it.

Approved direction

R1 — Minimal horned B

  • One-color geometric symbol derived from the capital B.
  • Two block horns retain the cow/horse/digital-employee character connection.
  • The extended lower bowl hints at an animal muzzle without illustration details.
  • The organization upload uses a black symbol on an opaque white square so it remains legible in both GitHub light and dark themes.
  • The full-body mascot remains a separate expressive asset and is not used as the organization avatar.

Requirements

  • REQ-001: Store the approved ByteFolk symbol and its reproducible organization-avatar export in the canonical .github repository.
  • REQ-002: Keep the symbol structurally valid in primary, reversed, and horizontal lockup contexts without adding gradients, shadows, mascot detail, or extra colors.
  • REQ-003: Apply the exact approved PNG to the centralized bytefolk GitHub organization profile after merge and successful push/main validation.
  • REQ-004: Preserve the organization handle, repository names, permissions, pins, descriptions, profile copy, member avatars, and all unrelated settings.

Acceptance criteria

  • AC-001: The repository contains a responsive primary SVG, reversed SVG, horizontal lockup SVG, and opaque 1024×1024 PNG generated from the same symbol geometry.
  • AC-002: SVGs parse successfully, contain no embedded raster image, gradient, filter, script, external resource, or fixed root dimensions, and remain recognizable at 16, 32, 64, and 512 pixels.
  • AC-003: The PNG is exactly 1024×1024, RGB/RGBA, opaque, and has a white background with the approved black one-color mark and sufficient circular-crop padding.
  • AC-004: Brand usage documentation records clear space, minimum sizes, primary/reversed usage, exact colors, the avatar export command, and prohibited modifications.
  • AC-005: Repository governance validation and git diff --check pass on the exact PR head.
  • AC-006: After merge and green push/main validation, an organization owner uploads the exact tracked PNG through GitHub Organization Settings.
  • AC-007: Authenticated API and anonymous-page readback show a changed organization avatar_url; downloading that URL produces pixels matching the tracked PNG after GitHub's expected resizing/cropping, while protected non-avatar organization fields remain unchanged.

Scope

Included: canonical brand assets and usage notes in .github, deterministic raster export, the centralized GitHub organization avatar update, and post-change readback.

Non-goals

  • Changing personal member avatars.
  • Assigning separate avatars to repositories or teams.
  • Changing the organization handle, name, description, pins, repository metadata, profile copy, permissions, topics, visibility, or product branding.
  • Replacing the full-body mascot or defining product-specific icons.

Validation plan

  1. Parse and lint every SVG and check prohibited constructs.
  2. Render the primary symbol at 16, 32, 64, 512, and 1024 pixels; verify dimensions, opacity, palette, and circular-crop padding.
  3. Run repository governance validation and git diff --check.
  4. Merge only after required CI and independent review pass.
  5. Record the before-state organization JSON and current avatar URL; upload the exact tracked PNG in GitHub Organization Settings.
  6. Read back the organization API and anonymous organization page, download the served avatar, compare its perceptual/structural pixels with the tracked source, and verify unrelated protected fields are unchanged.

Risk and rollback

Risk is limited to public brand presentation. Preserve the previous avatar URL and before-state JSON. If acceptance fails, restore the previous image only when the current avatar still matches this change; do not overwrite a concurrent owner update.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentationpriority:p0Required for the next shared product proofstatus:readyScope and acceptance criteria are ready for implementation

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions