@the-ai-company/cbio-node-runtime 0.39.0 → 1.0.0

package/docs/WORKS_WITH_CUSTOM_FETCH.md

@@ -1,196 +1,21 @@
-# Works With SDKs That Support Custom Fetch
+# Custom Fetch Notes
 
-This is the recommended integration path for `@the-ai-company/agent-identity-sdk`.
+This repository no longer exposes the old `CbioIdentity` custom-fetch surface.
 
-If a provider SDK accepts a custom `fetch`, you can keep the provider's official client and still avoid ever reading the API key in plaintext.
+In the current first version:
+- agent code creates signed dispatch requests through `clients/agent`
+- transport goes through `vault-ingress`
+- outbound authenticated HTTP is performed inside `vault-core` via `HttpDispatchExecutor`
+- `send_secret` dispatch may return response bodies to the agent
+- `acquire_secret` does not return raw response values; it returns protocol metadata plus a redacted response shape
+- `acquire_secret` currently supports only built-in standard extraction flows, not caller-defined extractors
+- owner-defined HTTP boundaries are created through `createOwnerHttpFlowBoundary(...)`
+- `createStandardAcquireBoundary(...)` and `createStandardDispatchBoundary(...)` derive the two built-in default boundaries
+- `custom_http` exists as an owner-defined exception path with fixed mode/target/method/response visibility
 
-## Why this is the preferred path
+That split is intentional:
 
-- you keep using the provider's official SDK surface
-- the vault still injects authentication headers for each request
-- agent logic never needs `identity.getSecret(...)`
-- the integration stays close to normal provider examples
+- `acquire_secret` treats the response path as sensitive
+- `send_secret` treats the downstream HTTP response as standard protocol output after owner approval
 
