Skip to content

Commit 46de6b9

Browse files
ttwjttwj
committed
feat: humanize site messaging and OpenVTC story
1 parent cb8cc97 commit 46de6b9

12 files changed

Lines changed: 305 additions & 252 deletions

File tree

‎agents/index.html‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,8 +4,8 @@
44
<meta charset="UTF-8" />
55
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
66
<meta name="theme-color" content="#1f1e1d" />
7-
<meta name="description" content="ONEComputer agent coverage: a safe cloud computer for Claude, NanoClaw, OpenClaw, Codex, Hermes Agent, and more." />
8-
<title>Agent Workspaces · ONEComputer</title>
7+
<meta name="description" content="Secure cloud workspaces for the AI agents your teams choose, including Claude, OpenClaw, Codex, NanoClaw, and Hermes Agent." />
8+
<title>A safe workspace for every AI agent · ONEComputer</title>
99
<link rel="icon" href="/favicon.svg" type="image/svg+xml" />
1010
</head>
1111
<body data-page="agents">

‎architecture/index.html‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@
44
<meta charset="UTF-8" />
55
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
66
<meta name="theme-color" content="#1f1e1d" />
7-
<meta name="description" content="ONEComputer architecture: a thin enterprise control plane over OpenVTC trust infrastructure." />
7+
<meta name="description" content="How ONEComputer combines cloud workspaces and company policy with OpenVTC identity and external approval." />
88
<title>Architecture · ONEComputer</title>
99
<link rel="icon" href="/favicon.svg" type="image/svg+xml" />
1010
</head>

