Skip to brand kit
Silver Signal Interface Specifications

SILVER SIGNAL / PUBLIC BRAND KIT / REVISION 1.0

Silver Signal Interface Specification

This document defines the visual and interface rules for lessons, research tools, community pages, and AI-assisted tools. It uses late-1990s software conventions for legibility and visible structure.

STATUS
Public
OWNER
Silver Signal
SCOPE
Web + product UI
BASE UNIT
4 pixels
9 color tokens3 type roles1 interface language

HANDOFF FILES

Download the working kit

Use the full package for implementation, or take the brief and tokens separately for an AI or engineering handoff.

Complete brand kitSilver Signal packagesilver-signal-brand-kit.zipClaude design briefProduct and visual instructionsclaude-design-brief.mdDesign tokensColors, type, spacing, bordersdesign-tokens.jsonInterface copy guideStatus, labels, instructions, and noticescopy-style-guide.md

Stable public paths are reserved above. A file may be temporarily unavailable while the downloadable package is being published.

FOUNDATION / PRINCIPLES

Interface requirements

  1. 01

    Clear controls

    Use familiar controls, visible page structure, and labels that state the result of each action.

  2. 02

    Written status

    Name what is ready, pending, local, or unavailable. Color may reinforce a state, but text must always explain it.

  3. 03

    Sources and limits

    Show sources, dates, limitations, and confidence. Do not use decoration to imply certainty or urgency.

  4. 04

    Review before action

    Keep review steps and privacy notices visible. Important actions must state what will happen before the user continues.

FOUNDATION / COLOR

System palette

Blue establishes application structure. Silver and paper carry most content. Semantic colors communicate state only when paired with a written label.

  • System Blue#245EDBActive chrome, primary markers
  • Deep Blue#0B3D91Frames, selected states
  • System Silver#D4D0C8Classic controls, dividers
  • Warm Surface#ECE9D8Menus, toolbars, panels
  • Paper#FFFFFFReading and data areas
  • Ink#111111Primary text and outlines
  • Signal Green#67B94AReady and online states
  • Review Yellow#FFD83DCaution and review states
  • Stop Red#C83B24Blocked and destructive states

FOUNDATION / TYPOGRAPHY

Type styles and uses

INTERFACETahoma, Verdana, Arial

Source record updated

Use for navigation, controls, tables, labels, help text, and anything a person must operate.

EDITORIALGeorgia, Times New Roman

Start with one clear question.

Use selectively for page titles and learning headlines. Keep body copy in the interface face.

TECHNICALCourier New, monospace

CONFIDENCE: MODERATE

Use for file names, identifiers, timestamps, tokens, compact metadata, and machine-readable values.

FOUNDATION / GEOMETRY

Spacing and borders

Start from a 4-pixel unit. Prefer borders, alignment, and spacing over shadows. When a shadow is useful, make it short and visibly mechanical.

  • --space-14px
  • --space-28px
  • --space-312px
  • --space-416px
  • --space-624px
  • --space-832px
  • --space-1248px
Window

Window frame

2px solid #143C8C
Divider

Content divider

1px solid #BCBCBC
Control

Classic control

2px outset #FFFFFF
Data field

Recessed field

2px inset #FFFFFF

COMPONENTS / CORE UI

Windows and controls

Application window

Use for major tools and contained workspaces. Title bars carry identity without imitation window controls.

Source Check
File   Edit   View   Help
claim-record-04.txt

Modified today · review pending

1 object selected

Buttons

Use sentence case and concrete verbs. Reserve the strongest outline for one preferred action per view.

Save recordOpen previewRemoveUnavailable
Height
32–36px
Label
Verb + object
Radius
0–3px

Status labels

Pair shape, color, and plain language.

  • OnlineAvailable and current
  • DraftUsable, still changing
  • ReviewNeeds a human check
  • OfflineUnavailable or disconnected

Tube-television video frame

Curriculum video uses a 640 × 480, 4:3 master inside a familiar, familiar cabinet. Existing widescreen footage is letterboxed, never stretched or silently cropped.

Master
640 × 480 progressive
Shape
4:3 tube-TV screen
Playback
Native controls, no autoplay
Access
Edited captions + transcript
SILVER SIGNAL4:3 TRAINING VIDEO640 × 480 MASTER
480P / 4:3Static component specimen · cabinet controls are decorative

PATTERNS / INFORMATION

Source and prompt records

Put source information beside interpretation. A person should be able to see what entered the system, what happened to it, and what remains uncertain.

Observation record

READ ONLY
Record   Source   History
ClaimService resumes Monday
Observed14 Aug 2026, 09:20
SourcePublic bulletin / direct copy
Confidence Review
MissingOfficial schedule confirmation

Use rows for facts and provenance. Do not hide important qualifiers inside a tooltip.

Prompt record

DRAFT
Task
Compare the bulletin with the published schedule.
Evidence
Bulletin text, source URL, schedule snapshot.
Limits
Do not infer intent. Flag dates that do not match.
Output
Three-column comparison with an uncertainty note.

A useful prompt names the task, evidence, limits, and output. It does not rely on a role-play persona to create authority.

GUIDANCE / APPLICATION

Implementation rules

Do

  • Use borders and alignment to reveal relationships.
  • Write status labels that make sense without color.
  • Keep sources, timestamps, and limitations visible.
  • Let dense views remain dense when the task requires it.
  • Use period references as functional design logic.

Don't

  • Make every object a separate rounded card.
  • Use blue glow, scanlines, or hacker imagery as shorthand.
  • Hide uncertainty behind confident generated prose.
  • Add feeds, streaks, or notifications without a user need.
  • Copy obsolete interaction problems for nostalgia.

SPECIMEN / AI WORKSPACE

AI interface example

This static example shows the required context, process, limits, and output fields for an AI-assisted tool.

UI specimen only. No model is running, no prompt will be submitted, and no information is stored.
Silver Signal Study Harness
Session   Context   Review   Help

User question

INPUT

“I found two posts saying the town water notice was lifted. How should I check this before sharing it?”

Review plan

  1. Write the exact claim and jurisdiction.
  2. Look for a dated update from the responsible public office.
  3. Compare publication time, location, and affected service area.
  4. State what remains unconfirmed before sharing.

Draft response

SPECIMEN OUTPUT

Treat the posts as leads, not confirmation. Check the town or utility's official notice page and confirm that the update names your service area and is newer than the original advisory. If no official update is available, share that the claim is unconfirmed and link to the latest dated notice instead.

Sources cited: 0Human review: required
Controls disabled in public specimen
MODE: DEMONSTRATIONPRIVACY: NO DATA STORED