A service is a lawful journey, not merely a form

Core principles

• Deliberate procedural friction for consequential changes.
• Dual human and machine legibility.
• Identity continuity and non-deprivation.
• Once-only data exchange only with lawful purpose and citizen control.
• Data minimization and explicit retention.
• Reasoned decisions with authority, evidence, uncertainty and appeal.
• Accessible forms, receipts, error recovery and status communication.
• No misleading live-status, backlog or completion claims.
• Graceful degradation and continuity tiers.
• Public performance reporting without exposing private topology or citizen data.

Service lifecycle

1. 01

   Discover and prepare

   Eligibility, authority, required evidence, privacy and expected result are explained before submission.

2. 02

   Submit and receive

   The service validates input, supports review before submission and produces a durable receipt.

3. 03

   Process and notify

   Status changes, requests for information and delays are reasoned and accessible.

4. 04

   Decide and implement

   The decision identifies authority, law, evidence, uncertainty, effective date and result.

5. 05

   Correct, appeal and preserve

   Correction and appeal remain available, and the complete record is preserved under the appropriate retention rule.

Decision record

A binding administrative decision requires a stable ID, responsible institution, legal authority, evidence considered, unavailable evidence, reasons, limitations, effective date, correction route, appeal route and revision history.

Truthful status

Configured information, available static content, a live service, a processing queue, an incident and assurance evidence are separate states. The portal must never convert one into another through optimistic wording.

Accessibility and assistance

Core guidance and decisions must remain available without JavaScript. Forms require labels, error summaries, saved progress where appropriate, keyboard operation, reflow and an assisted-access route that does not diminish legal rights.

Implementation gate

No Registry-pending service may be relabeled operational until a real backend, privacy review, authority, testing, accessibility acceptance, incident handling, rollback and evidence package exist.