-## General pattern
-
-```ts
-const authFetch = agent.createFetchWithAuth('provider-secret-name');
-
-const client = new ProviderSDK({
-  fetch: authFetch,
-});
-```
-
-Use `fetchWithAuth(...)` instead when you do not need the provider SDK at all.
-
-## OpenAI
-
-The official OpenAI JavaScript SDK supports a custom `fetch` function.
-
-```ts
-import OpenAI from 'openai';
-import { CbioIdentity } from '@the-ai-company/agent-identity-sdk';
-
-const identity = await CbioIdentity.load({
-  privateKey: process.env.AGENT_PRIV_KEY!,
-});
-
-const agent = identity.getAgent();
-
-const openai = new OpenAI({
-  fetch: agent.createFetchWithAuth('openai'),
-});
-
-const response = await openai.responses.create({
-  model: 'gpt-4.1',
-  input: 'Say hello in one sentence.',
-});
-```
-
-Store the secret under a name like `openai`, then reuse that secret name for all OpenAI requests.
-
-## Anthropic
-
-The official Anthropic TypeScript SDK also supports a custom `fetch` function.
-
-```ts
-import Anthropic from '@anthropic-ai/sdk';
-import { CbioIdentity } from '@the-ai-company/agent-identity-sdk';
-
-const identity = await CbioIdentity.load({
-  privateKey: process.env.AGENT_PRIV_KEY!,
-});
-
-const agent = identity.getAgent();
-
-const anthropic = new Anthropic({
-  fetch: agent.createFetchWithAuth('anthropic'),
-});
-
-const message = await anthropic.messages.create({
-  model: 'claude-sonnet-4-5',
-  max_tokens: 256,
-  messages: [{ role: 'user', content: 'Say hello in one sentence.' }],
-});
-```
-
-Use a dedicated secret name such as `anthropic`.
-
-## Other SDKs that support custom fetch
-
-Use the same pattern for any SDK that accepts:
-
-- `fetch`
-- a custom HTTP client built on `fetch`
-- request options that let you swap the transport layer
-
-The SDK does not need to know anything about Claw-biometric. It only needs to accept a `fetch` implementation.
-
-## If the SDK does not support custom fetch
-
-Do not solve that by calling `identity.getSecret(...)` inside agent logic just to feed a constructor that wants `apiKey: string`.
-
-Use one of these official alternatives instead:
-
-## Option 1: Call the provider API directly
-
-Best when:
-
-- the provider has a normal HTTP API
-- you only need a few endpoints
-- you want the smallest trusted surface
-
-Example:
-
-```ts
-const response = await agent.fetchWithAuth(
-  'resend',
-  'https://api.resend.com/emails',
-  {
-    method: 'POST',
-    headers: { 'Content-Type': 'application/json' },
-    body: JSON.stringify({
-      from: 'onboarding@example.com',
-      to: ['user@example.com'],
-      subject: 'Hello',
-      html: '<strong>Welcome</strong>',
-    }),
-  }
-);
-```
-
-This is the recommended path for SDKs whose official client only accepts a raw API key.
-
-## Option 2: Use a local trusted proxy or broker
-
-Best when:
-
-- your team wants to keep the provider's official SDK
-- the SDK only accepts `apiKey: string`
-- you want to isolate key use from agent logic
-
-Pattern:
-
-```text
-agent/runtime -> local trusted broker -> provider API
-```
-
-The agent talks to a local process over HTTP or IPC. The local process holds `identity` privileges or another trusted handle and injects authentication on the outbound request.
-
-With the runtime helper, configure the upstream explicitly:
-
-```ts
-const proxy = await startLocalAuthProxy({
-  authHandle: agent,
-  secretName: 'openai',
-  upstreamBaseUrl: 'https://api.openai.com',
-});
-```
-
-For providers that do not use `Authorization: Bearer ...`, override the auth settings:
-
-```ts
-const proxy = await startLocalAuthProxy({
-  authHandle: agent,
-  secretName: 'anthropic',
-  upstreamBaseUrl: 'https://api.anthropic.com',
-  authHeaderName: 'x-api-key',
-  authPrefix: '',
-});
-```
-
-Common examples:
-
-- OpenAI: `upstreamBaseUrl: 'https://api.openai.com'`
-- Anthropic: `upstreamBaseUrl: 'https://api.anthropic.com'`, `authHeaderName: 'x-api-key'`, `authPrefix: ''`
-- Resend: `upstreamBaseUrl: 'https://api.resend.com'`
-
-## Option 3: Run key-holding code in a separate trusted process
-
-Best when:
-
-- you already have a worker/service boundary
-- you need the provider SDK exactly as-is
-- you want process-level separation without introducing a local HTTP proxy
-
-Pattern:
-
-1. trusted process loads `AGENT_PRIV_KEY`
-2. trusted process creates `identity`, then `agent`
-3. untrusted process calls into the trusted process over RPC, IPC, or a queue
-
-The important part is not the transport. The important part is that the untrusted runtime never gets plaintext credentials and never gets `identity`.
-
-## Decision guide
-
-Use this order:
-
-1. If the SDK supports custom `fetch`, use `createFetchWithAuth(...)`.
-2. If you only need HTTP calls, use `fetchWithAuth(...)` directly.
-3. If the SDK only accepts a raw key, use a trusted proxy or separate trusted process.
-
-Avoid:
-
-- `identity.getSecret(...)` inside agent logic
-- passing plaintext API keys into prompts, tools, or third-party SDK constructors
-- loading `AGENT_PRIV_KEY` in the same process as untrusted tools or model-driven code
+If a future SDK-facing custom-fetch helper is added, it must be implemented on top of the current vault-first modules.

package/docs/es/README.md

@@ -1,27 +1,11 @@
-# cbio Node Runtime
+# cbio Vault Runtime
 
-Runtime Node.js para caja de identidad y credenciales cbio. Solo biblioteca, sin CLI ni TUI.
+Primera version publica del runtime centrado en autoridad.
 
-Importa y usa `CbioIdentity`, `CbioAgent` desde el export principal.
+Superficie principal:
+- `vault-core`
+- `clients/owner`
+- `clients/agent`
+- `vault-ingress`
 
