market-standardslisted

# market-standards **The system has a writing standard and no market standard.** `build-application` knows how a sentence should read; nothing knows **how long a CV should be, whether education stays on it, whether a cover letter is expected at all, or what a regulator requires of an accurate one.** 🔴 **All four of those answers change with country, level, industry and target role.** A US one-page résumé convention applied to a director-level application in Europe is simply wrong, and until this skill runs, nothing in the system knows that. ## What it writes **Four pages in `vault/wiki/`.** `type: synthesis`, `section: career`, `stale_after` six months out. | Page | Covers | |---|---| | `CV Layout and ATS Standards.md` | Length, structure, section order, typography, PDF vs DOCX, what each ATS actually does with the file, layout by level | | `Cover Letter Standards.md` | Whether one is expected at all, length, structure, tone, the form-field variant | | `LinkedIn Profile Standards.md` | Headline, About, skills, visibility settings, what is searchable | | `<Board> Profile and Sourcing Standards.md` | The boards that matter **in this user's country** — see below | 🟡 **These are reference pages, not deliverables.** They live in the vault, they are never committed, and they are read by other skills rather than by the user. **Cross-link all four to each other** so they resolve as a set. 🔴 **Filenames must not collide with the user's own pages.** A vault may already hold `