Recovered public website

Work in the flow, not under a pile of popups.

Ohverlay is a calm workspace layer for sticky notes, network file handoffs, supervisor dashboards, and future AI assistance. It is designed for visibility without clutter, urgency without panic, and coordination without surveillance theater.

4.0.3

Current office release with branded HTTPS update origin.

2 roles

Separate Standard User and Supervisor builds.

Local-first

Logs, overlays, and traceability stay inspectable on the machine.

Ohverlay Runtime
Sticky Notes

Countdowns, elapsed time, transparency, lock state, and calmer deadline visibility.

File Handoff

Joel opened the routed drawing. Sender, time, path, and acknowledgment captured.

Supervisor View

Deadlines, sent items, acknowledgements, and active overlays in one place.

Blue AI, later

Grounded assistant behavior comes after the workflow and ethics surfaces are clear.

Core surfaces

Built for operations, not vanity dashboards

The office build already moved beyond ambient visuals. It now combines reminder overlays, team dispatch, logs, and role-aware visibility in a single runtime.

Sticky note system
Reminder overlays that stay readable

Multiple simultaneous notes, countdowns, elapsed timers, theme options, transparency control, and lock state for click-through behavior.

  • Countdown and elapsed modes.
  • Theme and opacity presets.
  • Bottom-stack task visibility without hijacking the screen.
Network dispatch
File routing with traceability

Send a file from a shared folder, notify selected peers, open the path from the receiver overlay, and preserve the sender/recipient/time record.

  • Sender and receiver logs.
  • Path-aware notifications.
  • Future cleanup prompts for stale shared items.
Supervisor runtime
Visibility with declared scope

The supervisor build is not a different brand skin. It is a different operational role with dashboard access, timeline review, and deadline visibility.

  • Role-aware desktop builds.
  • Separate user and supervisor distribution.
  • Password-gated supervisor surfaces where configured.
Feature Inventory

What the office build already does today

This is the current product state, not concept art. These are the surfaces already present in the active Windows build.

Network File Handoff

Select a file or folder inside your shared location, choose peers, dispatch the handoff, and let the receiver open the routed path directly from the overlay.

Sticky Notes and Timers

Create multiple notes at once with countdown, elapsed time, transparency, theme, font scaling, lock state, and overdue escalation support.

Activity Console and Logs

Sent, received, opened, acknowledged, and sticky-note actions are recorded locally for review and export.

Role-Aware Desktop Builds

Standard User and Supervisor EXEs ship separately so the operational surfaces match the actual office role.

UI Gallery

Real interface images from the office build

These screenshots came from the actual deployment flow: setup, handoff dispatch, and console plus overlay notifications.

How it works

Fast operating flow

01
Install the right build

Use the Standard User EXE for staff or the Supervisor EXE for coordinators and oversight roles.

02
Configure folder, name, and peers

Open Control Center, set your shared folder, your username, and the peers you want to notify.

03
Send or receive

Create file handoffs, sticky notes, or timed reminders. Receivers can open directly from the overlay.

Path rule

The selected item must stay inside the configured shared folder

That rule is enforced intentionally so a notification cannot point outside the sender’s declared shared area. If a handoff fails validation, the selected file or folder is usually outside the configured base path.

  • UNC paths are safest for multi-user consistency.
  • Mapped drives can still work if all relevant PCs resolve them correctly.
  • Ohverlay normalizes Windows paths before validating the handoff.
Recovered public materials

The missing whitepaper is back

The public site had temporarily become only the updater/download endpoint. The original whitepaper-style material still existed in the repo, so it is now linked back into the live website instead of being stranded in source docs.

Design constraints

Calm technology is a product rule, not a mood board

Ohverlay is explicitly designed around privacy-first, local-first, transparent, and non-spammy behavior. That matters more than visual style because it determines what the system is allowed to become.

Downloads and docs

One public site, two jobs

This website now serves as both the update origin for the desktop app and the public-facing product site.

Standard User Build

Office desktop build for staff, peers, and day-to-day file handoffs.

Download EXE
Supervisor Build

Dashboard-enabled office build for oversight and coordination roles.

Download EXE
Updater Manifest

Role-aware update metadata used by the tray updater.

Open manifest
Source Documents

Recovered markdown docs behind the public summaries.

Open source docs