jobtrackingapp/docs/direct-roadmap/sources/CONTINUOUS_DEVELOPMENT_DIRECTIVE_b2425dc6.md

Jobjakt — CONTINUOUS DEVELOPMENT DIRECTIVE

Keep Working Until No Further Authorised Work Is Possible

I want you to continue developing Jobjakt autonomously for as long as the current execution environment permits.

Do not stop after completing one task, checkpoint, commit, feature, test suite or workstream.

Continue selecting and completing the next eligible task from my entire Jobjakt roadmap.

Do not use the autonomous orchestrator. Continue directly in this Codex conversation using my existing development environment and account.

1. Authoritative task sources

Read and continually maintain:

• docs/direct-roadmap/ROADMAP_TODO.md
• docs/direct-roadmap/ROADMAP_STATUS.md
• docs/direct-roadmap/LATEST_CHECKPOINT.md
• Relevant source prompts, implementation plans and acceptance documents.

Use the actual repository state as the source of truth.

The roadmap includes:

• Remaining Phase 10 acceptance.
• A3 application UI/UX modernisation.
• Product Review.
• International Global Job Search.
• European localisation.
• Europe-wide geographic support.
• Performance and scalability improvements.
• Public homepage redesign.
• Security audit and remediation.
• Release readiness.
• Existing technical debt and preservation requirements.

Do not abandon existing tasks or replace their acceptance criteria.

2. Continuous execution loop

After completing any task or checkpoint:

1. Verify the implementation.
2. Run the appropriate tests.
3. Fix bounded failures.
4. Record actual verification evidence.
5. Commit validated changes.
6. Push where available and required.
7. Update the authoritative TODO and continuation records.
8. Review all remaining eligible tasks.
9. Select the highest-priority independently authorised task.
10. Immediately continue working on it.

Repeat this process for as long as useful work remains and execution is available.

Do not end your response merely to provide a progress summary.

Do not ask whether I want you to continue.

Do not wait for a new "continue" instruction between checkpoints.

3. Latest progress

Recent published work includes:

• A3 application UI improvements and visual flattening.
• Discovery filter drawer and saved-search workflows.
• Settings freshness, locale-aware sorting and timezone fixes.
• Correspondence recovery and duplicate-submission fixes.
• Session-safe exports and CSV downloads.
• Import/conversion localisation fixes.
• Rules UX and recovery improvements.
• Offline backup and rollback improvements.

The latest reported application checkpoint is 214eb25f, followed by further published TODO work.

Verify the actual current Git HEAD and continuation records rather than assuming this summary is the latest commit.

Avoid repeating completed work.

The next reported focus is connected document/application workflows, followed by further eligible items in the existing roadmap.

4. Work through the entire TODO

Do not restrict yourself to the most recently discussed page or feature.

Continue across all authorised workstreams.

Prioritise:

1. Confirmed security or data-integrity defects.
2. Work that unblocks other roadmap tasks.
3. Incomplete core user journeys.
4. A3 UI/UX and accessibility gaps.
5. Global Job Search and European localisation.
6. Performance and scalability improvements.
7. Homepage implementation.
8. Broader security and release qualification.

Adjust priority using actual dependencies, risk and impact.

A roadmap task marked PARTIAL is not complete.

A task marked BLOCKED must remain open until its blocker is genuinely resolved.

5. Work concurrently when safe

Where the environment supports parallel Codex agents, use them for independent tasks.

Examples:

• Frontend UI/UX and accessibility.
• Backend performance and query optimisation.
• European translations.
• Global Job Search research and provider-independent implementation.
• Security static analysis.
• Release-readiness documentation and offline checks.

Use separate worktrees or otherwise isolated scopes.

Avoid conflicting modifications to the same files.

Do not run incompatible database migrations or competing tests against shared mutable fixtures.

Respect reasonable resource limits.

If safe parallel execution is unavailable, continue sequentially.

Do not stop simply because concurrency is unavailable.

6. Blockers must not stop the roadmap

If an individual task cannot proceed:

1. Investigate the blocker.
2. Attempt reasonable safe remediation within the authorised scope.
3. Record the exact issue in the existing TODO.
4. Mark it BLOCKED or AWAITING_APPROVAL.
5. Record the required action.
6. Identify another independently eligible task.
7. Continue immediately.

Do not retry unchanged failures indefinitely.

Do not waste time repeatedly investigating unavailable external providers, infrastructure or approvals.

