jobtrackingapp/docs/ui-modernisation/A3_APPROVAL.md

Jobjakt — A3 Final Design Approval and Implementation Authorisation

I approve A3 as the final Jobjakt UI/UX design foundation and authorise its phased implementation across the application.

I have reviewed the design direction and am happy with the result.

This approval includes the consolidated A3 prototype, its established design system, navigation approach, layouts and connected workflows.

1. Confirmed design decisions

Preserve the approved A3 combination:

• Original A1 dashboard.
• D1 visual foundation.
• B1 application tracking.
• Labelled, grouped and collapsible desktop sidebar.
• Hybrid mobile navigation.
• CV editor on the left with live preview on the right.
• Full application-detail pages with contextual information on the right.
• Optional quick-preview panels.
• Career Profile overview first, with immediate editing actions.
• Calendar agenda first, with an optional month view.
• Automation controls under Settings.
• Contextual AI assistance.
• Optional, resumable dashboard onboarding checklist with on-demand walkthroughs.

Maintain the selected light/dark visual treatment and consistent responsive behaviour.

Do not restart design exploration or generate another five concepts.

Minor adjustments for implementation feasibility, accessibility and usability are permitted.

Consult me before making substantial changes to the approved visual direction or user journeys.

2. Implementation approval

I authorise the actual implementation of the approved A3 redesign within the appropriate Jobjakt development branches.

This includes:

• Shared design system.
• Typography and colours.
• Navigation.
• Dashboard.
• Application tracking.
• Application details.
• Job discovery.
• Career Profile.
• CV Builder.
• CV import.
• Cover letters.
• Calendar.
• Correspondence.
• Documents.
• Settings.
• Automation controls.
• Administration.
• Onboarding.
• Mobile layouts.
• Light/dark modes.
• Accessibility improvements.

The implementation must cover the actual application, not merely reproduce static prototypes.

3. Preserve existing functionality

The design handoff identifies 57 preservation groups and 34 routes.

Treat these as mandatory preservation requirements.

Do not remove, simplify or hide advanced functionality merely because it was not shown in the prototypes.

Preserve:

• Existing user data.
• Career Profile ownership and persistence.
• CV revisions and undo/redo.
• Document imports and exports.
• Application records.
• Authentication.
• AI permissions and qualification restrictions.
• Dashboard customisation.
• Administrative permissions.
• Existing integrations.
• English/Norwegian support.
• Future European localisation.
• Database compatibility.
• Existing accessibility functionality.

Maintain all relevant RD21 data-integrity protections.

4. Implementation sequence

Use the implementation milestones documented in the A3 handoff.

Subject to the authoritative dependencies and Phase 10 gates, organise implementation approximately as follows:

UI-01 — Shared design system and navigation

Implement foundational styles, typography, components, navigation, themes and responsive structures.

UI-02 — Dashboard and applications

Implement dashboard layouts, interactive widgets, application tracking, Kanban and application-detail experiences.

UI-03 — Career Profile and CV workflows

Implement the approved Career Profile, CV Editor, template, import and cover-letter experiences.

UI-04 — Job discovery and application journeys

Implement approved job-discovery layouts and connections to the existing application workflows.

Coordinate with INT-GLOBAL-JOBS-01 to avoid conflicting implementations.

UI-05 — Supporting workflows

Implement calendar, reminders, correspondence, documents, administration, settings and automation controls.

UI-06 — Onboarding and mobile refinement

Complete guided optional onboarding, mobile navigation, small-screen layouts and responsive interaction parity.

UI-07 — Integrated qualification

Run full preservation, accessibility, responsive, browser and application regression acceptance.

Use the authoritative A3 implementation plan where it specifies more precise dependencies or acceptance requirements.

5. Autonomous development

Continue working through the implementation milestones without asking me to approve every ordinary change.

You may autonomously:

• Implement approved designs.
• Refactor affected frontend components.
• Introduce reusable design-system components.
• Improve responsive layouts.
• Fix implementation defects.
• Add tests.
• Update translations.
• Run regression checks.
• Commit validated checkpoints.
• Update documentation.

Pause only when a genuine owner decision, mandatory gate or substantial design change is required.

If a task is blocked, record the blocker and continue independently eligible work.

Do not bypass Phase 10 cleanup approvals, required integration baselines or other authoritative development-entry gates.

6. Coordinate with the remaining roadmap

Continue the existing direct roadmap execution.

Do not use the autonomous orchestrator.

Coordinate A3 implementation with:

• Phase 10.
• Product Review.
• International Global Job Search.
• Full European localisation.
• Multilingual homepage redesign.
• Security audit.
• Release readiness.

Avoid duplicate implementations and unnecessary rewrites.

Use established accepted baselines, isolated branches and documented dependencies.

Do not treat provisional mockup content as actual product functionality.

7. Validation requirements

For each implementation milestone:

• Run relevant frontend tests.
• Run required backend tests where workflows are affected.
• Validate browser journeys.
• Validate mobile layouts.
• Check keyboard accessibility.
• Check translation behaviour.
• Check light/dark modes.
• Test preservation requirements.
• Compare implementation against the approved A3 design.
• Record regressions and failures.

The prototype validation results are useful design evidence, but they do not qualify the implemented application.

Real screen-reader, physical-device and human accessibility tests remain pending until actually completed.

Do not claim unperformed tests passed.

8. Git and release restrictions

The latest design checkpoint is 237c79b8.

The roadmap continuation checkpoint is 286535be.

Verify the actual commits, branches and ancestry before integrating work.

Preserve the existing worktrees and acceptance records.

Keep validated changes in development branches and commit checkpoints.

Do not spend time repairing Gitea as part of this design implementation.

If publication fails, preserve the local work, record the issue and continue eligible work without falsely claiming publication success.

Never merge into main or deploy production without explicit approval.

9. Final objective

Deliver the approved A3 experience throughout the real Jobjakt application.

I want a cohesive, modern, approachable and powerful product, with equally strong desktop and mobile experiences.

Preserve the application's advanced capabilities while making everyday workflows easier to understand and use.

This is my final approval of the A3 design and authorisation to begin its staged development implementation.

It is not approval for production deployment or for bypassing outstanding security and release gates.

Continue with the next authorised implementation milestone, maintaining durable progress reports and proceeding through independently eligible work without unnecessary interruptions.