aa1d805e04
This repository is the one the template's README describes: 205 issues, zero
milestones, and severity labels spelled "P0 Critical" / "P1 High" / "P2 Medium",
which privacyllc.dev reports as NOT ADOPTED rather than as 87% complete.
Six markdown records described the same work and none pointed at the tracker.
Two of them said the project was in "Phase 5" while the code was at 0.9.3.
Migrated, then deleted in this commit:
FUTURE.md -> docs/history/BATCH_LEDGER.md (Archived). Its open
items were all already filed as issues, so nothing
needed migrating into the tracker
HISTORY.md -> docs/history/DEVELOPMENT_LOG.md, verbatim, 0 lines lost
DEVELOPMENT_LOG.md -> the same file, as a second labelled block. Not
interleaved: the changelog has three duplicated version
headings, so one date order would have implied more
than the record supports
PROJECT.md -> docs/planning/PROJECT_PLAN.md
STRUCTURE.md -> the agent pipeline into README.md; its versioning rules
retired
BUILD_SUMMARY.md -> BATCH_LEDGER.md. Its embedded SQL schema deliberately
NOT carried: it predated the UNIQUE constraint on
leads.email, and server/index.js owns the schema
SCRIPTS.md -> docs/TOOLS.md, corrected for the SSR + prerender build
Moved with history (git detects all four as renames):
OVERHAUL_PLAN.md, review.md, project-requirements.md, docs/zoho-setup.md
Kept because this project earned them: the five-agent pipeline, the design
system in OVERHAUL_PLAN.md (Status: Current, with a front-note saying which half
is history), the positioning argument in REDESIGN_REVIEW.md, and REQUIREMENTS.md
whole, including its change policy.
Deleted from the template because they do not apply, each said out loud in
DOC_TRUST_MAP.md: QA pass I (no money moves), the authorisation checklist group
and the session-token row (no accounts, no sessions), and one PRECAUTIONARY
paragraph in SECURITY.md about holding credentials on behalf of users — there
are none, and PROJECT_PLAN.md records accounts as out of scope. Pass H was kept
and rewritten: its authorisation half does not apply, its what-a-stranger-can-
reach half is the most exposed surface here.
Also removed: main.js, the old static site's hash router, referenced by nothing
and preserved in .drop/; and test-results/.last-run.json, a May Playwright
artifact reading {"status":"failed"} for a suite that does not exist.
The repository was made private on Forgejo before this commit. That is what let
the internal history be committed rather than exempted — null/fruit-fall is
already private and reports normally.
Two defects found on the way in and fixed here: zoho-setup.md told admins to
edit `server/zoho/`, a directory that has never existed in any commit (the
mapping is in server/index.js), and README.md's route list still advertised
/8x8, removed at 0.6.6, while omitting /privacy-policy.
Branding: icon.webp and logo.webp converted from this project's own marks in
assets/. banner.webp is absent and is filed as an issue rather than faked.
Verified: verify.sh 3/3, doc-claims 71 claimed paths all present, backup and a
first-ever restore of the live leads database (2 tables, 3 rows, under 1s).
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
||
|---|---|---|
| .. | ||
| img | ||
| README.md | ||
README.md
Data — Queue North Website
Status: Current
Owner: _null
Last reviewed: 2026-08-18
Governs: docs/data/** — the assets privacyllc.dev renders for this project
Review trigger: A rebrand, or any change to the icon, logo or banner
What goes here
Three files, in img/, at exactly these names:
docs/data/img/icon.webp the square mark, used wherever the project is listed
docs/data/img/logo.webp the full lockup, used on the project page
docs/data/img/banner.webp the wide image, used across the project header
All webp. All required. Only img/ is checked — an asset left in
docs/data/ instead of docs/data/img/ is not found.
Dimensions, weights and how to generate them are in
img/README.md, beside the files they describe. This
document owns the rule; that one owns the spec. Stating both in both places is
how two copies of one convention start disagreeing.
No placeholders ship with this template, deliberately. It carried a 0-byte
logo.webp once, and an empty file is the worst of the three states: a check
that asks "does the path exist" calls it present, and anything that reads the
bytes rejects it — a consumer verifying the webp signature answers 415, which
reads as a corrupt asset rather than a missing one. Absent is honest and the
conformance check reports it as absent, which is what gets it filled in.
Extra sizes and variants are welcome beside them — icon-512.webp,
logo-dark.webp — and are not treated as clutter. Only the three exact names
are checked for.
What is here now
| File | State | Source |
|---|---|---|
img/icon.webp |
present — 512 × 512, 28 KB | assets/icons/logo512.png, the Queue North compass-star mark |
img/logo.webp |
present — 1024 × 1024, 41 KB | assets/logo2.png, the full lockup |
img/banner.webp |
absent | no 3:1 source exists — see below |
Both present files were converted from the project's own existing marks on
2026-08-18, which is using the art the project already had rather than inventing
a placeholder. The source art lives in assets/ at the repository root, which is
where this project keeps exported source files; nothing in the build references
that directory, so do not delete it as dead.
banner.webp needs 2176 × 725 and nothing in the repository is that shape.
assets/JointLogoWhite.png is 4082 × 1066 and close, but it is a joint mark
with a partner, and whether that is the right thing on a Queue North project
header is somebody's decision rather than a conversion. Filed as a P2 issue.
If an asset is missing, open an issue — do not invent one
An agent cannot draw a logo, and this is the one gap in the whole convention that cannot be closed by writing a file.
So when an asset is absent, file an issue rather than producing something:
title it for the asset, label it P2, and end the body with its Verify: line
— Verify: docs/data/img/logo.webp exists and the project card renders it.
Do not generate a placeholder. A placeholder that looks deliberate outlives the issue that would have replaced it: nobody files a ticket against an image that appears to be finished. An obviously absent asset keeps asking.
Why this folder is different from every other one here
The Command Center consumes these. Every other document in this tree is written for a person to read; these are fetched and rendered on privacyllc.dev's project page.
That has one consequence worth stating plainly: this folder cannot be declared
exempt. A repository may tell the conformance check that a required document is
deliberately absent — kept out of git on purpose, say — and the check will
believe it. It will not accept that declaration for docs/data/, because the
result would be a project card with nothing to show and nothing explaining why,
which is the exact failure the check exists to prevent.
Why webp and not PNG
One format, checked by its magic bytes rather than its file extension, so the site can serve it inline with confidence. A file whose first bytes are RIFF/WEBP cannot be an HTML document or an SVG carrying script, which is what makes it safe to render directly rather than forcing a download.
Renaming a PNG to .webp will not work, and is meant not to.
This is not an asset library
Screenshots, mockups, reference art and exported source files do not belong here. They belong wherever the project already keeps them. This folder holds the three marks that identify the project elsewhere, and stays small enough that its contents are obvious at a glance.