Temet now runs as a local macOS mission workspace

Temet started by making professional expertise legible: public profiles, machine-readable cards, structured competencies, and agent-facing endpoints. That layer still matters. It gives other agents a way to understand who you are, what you can do, and how your work is evidenced.

The next layer is operational. A consultant does not only need a profile. They need a place where incoming work can be received, examined, corrected, and turned into a deliverable without losing human responsibility. That is why Temet now has a local macOS application.

Professional work often contains client context, commercial terms, technical constraints, and private judgment. A browser page can present a profile, but the working surface belongs closer to the expert's machine.

The macOS app keeps the mission workspace local. It is designed around the files, decisions, corrections, and review steps that happen before a client receives anything. Temet Web remains the public read-only surface. The app is where the work is prepared.

The app is not a generic chat window. It is a mission workspace. It receives structured requests, keeps the expert's working context, exposes the state of a mission, and supports the review loop before delivery.

The menu bar companion follows a narrow local design: read-only access to `~/.temet`, no network calls, no direct session parsing, and actions delegated to the Temet CLI. It can be installed through `temet install-menubar`, places Temet in `~/Applications`, creates a LaunchAgent, and opens the app on macOS.

The important distinction is control. Agents can prepare, draft, and organize. The human expert reviews, corrects, signs, and accepts responsibility for the final result. Temet is built around that separation.

Temet Web remains the public side of the system. It serves the landing page, articles, public profiles, agent-readable endpoints, and the relay bridge. The macOS app carries the private working side: local mission handling, expert review, method building, and delivery preparation.

This split is deliberate. The web surface is for discovery and interoperability. The desktop surface is for production and supervision.

Temet is no longer only a way to describe expertise. It is becoming a way to operate it. A request can arrive as structured work, the agent can prepare the file, and the expert can decide what is acceptable before anything leaves the workspace.

That is the launch message: Temet turns AI-assisted professional work into a supervised delivery process. The public profile helps work find you. The local app helps you handle it.

The landing page now shows the macOS app in context, and this article is the public announcement behind that launch banner. The next step is to use the app as the entry point for the broader argument: consultants need local, supervised, structured workflows for AI-era services.

Temet Web remains the surface that explains and exposes the protocol. The macOS app is where the expert keeps control of the work.