‎docs/.vitepress/config.mjs‎

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ export default defineConfig({
44
title: "ONEComputer Docs",
55
titleTemplate: "%s · ONEComputer",
66
description:
7-
"Open-source documentation for secure cloud Claude workspaces, policy, and OpenVTC approvals.",
7+
"Documentation for isolated AI workspaces, company policy, and human approval through OpenVTC.",
88
base: "/docs/",
99
cleanUrls: true,
1010
appearance: true,
@@ -68,6 +68,7 @@ export default defineConfig({
6868
{ text: "Repository and runtime map", link: "/reference/repository-map" },
6969
{ text: "Troubleshooting", link: "/reference/troubleshooting" },
7070
{ text: "Current status", link: "/reference/status" },
71+
{ text: "Writing and messaging", link: "/reference/content-style" },
7172
],
7273
},
7374
],
@@ -83,7 +84,7 @@ export default defineConfig({
8384
},
8485
docFooter: { prev: "Previous", next: "Next" },
8586
footer: {
86-
message: "Open-source governed AI computers · forked from ONECli",
87+
message: "Open-source workspaces for safer agentic work · built from ONECli",
8788
copyright: "Released under the Apache-2.0 license",
8889
},
8990
},

‎docs/index.md‎

Lines changed: 27 additions & 28 deletions
Original file line numberDiff line numberDiff line change
@@ -1,76 +1,75 @@
11
---
22
layout: home
33
title: ONEComputer Docs
4-
titleTemplate: Secure cloud workspaces for Claude
5-
description: Install, operate, and extend ONEComputer.
4+
titleTemplate: Safe cloud workspaces for AI agents
5+
description: Learn how to install ONEComputer, run safe AI workspaces, and connect human approval through OpenVTC.
66
hero:
77
name: ONEComputer Docs
8-
text: The open-source control plane for secure Claude workspaces.
9-
tagline: Install the stack locally, understand the OpenVTC boundary, and operate the enterprise path from sandbox to verified approval.
8+
text: Build a safe place for AI agents to work.
9+
tagline: Install ONEComputer locally, understand how OpenVTC keeps approval separate, and follow the path from an employee workspace to a signed human decision.
1010
actions:
1111
- theme: brand
1212
text: Install ONEComputer
1313
link: /getting-started/installation
1414
- theme: alt
15-
text: Understand the architecture
15+
text: See how it works
1616
link: /architecture/
1717
features:
18-
- title: Cloud workspaces
19-
details: Give teams an isolated computer with Claude Desktop and Claude Code available in the runtime.
20-
- title: Enterprise controls
21-
details: Apply policy, gateway holds, evidence, and operator workflows around agentic work.
22-
- title: Open trust boundary
23-
details: Keep identity, wallet custody, Trust Tasks, and signed approval in OpenVTC—not inside the portal.
18+
- title: A computer for each employee
19+
details: Give people an isolated cloud workspace with the AI agents and tools their work requires.
20+
- title: Clear company rules
21+
details: Decide what agents can access, what stays blocked, and which actions need a person.
22+
- title: Approval outside the application
23+
details: Use OpenVTC to keep identity, signing keys, and important decisions in a separate wallet.
2424
---
2525

2626
<div class="docs-home">
27-
<p class="eyebrow">Documentation · open source · enterprise runtime</p>
28-
<h2>From first install to governed production work.</h2>
27+
<p class="eyebrow">Documentation · open source · built for enterprise use</p>
28+
<h2>From your first local workspace to a production deployment.</h2>
2929
<p class="lede">
30-
ONEComputer is a thin business and enforcement layer over an open trust
31-
plane. These docs explain what is real today, how to run it, and where the
32-
remaining OpenVTC integration work belongs.
30+
These docs explain how to run ONEComputer, how its safeguards work, and
31+
which parts of the complete OpenVTC integration are available today.
3332
</p>
3433

3534
<div class="doc-grid">
3635
<a class="doc-card" href="./getting-started/installation">
3736
<span>01 · Start here</span>
38-
<b>Install the OSS stack</b>
37+
<b>Install ONEComputer</b>
3938
<p>Use the one-line installer or prepare an existing checkout without losing local state.</p>
4039
</a>
4140
<a class="doc-card" href="./getting-started/quickstart">
4241
<span>02 · Build</span>
4342
<b>Run the local quickstart</b>
44-
<p>Bring up PostgreSQL, migrations, the portal, and the Rust policy gateway.</p>
43+
<p>Start the database, prepare its tables, and run the portal and policy gateway.</p>
4544
</a>
4645
<a class="doc-card" href="./architecture/openvtc-boundary">
4746
<span>03 · Trust</span>
48-
<b>Read the OpenVTC boundary</b>
47+
<b>Understand OpenVTC approval</b>
4948
<p>Understand why approval happens in an external wallet and how the signed result returns.</p>
5049
</a>
5150
<a class="doc-card" href="./operations/azure-deployment">
5251
<span>04 · Operate</span>
5352
<b>Deploy to Azure</b>
54-
<p>See the service topology, systemd units, release gates, and health checks.</p>
53+
<p>See how the services fit together, how releases are checked, and how to monitor their health.</p>
5554
</a>
5655
<a class="doc-card" href="./governance/policy">
57-
<span>05 · Govern</span>
58-
<b>Design policy safely</b>
59-
<p>Separate business policy from cryptographic authority and keep defaults explicit.</p>
56+
<span>05 · Set rules</span>
57+
<b>Design clear company policy</b>
58+
<p>Choose what is allowed, blocked, recorded, or sent to a person for review.</p>
6059
</a>
6160
<a class="doc-card" href="./reference/status">
6261
<span>06 · Reality check</span>
6362
<b>Know the current status</b>
64-
<p>Track the verified implementation, the compatibility harnesses, and the E2E gaps.</p>
63+
<p>See what works today, what is still being integrated, and how completion is verified.</p>
6564
</a>
6665
</div>
6766

6867
<div class="boundary-note">
6968
<p>
70-
<strong>Security invariant:</strong> ONEComputer may display an approval
71-
request and its state, but it must never be the approval authority. The
72-
external OpenVTC wallet signs the exact held action; ONEComputer verifies
73-
the result before release.
69+
<strong>One rule we do not compromise:</strong> ONEComputer may show an
70+
approval request, but it cannot approve that request itself. A separate
71+
OpenVTC wallet signs the manager's decision, and ONEComputer checks that
72+
decision before the action continues.
7473
</p>
7574
</div>
7675
</div>

‎docs/reference/content-style.md‎

Lines changed: 53 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,53 @@
1+
# Writing and messaging
2+
3+
ONEComputer helps people use capable AI agents at work without giving those agents more access than the task requires. Our writing should make that idea feel understandable and useful—not remote or intimidating.
4+
5+
## Voice
6+
7+
Write with calm confidence. Begin with what a person is trying to accomplish, explain the practical tension, and then describe how the product helps. Use technical language when it adds precision, but explain the human meaning first.
8+
9+
Our voice is:
10+
11+
- **Human-first.** Talk about employees, managers, and security teams before systems and layers.
12+
- **Concrete.** Name the file, action, decision, or workspace instead of relying on abstract nouns.
13+
- **Candid.** Distinguish what works today from what is planned, and describe limitations plainly.
14+
- **Empowering.** Security exists to help people use agents responsibly, not to make AI sound frightening.
15+
- **Measured.** Avoid absolute safety claims. Explain the safeguards and what each one contributes.
16+
17+
## A useful order
18+
19+
Most product explanations should follow this sequence:
20+
21+
1. What people want to do.
22+
2. What becomes difficult or risky.
23+
3. How ONEComputer responds in practical terms.
24+
4. How OpenVTC supports decisions that need a person.
25+
5. Technical names and implementation detail, when the reader needs them.
26+
27+
For example:
28+
29+
> An employee asks Claude Code to prepare a customer report. Company policy allows the analysis but requires a manager to approve external sharing. ONEComputer pauses the export, and OpenVTC sends the exact request to the manager's separate wallet. The signed decision releases that request once.
30+
31+
## Preferred language
32+
33+
| Prefer | Avoid when plain language works |
34+
| --- | --- |
35+
| isolated cloud workspace | governed runtime |
36+
| company rules | policy plane |
37+
| pause the request | durable hold orchestration |
38+
| separate wallet | external authority surface |
39+
| signed decision | verifiable approval evidence |
40+
| the application cannot approve its own request | explicit trust-boundary separation |
41+
| works with different agents | agent-agnostic control plane |
42+
43+
Some technical terms remain necessary in architecture and protocol documentation. Introduce them after the reader understands their purpose.
44+
45+
## Claims and roadmap language
46+
47+
Use present tense only for capabilities in the working product. Mark roadmap integrations as **Planned** or **Coming soon**, and do not imply that a product is certified, compliant, or fully secure unless the repository contains current evidence for that claim.
48+
49+
Prefer descriptions such as “adds a safeguard,” “limits what the workspace can reach,” and “helps a manager verify the request” over absolute claims such as “guarantees safety” or “eliminates risk.”
50+
51+
## Calls to action
52+
53+
Buttons should tell the reader what they will see or do. Prefer “See how approvals work,” “Open this view,” and “Install locally” over vague labels such as “Learn more” or “Explore the surface.”

‎docs/reference/status.md‎

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
11
# Current status
22

3-
This page keeps the public docs honest. ONEComputer is under active integration work; the product direction is clear, but the complete production E2E is gated on the OpenVTC trust-plane path.
3+
This page distinguishes what works today from what still needs to be integrated. The product direction is clear, but the complete production journey still depends on the full OpenVTC approval path.
44

5-
## Working product surfaces
5+
## What works today
66

77
- local OSS installer and rerunnable setup path;
88
- Next.js web/API workspace;
@@ -12,7 +12,7 @@ This page keeps the public docs honest. ONEComputer is under active integration
1212
- CISO console, policy, approval, and audit presentation surfaces;
1313
- deployment and runner tooling versioned with the application.
1414

15-
## Open gates
15+
## What still needs to be completed
1616

1717
- OpenVTC-native login as the production identity authority;
1818
- role projection from verified VMC/M-DID/VTC claims;
@@ -24,8 +24,8 @@ This page keeps the public docs honest. ONEComputer is under active integration
2424

2525
## How to read “done”
2626

27-
Do not mark a gate complete because a screen exists, a fixture passes, a local adapter returns success, or a manually seeded record appears in the UI. A gate is complete when the runtime behavior, security invariant, test, and evidence artifact agree.
27+
Do not call an item complete because a screen exists or a local test returns success. It is complete only when the real system behaves as intended, the security rule is enforced, the test passes, and the resulting record agrees.
2828

2929
## North star
3030

31-
> Enterprises can give every team a secure Claude workspace while keeping identity, policy, approval authority, and evidence explicit—and OpenVTC remains the independent trust layer underneath.
31+
> Every employee can use the AI agent that fits their work in an isolated cloud computer, while company rules remain clear and important decisions stay with people through OpenVTC.

‎getting-started/index.html‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@
44
<meta charset="UTF-8" />
55
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
66
<meta name="theme-color" content="#1f1e1d" />
7-
<meta name="description" content="Install and run ONEComputer locally, then move to the full documentation." />
7+
<meta name="description" content="Install ONEComputer locally and launch your first isolated AI workspace." />
88
<title>Getting Started · ONEComputer</title>
99
<link rel="icon" href="/favicon.svg" type="image/svg+xml" />
1010
</head>

‎index.html‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -6,17 +6,17 @@
66
<meta name="theme-color" content="#1f1e1d" />
77
<meta
88
name="description"
9-
content="ONEComputer is the open-source enterprise control plane for safe cloud workspaces across Claude, NanoClaw, OpenClaw, Codex, Hermes Agent, and the agent stack that comes next."
9+
content="Give every employee an isolated cloud workspace for Claude, OpenClaw, Codex, and other agents—with company policy and human approval built in."
1010
/>
11-
<meta property="og:title" content="ONEComputer · Safe cloud workspaces for agentic work" />
11+
<meta property="og:title" content="ONEComputer · A safe computer for AI agents" />
1212
<meta
1313
property="og:description"
14-
content="Give every team a governed computer for their agent stack—with isolation, policy, external approval, and durable evidence built in."
14+
content="A ready-to-use cloud computer where AI agents can do real work, while company policy and human approval stay in control."
1515
/>
1616
<meta property="og:url" content="https://one-computer.github.io/" />
1717
<meta property="og:type" content="website" />
1818
<link rel="canonical" href="https://one-computer.github.io/" />
19-
<title>ONEComputer · Safe cloud workspaces for agentic work</title>
19+
<title>ONEComputer · A safe computer for AI agents</title>
2020
<link rel="icon" href="/favicon.svg" type="image/svg+xml" />
2121
</head>
2222
<body>

‎open-source/index.html‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@
44
<meta charset="UTF-8" />
55
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
66
<meta name="theme-color" content="#1f1e1d" />
7-
<meta name="description" content="Explore the open-source ONEComputer control plane, OpenVTC trust plane, wallet, and protocol repositories." />
7+
<meta name="description" content="Explore and run the open-source projects behind ONEComputer, OpenVTC, and the external VTI wallet." />
88
<title>Open Source · ONEComputer</title>
99
<link rel="icon" href="/favicon.svg" type="image/svg+xml" />
1010
</head>

‎openvtc/index.html‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,8 +4,8 @@
44
<meta charset="UTF-8" />
55
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
66
<meta name="theme-color" content="#1f1e1d" />
7-
<meta name="description" content="How OpenVTC gives AI agents verifiable identity, external wallet authority, signed approvals, and trustworthy evidence." />
8-
<title>OpenVTC: Verifiable Authority for AI Agents · ONEComputer</title>
7+
<meta name="description" content="A plain-language guide to how OpenVTC gives important AI-agent decisions a verifiable human source." />
8+
<title>What is OpenVTC? · ONEComputer</title>
99
<link rel="icon" href="/favicon.svg" type="image/svg+xml" />
1010
</head>
1111
<body data-page="openvtc">

0 commit comments

Comments
 (0)