design canon — define scope #93

New issue

Open

opened 2026-09-08 18:20:20 +00:00 by peterswimm · 2 comments

peterswimm commented

2026-09-08 18:20:20 +00:00

Owner

No canon document exists in the repo.

Scope is undefined as written — the originating wish is the two words "design canon".
Needs a sentence of intent before it is actionable. Candidate readings:

a written statement of the aesthetic position (the <frontend_aesthetics> block in
CLAUDE.md is currently the de-facto canon, but lives in agent instructions rather than
as a design document), or
fold into the product names / logos / taglines register.

Mirrored from forge wish 55c615b5; flagged at mirror time as needing scope.

No canon document exists in the repo. **Scope is undefined as written** — the originating wish is the two words "design canon". Needs a sentence of intent before it is actionable. Candidate readings: - a written statement of the aesthetic position (the `<frontend_aesthetics>` block in `CLAUDE.md` is currently the de-facto canon, but lives in agent instructions rather than as a design document), or - fold into the product names / logos / taglines register. Mirrored from forge wish `55c615b5`; flagged at mirror time as needing scope.

ville commented

2026-09-28 10:17:50 +00:00

Member

Decided: "design canon" is the official visual design document for Toilville — a human-readable document defining how Toilville products should look and feel, why, and the shared visual/design principles they follow.

The <frontend_aesthetics> block in brand/CLAUDE.md is source material for it, not a second rule set — it's the current de-facto canon, just not written as a document yet.

Goal: the canon becomes the authoritative document; CLAUDE.md refers to it rather than duplicating it, so the two can't drift apart.

Not folding this into the product names/logos/taglines register (#90) — that's a separate document.

Scope is confirmed here. Not starting the write-up or restructuring yet.

**Decided: "design canon" is the official visual design document for Toilville** — a human-readable document defining how Toilville products should look and feel, why, and the shared visual/design principles they follow. The `<frontend_aesthetics>` block in `brand/CLAUDE.md` is source material for it, not a second rule set — it's the current de-facto canon, just not written as a document yet. Goal: the canon becomes the authoritative document; `CLAUDE.md` refers to it rather than duplicating it, so the two can't drift apart. Not folding this into the product names/logos/taglines register (#90) — that's a separate document. Scope is confirmed here. Not starting the write-up or restructuring yet.

👍 1

peterswimm self-assigned this

2026-09-28 16:49:54 +00:00

peterswimm referenced this issue

2026-10-04 20:20:20 +00:00

Rituals: house-style views over ritual events, with user lenses #177

peterswimm commented

2026-10-20 15:09:17 +00:00

Author

Owner

Approved (2026-10-20): ville's scope stands. The design canon is the official human-readable visual design document for Toilville, separate from the names register (#90).

Acceptance:

The document exists under Brand/.
CLAUDE.md's frontend_aesthetics block links to it instead of duplicating it, so the two can't drift.

@ville, the write-up is yours as design authority. I'm on this issue for review.

**Approved (2026-10-20):** ville's scope stands. The design canon is the official human-readable visual design document for Toilville, separate from the names register (#90). Acceptance: - The document exists under `Brand/`. - `CLAUDE.md`'s `frontend_aesthetics` block **links** to it instead of duplicating it, so the two can't drift. @ville, the write-up is yours as design authority. I'm on this issue for review.

ville was assigned by peterswimm

2026-10-20 15:09:37 +00:00