LogicVirtual Mind

VMLogic Harness / macOS

In development · No public release date

A native environment where agents remember, act, and leave evidence.

VMLogic Harness is the planned macOS product surface for persistent agent work. It is designed to connect durable project state with apps, browser sessions, files, and tools—then make the resulting actions and updates inspectable.

PlatformmacOS
ArchitectureModel-flexible
StateIn development
VMLogic Harness / Research workspaceVML—H—01
TaskBuild an evidence-backed market brief
01

Relevant project state recovered

02

Claims mapped to sources and constraints

03

Browser · Files · Analysis · Document

Artifactbrief.pdf

Verified artifact · trace retained

System loop / 01

The work continues beyond one model response.

A harness coordinates the surrounding system: what should be remembered, which tools may act, how progress survives, and what evidence supports the final result.

01

Intent

Define the goal, boundaries, and expected artifact.

02

Context

Recover only the project state relevant to this decision.

03

Plan

Turn relations and constraints into inspectable work.

04

Execute

Work through authorized apps, browser sessions, files, and tools.

05

Verify

Check the artifact, sources, actions, and unresolved questions.

06

Persist

Store evidence-backed state so the work can continue later.

One workflow / Research brief

From a request to a continuable workspace.

The example below is a product-direction scenario, not a claim of current public availability.

Request

Compare three approaches to persistent agent memory. Produce a concise brief, preserve the evidence, and leave open questions for the next session.

01

Recover the research state

Load the relevant project, prior decisions, source register, and outstanding questions.

Project state
02

Collect and structure evidence

Use the browser and local files, mapping each claim to its source and timestamp.

Evidence graph
03

Compose and check the brief

Draft the comparison, test constraints, and surface conflicts rather than smoothing them away.

Reviewable draft
04

Deliver and preserve continuity

Write the artifact, retain the execution trace, and carry forward only supported updates.

Brief + next state

Product architecture / Design targets

Built around the seams where agent work usually breaks.

01

Persistent project context

Projects, people, decisions, evidence, and open questions can remain available across sessions without replaying an entire transcript.

02

A real macOS work surface

The harness is intended to coordinate authorized work across local files, apps, browser sessions, and external tools.

03

Long-running and recurring work

Checkpoints, resumable progress, and scheduled routines are treated as system concerns rather than prompt conventions.

04

Skills and deliverables

Repeatable methods can be packaged as skills, while results are delivered as real documents, data, code, and other artifacts.

Inspectable by design / 04

Persistence should not become invisible automation.

The product direction is to keep cognitive state and execution reviewable: where context came from, what acted, what changed, and what remains uncertain.

01

Memory provenance

Recovered state should retain its source and scope.

02

Execution trace

Tool actions and produced artifacts should remain inspectable.

03

Human checkpoints

Consequential actions should expose clear review and control points.

04

Model boundary

Durable state should remain separable from the selected foundation model.

Supported models, exact permissions, data handling, availability, and pricing will be published in formal product documentation before release.

VMLogic Harness / Product direction

The native product surface for persistent AI.

In development for macOS. No public release date has been announced.

Return to VMLogic research Read the Tensor Logic note