# Silver Signal interface copy

Write interface text like a maintained 1990s reference program or desktop help
system. Function is more important than brand voice. The period feeling comes
from short labels, visible status, ordinary controls, and clear task order—not
slang, fake errors, or deliberately obsolete behavior.

## Rules

- Name the page or function in the main heading.
- Put status before explanation: `LOGIN REQUIRED`, `NOT CONNECTED`, `SAVED ON
  THIS DEVICE`, or `SETUP PENDING`.
- Follow status with the next available action.
- Use short control verbs: `Open`, `Search`, `Save`, `Copy`, `Download`,
  `Clear`, `Return`, and `Sign in`.
- Prefer literal terms to brand voice. Avoid journeys, invitations to discover,
  care metaphors, conversational filler, and claims that a screen is quiet,
  gentle, delightful, or empowering.
- Keep one job per paragraph. Remove adjectives that do not change the job.
- State prices, dates, limits, storage locations, and unavailable functions
  exactly.
- Keep the implementation responsive, keyboard accessible, and readable on
  small screens. Do not imitate obsolete technical limitations.

Privacy, billing, consent, health, emergency, and security notices use current,
precise language. Curriculum articles may use a teaching voice; these rules
apply primarily to navigation, headings, instructions, buttons, notices, and
product descriptions.
