Footer

Key Ideas

• Avoid Decorative Chrome: Refine is an operational tool; footer-like information should not distract from work.
• Use Persistent Utility Areas: status, logs, chat, files, terminal, and Guide belong in dedicated persistent surfaces.
• Context Over Branding: if bottom-of-screen space is used, it should carry operational value.

Purpose

The footer concept exists to define what Refine should not become: a page-like website with ornamental bottom navigation or marketing chrome.

The browser-desktop surface already has persistent utility areas: toolbar dock, Guide panel, banners, and shell status. Those should carry operational context better than a conventional footer would.

Expected Role

Footer-level information should be sparse. Version, status, diagnostics, and legal or support links may matter, but they should not compete with the active work surface.

If a future footer exists, it should be functional: system health, sync status, active app, update state, or diagnostics access. It should not become a second nav or a dumping ground for controls.

Future Direction

As Refine becomes more autonomous, bottom or edge surfaces may become useful for global queues, pending approvals, background work, or agent fleet status. Those should be treated as operational overlays, not as a traditional website footer.

The design intent is to preserve attention for work, state, and evidence.