-## Instalación
-
-```bash
-npm install @the-ai-company/cbio-node-runtime
-```
-
-## Uso
-
-```ts
-import { CbioIdentity, generateIdentityKeys } from '@the-ai-company/cbio-node-runtime';
-
-const keys = generateIdentityKeys();
-const identity = await CbioIdentity.load({ privateKey: keys.privateKey });
-```
-
-## Compilación
-
-```bash
-npm run build
-npm run test
-```
+La API antigua centrada en `CbioIdentity` ya no forma parte del producto.

package/docs/fr/README.md

@@ -1,27 +1,11 @@
-# cbio Node Runtime
+# cbio Vault Runtime
 
-Runtime Node.js pour le coffre d'identité et de credentials cbio. Bibliothèque uniquement, pas de CLI ni TUI.
+Premiere version publique du runtime centre sur l'autorite.
 
-Importez et utilisez `CbioIdentity`, `CbioAgent` depuis l'export principal.
+Surface principale :
+- `vault-core`
+- `clients/owner`
+- `clients/agent`
+- `vault-ingress`
 
-## Installation
-
-```bash
-npm install @the-ai-company/cbio-node-runtime
-```
-
-## Utilisation
-
-```ts
-import { CbioIdentity, generateIdentityKeys } from '@the-ai-company/cbio-node-runtime';
-
-const keys = generateIdentityKeys();
-const identity = await CbioIdentity.load({ privateKey: keys.privateKey });
-```
-
-## Compilation
-
-```bash
-npm run build
-npm run test
-```
+L'ancienne API centree sur `CbioIdentity` ne fait plus partie du produit.

package/docs/ja/README.md

@@ -1,27 +1,11 @@
-# cbio Node Runtime
+# cbio Vault Runtime
 
-cbio アイデンティティと credential vault の Node.js ランタイム。ライブラリのみ、CLI / TUI なし。
+Vault first の第一版ランタイムです。
 
-メインエクスポートから `CbioIdentity`、`CbioAgent` をインポートして使用。
+主な公開モジュール:
+- `vault-core`
+- `clients/owner`
+- `clients/agent`
+- `vault-ingress`
 
-## インストール
-
-```bash
-npm install @the-ai-company/cbio-node-runtime
-```
-
-## 使用例
-
-```ts
-import { CbioIdentity, generateIdentityKeys } from '@the-ai-company/cbio-node-runtime';
-
-const keys = generateIdentityKeys();
-const identity = await CbioIdentity.load({ privateKey: keys.privateKey });
-```
-
-## ビルド
-
-```bash
-npm run build
-npm run test
-```
+旧 `CbioIdentity` 中心 API は公開面から外れています。

package/docs/ko/README.md

@@ -1,27 +1,11 @@
-# cbio Node Runtime
+# cbio Vault Runtime
 
-cbio identity 및 credential vault용 Node.js 런타임. 라이브러리만 제공, CLI/TUI 없음.
+vault-first 1차 공개 런타임입니다.
 
-메인 export에서 `CbioIdentity`, `CbioAgent`를 import하여 사용.
+주요 공개 모듈:
+- `vault-core`
+- `clients/owner`
+- `clients/agent`
+- `vault-ingress`
 
-## 설치
-
-```bash
-npm install @the-ai-company/cbio-node-runtime
-```
-
-## 사용법
-
-```ts
-import { CbioIdentity, generateIdentityKeys } from '@the-ai-company/cbio-node-runtime';
-
-const keys = generateIdentityKeys();
-const identity = await CbioIdentity.load({ privateKey: keys.privateKey });
-```
-
-## 빌드
-
-```bash
-npm run build
-npm run test
-```
+이전 `CbioIdentity` 중심 API 는 더 이상 제품 표면이 아닙니다.

package/docs/pt/README.md

@@ -1,27 +1,11 @@
-# cbio Node Runtime
+# cbio Vault Runtime
 
-Runtime Node.js para cofre de identidade e credenciais cbio. Apenas biblioteca, sem CLI ou TUI.
+Primeira versao publica do runtime vault-first.
 
-Importe e use `CbioIdentity`, `CbioAgent` do export principal.
+Superficie principal:
+- `vault-core`
+- `clients/owner`
+- `clients/agent`
+- `vault-ingress`
 
-## Instalação
-
-```bash
-npm install @the-ai-company/cbio-node-runtime
-```
-
-## Uso
-
-```ts
-import { CbioIdentity, generateIdentityKeys } from '@the-ai-company/cbio-node-runtime';
-
-const keys = generateIdentityKeys();
-const identity = await CbioIdentity.load({ privateKey: keys.privateKey });
-```
-
-## Compilação
-
-```bash
-npm run build
-npm run test
-```
+A antiga API centrada em `CbioIdentity` nao faz mais parte do produto.

package/docs/zh/README.md

@@ -1,8 +1,12 @@
-# cbio Node Runtime
+# cbio Vault Runtime
 
-cbio 身份与凭证保险库的 Node.js 运行时。仅库，无 CLI 或 TUI。
+cbio 权限核心运行时。仅库，无 CLI 或 TUI。
 
-从主入口导入并使用 `CbioIdentity`、`CbioAgent`。
+主入口现在围绕四个模块：
+- `vault-core`
+- `clients/owner`
+- `clients/agent`
+- `vault-ingress`
 
 ## 安装
 
@@ -13,12 +17,22 @@ npm install @the-ai-company/cbio-node-runtime
 ## 使用
 
 ```ts
-import { CbioIdentity, generateIdentityKeys } from '@the-ai-company/cbio-node-runtime';
-
-const keys = generateIdentityKeys();
-const identity = await CbioIdentity.load({ privateKey: keys.privateKey });
+import {
+  createVaultService,
+  InMemoryVaultCapabilityResolver,
+  LocalVaultTransport,
+  createOwnerClient,
+  createAgentClient,
+} from '@the-ai-company/cbio-node-runtime';
 ```
 
+## 架构
+
+1. secret 明文只存在于 `vault-core`
+2. `clients/owner` 负责 owner 写入与审计读取
+3. `clients/agent` 负责 agent 签名 dispatch 请求
+4. `vault-ingress` 负责在 vault 边界内部处理 capability 解析与 dispatch ingress
+
 ## 构建
 
 ```bash

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@the-ai-company/cbio-node-runtime",
-  "version": "0.39.0",
+  "version": "1.0.0",
   "description": "Node.js runtime for cbio identity and credential vault. Library only, no CLI or TUI.",
   "type": "module",
   "main": "./dist/runtime/index.js",
@@ -17,14 +17,6 @@
     ".": {
       "import": "./dist/runtime/index.js",
       "types": "./dist/runtime/index.d.ts"
-    },
-    "./protocol": {
-      "import": "./dist/protocol/identity.js",
-      "types": "./dist/protocol/identity.d.ts"
-    },
-    "./sealed": {
-      "import": "./dist/sealed/index.js",
-      "types": "./dist/sealed/index.d.ts"
     }
   },
   "dependencies": {
@@ -34,7 +26,7 @@
     "build": "node ./scripts/clean-dist.mjs && tsc",
     "prepare": "npm run build",
     "test": "npm run build && npm run test:acceptance",
-    "test:acceptance": "node tests/runtime/derivation.js && node tests/runtime/errors.js && node tests/runtime/hardened_vault.js && node tests/runtime/isolation_local.js && node tests/runtime/managed_agent_identity.js && node tests/runtime/merge_security_local.js && node tests/runtime/recursive_cbio.js && node tests/runtime/register_child.js && node tests/runtime/transparency.js && node tests/runtime/vault_resilience.js && node tests/runtime/activity_log.js && node tests/runtime/secret_rotation_policy.js && node tests/runtime/local_auth_proxy.js && node tests/runtime/local_secret_ingress.js && node tests/runtime/local_secret_proof.js && node tests/runtime/local_secret_validate.js && node tests/runtime/generic_secret_validator.js && node tests/runtime/local_secret_guardrails.js && node tests/storage/adaptability.js && node tests/runtime/autosave.js"
+    "test:acceptance": "node tests/smoke/runtime-surface.js && node tests/smoke/policy-and-persistence.js && node tests/smoke/replay-guard.js && node tests/smoke/security-guards.js"
   },
   "keywords": [
     "claw-biometric",