Devonshire Digital LLC — Approved Brand Assets¶

This is the canonical record of which Devonshire Digital LLC brand assets are approved, as distinct from files that may exist in brand/company/ but have not been explicitly approved. A file's presence in brand/company/ does not by itself mean it is approved — it must be listed here, with an explicit approval note, to count as approved.

Current state¶

The standalone "D" mark is approved, and so are its live deployed derivatives, siteinfra/assets/logo.png and favicon.png. The Founder approved the mark itself on 2026-07-16 ("This mark is approved to support Devonshire Digital"), after the two-pass geometry correction recorded below, and approved the 2026-07-17 regeneration of logo.png/favicon.png the same day it was produced. See the Asset register for the formal record. No other Devonshire Digital LLC brand asset (wordmark lockup) exists yet.

Provenance of the "D" mark candidate¶

Origin (current geometry, 2026-07-16): C:\Users\Stuart\Downloads\ChatGPT Image Jul 16, 2026, 07_57_41 AM.png (a 1254×1254 white-on-navy render of the mark, supplied by the Founder specifically to redraw the shape with cleaner edges).
Not derived from siteinfra/assets/favicon.png or siteinfra/assets/logo.png — those were lower-resolution, already-rasterized derivatives of an earlier mockup, and logo.png in particular was an unfilled outline-only rendering, unsuitable as a source. Both were downstream of the previous master for a full day after this geometry was approved; regenerated 2026-07-17 — see "siteinfra/assets/logo.png and favicon.png — regenerated" below.
Method (current, two passes, both superseding the GIMP autotrace below): the original method (GIMP 3.2's plug-in-sel2path autotrace) produced bezier curves on edges that should have been straight — wobbly square sides and a wobbly straight-cap-to-curve transition on the "D" glyph — flagged by the Founder on 2026-07-16. The squares were rebuilt as true axis-aligned <rect> elements from pixel connected-component analysis of the reference image and have not needed further revision.
First redraw pass fit a true circle to the "D" glyph's outer/inner curve boundaries via least-squares (outer center ≈(709,615) r≈338, inner center ≈(724,615) r≈186) and joined the circular arc directly to the straight stem-nub with an A command. This still produced a visible bulge/kink: the nub's straight edge is vertical, but the circle's start point (fit to the blurred raster) wasn't at the circle's own horizontal-tangent extremum, so straight met curve at an angle rather than smoothly — flagged by the Founder on 2026-07-16 (same day).
Second, current pass abandoned fitting the raster's blurred edge for the curve (kept it only for the squares and for overall proportions) and instead built the band the way a typeface glyph is constructed: a flat horizontal "shoulder" (~30% of the outer width) hands off to a cubic-Bezier quarter-curve with matched tangents (horizontal at the shoulder, vertical at the rightmost point; kappa≈0.5523 control-point placement), mirrored top and bottom, with a uniform-thickness (~138px) inner band and two short vertical end caps on the left connecting outer and inner boundaries — not a full-height stem, since the stem is what's dissolving into the squares. This is tangent-continuous everywhere, eliminating the kink.
GIMP 3.2 was used only for the raster production step in both passes (Python-Fu batch scripts scripts/gimp_render_svg.py and scripts/gimp_compose_badge.py, both already established by the 2026-07-11 GIMP workflow), never for tracing.
Master file: brand/company/source/d-mark.svg — fill="currentColor", recolor freely; this is the file to edit if the shape itself ever needs to change. viewBox="212 236 885 758" is a tight crop around the mark's content bounding box.
Colorway exports: brand/company/exports/d-mark-{navy,white}.svg and d-mark-{navy,white}-{256,1024}.png (transparent background), plus d-mark-square-badge-navy-256.png (the navy square favicon-style badge, mark centered). Navy uses #0D1B2A (see Navy color reconciliation).
Reference-only files: brand/company/source/d-mark-traced-raw.svg (the unstyled raw GIMP autotrace output from the previous, now-superseded method — kept only as a record of what was rejected and why) and brand/company/exports/d-mark-crop-reference.png (the exact crop of the current 2026-07-16 reference image that the current geometry was derived from) are kept for provenance/re-derivation, not for reuse as final assets.

Navy color reconciliation¶

Two slightly different navies were found in the existing assets: siteinfra/assets/favicon.png's background sampled at roughly #05142C (averaged), the ChatGPT mockup's own navy panel averaged to roughly #031837, and the docs site's chosen brand primary in siteinfra/assets/extra.css is #0D1B2A. All three are dark navies within a similar family, and the gap between them (a handful of units per RGB channel) is consistent with generation/compression/anti-aliasing noise in a raster ChatGPT output and a separately-rendered favicon, not evidence of a genuinely different intended color.

Resolution: #0D1B2A is treated as canonical, because it is the one value that was deliberately chosen, explicitly documented (with a code comment explaining why), and is already live in production — a human-reviewed, committed decision outweighs re-deriving a color from an AI-generated mockup's pixels. All new exports (the "D" mark colorways, favicon.png, logo.png) now use #0D1B2A consistently. This is a working resolution, not a Founder-ratified brand-color policy — if the Founder intended a different exact navy, say so and this gets revisited.

`siteinfra/assets/logo.png` and `favicon.png` — regenerated (2026-07-11, then again 2026-07-17)¶

Both are live docs-site assets (deployed directly, not brand/ masters) and have now been regenerated twice:

2026-07-11 (first regeneration, from the mark as it existed then):

logo.png was previously an unfilled outline-only rendering — nearly invisible against the navy header introduced by the recent header-color fix (commit 6288f51). Replaced with a tightly-cropped, transparent-background white d-mark-white render (628×512).
favicon.png previously used the slightly-off navy noted above and a lower-quality rendering of the mark. Replaced with a navy (#0D1B2A) square badge (256×256), mark at 54,60, sized ~161×131.

2026-07-17 (second regeneration, after the mark's 2026-07-16 geometry redraw and 2026-07-16 Founder approval — the first regeneration above had been left stale against the new geometry, flagged in Still open below until now):

favicon.png: re-rendered via scripts/gimp_compose_badge.py --mark-svg brand/company/exports/d-mark-white.svg --canvas 256 256 --bg-color "#0D1B2A" --mark-size 161 131 --offset 54 60 — the exact same padding/position as the 2026-07-11 version, just against the current, approved "D" geometry.
logo.png: re-rendered from d-mark-white.svg at high resolution, autocropped to the ink bounding box, given ~8% padding on each side (matching the previous file's ~7-10% margins), then scaled to 512px height — 612×512 final. A pixel-exact byte match to the 2026-07-11 crop wasn't attempted (the geometry itself changed on 2026-07-16), but the padding proportion was matched by measurement, not guessed.
Both verified in a live mkdocs build (python siteinfra/build_site.py), viewed in-browser at http://127.0.0.1:8123/ after serving the built devonshire-digital-site/ output: the header logo renders as a crisp solid white mark on the navy header, matching the "D" mark's current approved geometry.

These are ordinary file replacements (same filenames, same usage in mkdocs.yml), not new brand policy — they follow directly from the "D" mark's own 2026-07-16 approval. Approved by the Founder, 2026-07-17 — see the Asset register.

Typography¶

The Founder has selected the following typefaces (2026-07-11), resolving the font-decision blocker noted below:

Montserrat Medium — primary wordmark/logotype weight (this is what the ChatGPT mockup itself suggested for the "DEVONSHIRE DIGITAL LLC" lockup).
Montserrat Regular — small captions and UI labels, where Medium would be too heavy at small sizes.
Inter Regular — business-card-style contact information and other small-print body text.

This is a font selection; as of 2026-07-17 it has also been applied — see "Wordmark lockup" below.

Wordmark lockup — built 2026-07-17¶

The Founder reviewed a live, interactive comparison of lockup candidates (real vector marks, real Montserrat Medium — not flattened mockups) covering case (ALL CAPS vs. mixed), orientation (horizontal vs. stacked), single-line vs. two-line text treatments, and text alignment (left, center, justified). Decisions from that review:

Case: ALL CAPS, for both brands.
Typeface: Montserrat Medium, shared with Devonside Labs (see DD-DIGPROD-ADR-0002's 2026-07-17 amendment) — the Founder was explicit that sharing the typeface family is enough; no additional typographic differentiation between the two brands was requested.
Devonshire Digital LLC, horizontal: two-line, left-aligned — "DEVONSHIRE" / "DIGITAL LLC".
Devonshire Digital LLC, stacked: two-line, justified (the shorter line gets extra letter-spacing to match the longer line's width) — this reads well here because "DEVONSHIRE" and "DIGITAL LLC" are naturally close in length.

Production files (Montserrat Medium glyphs outlined to vector paths — no live font dependency, matching the standalone mark's own convention): brand/company/source/d-mark-lockup-horizontal.svg, d-mark-lockup-stacked.svg, plus navy/white exports in brand/company/exports/. Approved by the Founder, 2026-07-17, after confirming the rendered vector output matched the interactive review — see Asset register.

Color palette — finalized 2026-07-30¶

Per ADR-0018, the full palette is approved, extending the already-approved navy:

Token	Value	Role
Navy	`#0D1B2A`	Primary ground
Navy 800	`#16283B`	Raised surfaces / cards on navy
Slate	`#7C8798`	Secondary text, rules, muted UI
Brass	`#B08D57`	Sparing accent only — seals, dividers, an "approved document" stamp motif
Ivory	`#F2EFE9`	Text on navy; light-mode paper ground
Muted sage	`#8FA98B`	Semantic success

Still open¶

Nothing outstanding for the color palette. Remaining open items for this venture's brand identity are tracked in brand-architecture.md, not here.

Asset register¶

Asset	Type	Source file	Export file(s)	Approved by	Approved date	Notes
"D" mark (standalone)	Vector mark, two colorways	`brand/company/source/d-mark.svg`	`brand/company/exports/d-mark-{navy,white}.svg`, `d-mark-{navy,white}-{256,1024}.png`	Founder	2026-07-16	Approved after the two-pass curve correction (see Provenance above). Navy color reconciled to `#0D1B2A`.
`siteinfra/assets/logo.png` (docs-site header logo)	PNG, deployed derivative	derived from `d-mark.svg` (white)	—	Founder	2026-07-17	Live on the docs site. Regenerated 2026-07-17 from the approved "D" geometry (autocropped, ~8% padding, 612×512).
`siteinfra/assets/favicon.png` (docs-site favicon)	PNG, deployed derivative	derived from `d-mark.svg` (white) + `#0D1B2A` navy badge	—	Founder	2026-07-17	Live on the docs site. Regenerated 2026-07-17 from the approved "D" geometry, same padding/position (`54,60`, `161×131`) as the prior version.
"D" mark wordmark lockup, horizontal	Vector, two-line left-aligned	`brand/company/source/d-mark-lockup-horizontal.svg`	`brand/company/exports/d-mark-lockup-horizontal-{navy,white}.svg`	Founder	2026-07-17	Selected from an interactive review of case/orientation/alignment candidates; Montserrat Medium outlined to vector paths.
"D" mark wordmark lockup, stacked	Vector, two-line justified	`brand/company/source/d-mark-lockup-stacked.svg`	`brand/company/exports/d-mark-lockup-stacked-{navy,white}.svg`	Founder	2026-07-17	Justified alignment works here since "DEVONSHIRE" and "DIGITAL LLC" are naturally close in width.

How an asset gets added here¶

A candidate asset is produced (e.g. via the GIMP workflow tracked in work/active/2026-07-11-brand-assets-and-gimp-workflow.md) and placed under brand/company/source/ and/or brand/company/exports/.
The Founder reviews and explicitly approves it.
Only then is a row added to the Asset register above, recording the approval. An agent may draft a proposed row (e.g. after producing a candidate export) but must not mark it approved — per this repository's operating rules, only a human approves.

Report an issue about this page