Skip to content

Bring the design brief into the repo - #6

Open
XxHugheadxX wants to merge 1 commit into
mainfrom
docs/design-brief
Open

XxHugheadxX wants to merge 1 commit into
mainfrom
docs/design-brief

Conversation

@XxHugheadxX

Copy link
Copy Markdown
Contributor

Docs only. No code, no CI, no conflict with anything in flight.

Why

The design brief was written on 22/08 and lived in a downloads folder on one machine. Nobody could cite it in a review, and nobody could notice when it stopped being followed.

That is the actual root cause of the visual drift — not anyone ignoring it. The first implementation of the app (efafde2) matched the brief closely: navy: '#0D47A1' against the brief's --trazo #0E47A1, one hex digit apart. af42c9d then replaced the whole system with 8-bit cyan, and no reviewer had a document to point at.

What this does and does not do

Does: files the brief unedited, records the drift with the hex evidence, and states who is responsible for what.

Does not: decide anything. Which direction the design takes is an open conversation and this PR deliberately leaves it open.

The language trap, headed off early

The brief names its tokens in Spanish — tinta, hueso, trazo, senal — and AGENTS.md requires English for every identifier in code. This exact mismatch already cost the project once: the plan froze the contract as escanear/transmitir while the code shipped scan/beacon, and an arbitration paragraph had to be added to AGENTS.md afterwards.

So the README carries a mapping, and flags one collision worth catching before someone writes it two different ways: the brief's senal would naturally become signal, and frontend/src/api/mock-data.js already uses signal for a peer's signal strength. Two different things, same name.

Note

The README also records, without fixing, three Spanish identifiers in frontend/src ('local-propio', propio: true, 'z32milocalpropio') that date to efafde2 and contradict AGENTS.md. They belong to whoever owns that folder — flagged, not touched.

🤖 Generated with Claude Code

https://claude.ai/code/session_01V9zUvsS38fU1M1hT9yFK6j

The brief was written on 22/08 and lived in a downloads folder, so nobody
could cite it in a review or notice when it stopped being followed. That is
the root cause of the visual drift, not anyone ignoring it: af42c9d replaced
a palette that matched the brief almost exactly (navy #0D47A1 against trazo
#0E47A1) with an 8-bit system, and no reviewer had a document to point at.

Files the brief unedited and records the drift with the hex evidence. It
decides nothing -- which direction to take is still an open conversation.

Also heads off a language trap before it costs anything. The brief names its
tokens in Spanish, and AGENTS.md requires English in code; the same mismatch
already forced an arbitration paragraph when the plan said escanear/transmitir
and the code said scan/beacon. Includes a mapping, and flags that the brief's
`senal` would become `signal`, which mock-data.js already uses for peer signal
strength.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01V9zUvsS38fU1M1hT9yFK6j

This branch has not been deployed

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant