// the future

Roadmap

Where Visor goes next.

planned Secure Boot automation

Make the fully-signed chain a one-command outcome instead of a manual checklist. Planned scope:

• install.sh / visor update sign Visor, kernels/UKIs, and EfiFs drivers automatically when sbctl keys are enrolled — including re-signing on every update so an update can never break a signed setup.
• First-class shim support: install Visor behind shimx64.efi, with a MOK enrollment helper for self-built kernels.
• visor status gains a Secure Boot report: what is signed, with which key, and what would fail to boot right now.

planned Theme system & gallery

Themes today are loose .conf files. Planned scope:

• A shareable theme package format: one file bundling colors, layout, background, icons, and font choices.
• visor theme install <file-or-url> / visor theme list host-side management.
• A community gallery — a repository of user-made themes browsable from the wiki, with screenshots, one command to install.
• More themeable knobs as they are requested (per-element fonts, icon packs, layout presets).

planned More architectures

The architecture layer (src/arch_*.c) was built for this. Planned scope:

• RISC-V (riscv64) UEFI build as the third target: arch layer implementation (timer, cache/WC behavior) and gnu-efi cross staging like the AArch64 setup script.
• Keeping all targets building from the one tree with the same zero-warning, RELATIVE-only-relocation rules.

Not planned

Things Visor deliberately stays away from, so the "minimal" in the tagline keeps meaning something:

• A scripting language in the bootloader.
• Parsing LUKS/filesystem encryption in firmware (the initramfs does that better).
• Becoming a firmware setup replacement — Visor boots things, that's the job.