KSD Workspace
In development

One governed place to work.

KSD Workspace is the human-facing operating environment for KSD. It is designed to bring approved tools, context, communication, rooms, mission state and proof into one protected workspace while keeping the underlying authority boundaries intact.

One protected appPasskey-first directionGoverned InboxLibraryMission visibilityProof receipts
The key distinction

Workspace is where you work. Dispatch is what governs the work.

Workspace is not the control plane. A clean interface must not blur authority. Workspace can collect intent, show assignments, display proof and present human checkpoints. It does not independently issue mission authority, certify execution or change governed mission state.

WorkspaceHuman-facing environment and security perimeter.
DispatchSole governed execution and mission-state control plane.
OrbitIndependent verification; cannot mutate Dispatch state.
LibraryGoverned knowledge and read access; not execution authority.
Connected rooms

One app without pretending everything is the same thing.

Workspace is intended to make KSD feel coherent while preserving separate product and authority boundaries.

Mission room

See current state, your role and authority, assignment, required proof, blockers, handoff history and the next available action.

Governed Inbox

External communication enters the work environment only when deliberately admitted, with channel-specific permissions and disclosure rules.

Library

Browse governed knowledge, search the catalogue and request controlled access without treating discovery as authority to possess or execute.

Calendar

Surface appointments, deadlines, events, maintenance windows and reminders in a provider-neutral work timeline.

Secretary + Manager

Human-facing support roles can organize and coordinate work while remaining subordinate to the mission's actual authority model.

Catalogue

Choose Workers, skills, Backpacks, products and repeatable outcomes, then hand the bounded request into governed execution.

System flow

From a human request to independently verified proof.

This public model describes the intended architecture. It is not a claim that every Workspace room is released or runtime-proven.

01PersonStates the desired outcome and sees the relevant context.
02WorkspaceCollects intent and presents the governed mission surface.
03DispatchChecks authority, routes the mission and controls state.
04Worker + Skills + BackpackExecutes only the bounded work admitted for that mission.
05OrbitIndependently checks the evidence and unsupported claims.
06ReceiptWorkspace can present the proof-backed result after the governed state transition.
Identity, privacy & device boundary

Losing a phone should not mean losing the company.

The Workspace direction treats the app as a governed security perimeter rather than a copy of the full company. Authentication is designed around strong device/passkey controls, while sensitive knowledge and authority remain bounded instead of being permanently replicated onto the device.

Midnight Lens keeps its own job.

When identity, consent, signing, temporary access or selective disclosure is required, Workspace can invoke Midnight Lens without absorbing Lens authority. Detection or presentation alone never authorizes execution.

Data boundary

User-owned storage remains the default.

Workspace does not imply that KSD centrally stores a person's content. The default direction remains on-device or user-controlled cloud storage. Any KSD-managed storage would be a separate explicit service with its own consent, limits and retention terms.

External channelsAdmitted intentionally rather than automatically mirrored into work.
KnowledgeNeed-to-know access can remain read-only and session-bound.
ExecutionOnly Dispatch-issued bounded missions reach Workers.
ProofReceipts remain attributable to the mission and executor.
See the control architecture

Workspace makes the system usable. It does not weaken the separation.

Dispatch + Orbit