YahHeard
What the work is for, and the rules it is held to. Each principle comes with the things it rules out, because a principle that rules nothing out is a slogan.
These apply to every project, and they show up in the code.
Local storage is the primary store, not a cache. A project should do its whole job with the aeroplane-mode switch on.
Rules out
Saves are versioned, checksummed and written atomically, with a backup kept. A corrupt file is reported, never silently treated as valid.
Rules out
Status, permissions, limitations and the way each image was captured are stated plainly — including the unflattering parts. This site will not build if a project claims a store listing it does not have.
Rules out
Contrast, text scaling, reduced motion, colour-blind palettes, keyboard access and screen-reader labels are designed in from the start rather than added before release.
Rules out
No analytics, advertising or tracking SDKs unless there is a real reason, stated openly. Permissions are requested only when the feature that needs them is used.
Rules out
Reminders are gentle and optional, and nothing is designed to keep someone scrolling. Neglect never deletes progress in a game.
Rules out
Health, safety and paranormal-themed projects carry explicit, prominent non-claims and point to official sources.
Rules out
Original or procedurally generated art and sound, and correctly licensed photography with its credit travelling alongside it.
Rules out
Projects are built with AI assistants alongside ordinary engineering practice. The decisions, the reviews and the responsibility stay with a person, and the tools used are stated openly.
Rules out
