NewGuy

Powered by Secretary 2.0

Your AI operating partner.

Objectives, conversations, devices, approvals, execution and proof under explicit governance.

Powered by Secretary 2.0

Developed by David William Gislason

Secure workspace

Sign in

Use your Secretary 2.0 account.

Release unavailable

Good to see you

NeRD

What David owns, what needs you, and what S2 has proven.

David is available Reception and governed execution online

Active objectives — Loading…

Needs you — Approvals and decisions

Devices — Registered estate

Recent activity — Auditable events

Active Objectives

Needs You

Devices

Latest Activity

D

David

NewGuy · Active assistant

Door Key: General

Governed conversation records will appear here.

Current session

Context

Principal

Principal ID

Device

Session

Outcome Sessions

Objectives

Durable work S2 is responsible for completing and proving.

Waiting for governed S2 data.

Objective Workspace

Loading objective…

Retrieving governed objective state.

unknown

Service —

Operating mode —

Risk —

Approval —

Updated —

Revision —

Plan

What S2 intends to accomplish

Scope

—

Likely root cause

—

Proposed fix

—

Rollback plan

—

Evidence

Observed facts

0

Diagnosis

Hypotheses

0

Investigation

Tests

0

Execution

Governed actions

0

Proof

Verification

0

Outcome

Current result

Resolution

—

Remaining uncertainty

—

Follow-up

—

Related

Governed context

Objective ID: —
Conversation: —
Device: —
Owner: —

Observable S2 State

Live Activity

Evidence, state changes and execution events — not hidden chain-of-thought.

Waiting for governed S2 data.

Governance · Human Authority

Approvals

What needs your authority, why it needs it, and what governed action is waiting.

Pending 0

Approved 0

Denied 0

Total 0

Authority boundary

Read-only governance view

Approval decisions are intentionally not available here yet. S2 will expose those controls only after the complete authorization, authentication and step-up decision path is proven.

Waiting for governed approval data.

Trusted Estate

Devices

Registered endpoints, trust state and governed capabilities.

Waiting for governed S2 data.

Device Workspace

Loading device…

Retrieving governed device state.

unknown

Platform —

Device class —

Last seen —

Registered —

Trusted since —

Revision —

Identity & Trust

Registered device identity

Device identifier —

Device ID —

Bound principal —

Public key fingerprint —

Objectives

Work involving this device

0

Observable Activity

Device-linked S2 events

0

Device Agent

Presence

Agent connectivity Not exposed

Device registration and trust do not prove that the native Device Agent is currently connected.

Capabilities

Current advertisement

Advertised capabilities Not exposed

S2 does not infer current Device Agent capabilities from platform, device class, or historical evidence.

Identity & Authentication

People

Authenticated human identity, sessions, assurance and trusted devices.

Waiting for governed identity data.

People · Identity · Authentication

Loading identity…

Human-facing projection of authenticated identity, sessions, assurance and devices.

Principal type —

Unavailable

Authentication —

Method —

Assurance —

Last verified —

Active sessions 0

Trusted devices 0

Identity

Authenticated principal

Principal ID

—

Current session

—

Current device

—

Authentication

Authentication history

0

Sessions

Authenticated sessions

0

Objectives

Work involving this principal

0

Conversations

Related communications

0

Devices

Registered devices

0

Security Activity

Observable identity events

0

Security boundary

Sanitized projection

Tokens, authentication factors, evidence, credential material, recovery material and provider secrets are not exposed to this workspace.

Governed Capability Library

Abilities

Semantic capabilities S2 may discover, govern and invoke.

Waiting for governed S2 data.

Durable Outputs

Artifacts

Governed files, versions, derivations and generated outputs.

Waiting for governed S2 data.

Evidence & Accountability

Audit

Observable event history across S2.

Waiting for governed S2 data.

Voice · Message · Notification

Communications History

What happened, through which channel, and why S2 communicated.

Conversations 0

Realtime sessions 0

Notifications 0

Governed events 0

Communication threads

Conversations and channel activity

Waiting for sanitized communications history.

Standalone evidence

Communication events

Telephone, SMS, voice and message evidence appears here when S2 recorded it but no explicit Conversation link exists.

Notifications

Unlinked notifications

Notifications remain separate unless a real source-object or correlation relationship links them to a Conversation.

Relationship boundary

No inferred history

S2 does not group communications because their timestamps are close. Threads use explicit Conversation IDs, correlation IDs, source-object IDs, or Objective conversation relationships only.

External Integration Kernel

Integrations

Canonical providers available through the governed S2 integration boundary.

Governed Secret Boundary

Credentials

Tenant-managed credential metadata. Secret values are never displayed.

Commercial Telemetry

Usage & Economics

Real S2 execution telemetry only. No fabricated billing data.

Workflow runs —

Ability invocations —

Realtime sessions —

Billing ledger Not exposed

Persona Registry

Door Keys

Behavior and capability presentation. Door Keys never grant authority.

Reception

Tech Wizard

Sports Buff

Master Chef

Shopaholic

Identity · Session · Runtime

Settings

Principal

Tenant

Session

Browser device

S2 LIVE · REAL OBJECTIVE SESSION

Objective-driven AI, visibly governed.

One real objective. The evidence S2 saw, the plan it formed, the authority it respected, the actions it took, and the proof that determined the outcome.

OBJECTIVE

Waiting for a real Objective Session

Presentation Mode follows the newest governed Objective Session.

Status —

Service —

Risk —

Governance —

Verification —

Affected device —

01

EVIDENCE

What S2 actually observed

02

HYPOTHESES

What might explain reality

03

PLAN

How S2 intended to reach the outcome

04

GOVERNANCE

Authority before action

05

GOVERNED ACTIONS

What S2 actually attempted

07

VERIFICATION

Command success is not objective success

08

OUTCOME

What happened in the real world

09

COMMUNICATIONS

Who S2 could prove was connected to the objective

Communications are linked only through the Objective's explicit Conversation ID and the sanitized Communications projection. No timestamp-proximity grouping is used.