Skip to content

Draft — not approved. A working draft by UASK. It may change without notice.

Status: draft · Version 0.6.0

Human Interface Framework

Status: draft normative and professional knowledge base, version 0.6

HIF is a brand-independent framework for designing, building, evaluating and governing human interfaces across operating systems, applications, websites, services, documentation, administrative tools, kiosks, terminals, conversational products and AI-mediated systems.

HIF does not prescribe one visual style. It defines stable human meanings, rights, safeguards and quality methods from which product-specific design systems can be derived.

Normative hierarchy

  1. applicable law and safety obligations;
  2. platform requirements necessary for interoperability;
  3. the HIF Interface Constitution;
  4. an applicable HIF Product Profile;
  5. a product’s documented domain model and policies;
  6. its design system, components and implementation.

A lower layer MUST NOT silently weaken a higher layer. A justified exception requires scope, owner, evidence, risk, mitigation and review date.

Corpus

Orientation and foundations

Architecture and interaction

Design foundations

Systems and profiles

Governance and rights

Research, measurement and conformance

Commercial client practice

Source register

Normative words

  • MUST / MUST NOT — a requirement for HIF conformance;
  • SHOULD / SHOULD NOT — the expected decision unless evidence justifies an exception;
  • MAY — an allowed choice that remains subject to stronger requirements.

Product workflow

context and user needs
→ product profile
→ objects, commands, states and policy
→ information and interaction architecture
→ content, visual language and patterns
→ design-system contracts and implementation
→ evaluation and release evidence
→ operational learning

Maintain traceability from each important user need through requirement, design decision, implementation, test and evidence.

Client-site workflow

authority and scope
→ inventory, task corpus and sample
→ risk-based test design
→ expert, participant, accessibility and technical evaluation
→ reproducible findings
→ prioritised remediation proposal
→ implementation
→ acceptance, retest and regression
→ measured outcome and residual risk

An organisation that both audits and implements MUST disclose that commercial relationship. Finding severity MUST be based on user and system consequences, not expected remediation revenue. Conformance claims MUST remain within the evaluated scope and evidence.

Source policy

HIF cites traceable English-language originals: issuing standards bodies, original research, official platform guidance and official public-service manuals. Translations and secondary articles are not evidential authorities.

Change management

Every material change records the affected claim, evidence, profiles, tests, migration impact, reviewer and date. Platform rules and living standards are reviewed before relevant engagements and at least annually.