Do not treat production NO-GO as a reason to stop unrelated development.

7. Batch all owner questions

I do not want to be interrupted for ordinary development decisions.

Maintain one consolidated list of questions and approvals.

If a task requires my input:

• Record the decision.
• Explain the available options.
• Provide your recommendation.
• Identify the dependent work.
• Continue other eligible work.

Only ask me questions when there is no further useful authorised work that can proceed, or when an immediate security/data-loss risk genuinely requires my attention.

When that point is reached, present all outstanding questions together in one prioritised decision batch.

Do not interpret silence as approval.

Do not bypass mandatory approval gates.

8. Use accepted decisions

Do not repeatedly ask me to approve decisions I have already made.

Preserve:

• The approved A3 design direction.
• The requirement to remove unnecessary nested cards on desktop and mobile.
• All 34 routes and 57 preservation groups.
• The international, Europe-wide product scope.
• Country-aware geographic filtering and maps.
• Full European localisation goals.
• The existing PDF visual approval and accepted S01 metrics.
• Previously authorised reversible development changes.
• All genuine remaining approval requirements.

If an approval applies only to a particular scope, do not extend it to unrelated work.

9. Testing and acceptance

For every meaningful change:

• Run relevant automated tests.
• Validate data integrity.
• Check authorisation where applicable.
• Check desktop/mobile behaviour.
• Check English/Norwegian and affected European locales.
• Preserve existing functionality.
• Record actual results.
• Fix regressions when possible.

Run broader regression suites when the applicable acceptance gates require them.

Do not fabricate passing results.

Do not mark incomplete implementation or tests as accepted.

Distinguish:

• Implemented.
• Tested.
• Accepted.
• Published.
• Production-ready.

Use valid historical evidence where appropriate, without presenting it as newly executed tests.

10. Maintain durable continuity

After every validated increment, update:

ROADMAP_TODO.md

ROADMAP_STATUS.md

LATEST_CHECKPOINT.md

Record:

• Exact branch and commit.
• Completed work.
• Tests executed.
• Outstanding defects.
• Blockers.
• Required approvals.
• Next eligible tasks.

Ensure another Codex session could resume from the latest checkpoint without repeating work.

Do not create a replacement orchestrator or additional automation infrastructure.

11. Do not stop prematurely

The following are NOT reasons to stop:

• One feature is complete.
• A set of tests passes.
• A commit is published.
• An external provider is unavailable.
• One workstream needs approval.
• A design review is pending.
• Hosted CI is unavailable.
• A production-only gate remains blocked.
• A partial acceptance report has been generated.
• A single development task has no further actions.

Continue with another independent task.

12. Genuine stopping conditions

Stop only when:

1. No further independently authorised, useful work remains.
2. All remaining tasks genuinely require owner decisions, external permissions or unavailable prerequisites.
3. A safety issue makes further work unsafe.
4. The current Codex execution session reaches a technical, context, resource or usage limit.

If execution must end because of a technical limit, preserve a complete continuation checkpoint and identify the next eligible task.

Do not claim that work will continue in the background unless an actual supported scheduled continuation mechanism is running.

13. Final consolidated report

When no further work can proceed, report:

• All completed tasks.
• All incomplete tasks.
• Actual verification results.
• Remaining security issues.
• European market and language coverage.
• UI/UX implementation progress.
• Performance improvements.
• Outstanding acceptance gates.
• Grouped owner decisions.
• Highest-priority next actions.

Present the owner questions together, with recommendations.

Do not claim the whole roadmap is complete unless every relevant acceptance criterion is satisfied.

Hard restrictions

Never:

• Use or modify the autonomous orchestrator.
• Merge into main.
• Deploy production.
• Perform destructive migrations without approval.
• Change production infrastructure without approval.
• Self-approve protected gates.
• Activate unqualified production AI models.
• Access private production data unnecessarily.
• Ignore security or tenant-isolation failures.
• Weaken tests to obtain passing results.

Final instruction

START CONTINUOUS ROADMAP EXECUTION NOW.

Keep implementing, testing, fixing, documenting and committing.

After each completed task, immediately move to the next eligible task.

Use safe concurrency where supported.

If blocked, record the issue and move on.

Do not pause for routine questions or milestone summaries.

Continue until there is genuinely no more authorised work you can do within the available execution session.

Only then provide a consolidated report and batch the outstanding questions for me.