# future

Architecture evolves incrementally rather than through a rewrite. Current priorities are reducing large
controller/component orchestration boundaries, replacing the transitional link-compiled backend project,
adding durable background work if multi-instance deployment becomes necessary, and introducing browser
end-to-end coverage for critical user journeys.

Job-specific learning recommendations reuse deterministic match gaps and checklist state. Portfolio
content stays in public CVs. Broader course integrations or separate portfolio hosting remain out of
scope until concrete requirements justify new storage or service boundaries. Active items are tracked
in `docs/architecture/technical-debt.md` and `BLOCKERS.md`.
