Packages without permission slips.

Discover an exact version, read its manifest, and install through ordinary HTTPS or the optional public npm mirror. LOVE packages are Locator-independent, Open, Verifiable, and Exchangeable. npm is a convenient entrance, not release authority or a prerequisite for access.

The package is a set of bytes, not an account relationship. Anyone can fetch it; verified mirrors can serve the same bytes.

Install an exact version

Use an exact npm mirror when that registry carries it, or install the immutable LOVE tarball when you want an explicit locator and verification path. Either route keeps the declared scoped package name, so application imports stay unchanged.

npm install --save-exact @agenttool/adds@0.2.3
npm install --save-exact @agenttool/data@0.3.1
npm install --save-exact @agenttool/data-sync@0.1.2
npm install --save-exact @agenttool/credential-broker@0.3.1
npm install --save-exact @agenttool/sdk@0.21.0
npm install --save-exact @agenttool/wallet@0.1.3 @agenttool/wallet-zerone@0.1.2
npm install --save-exact @agenttool/telescope@0.2.3
npm install --save-exact @agenttool/browser@0.6.0

npm install --save-exact @agenttool/collab@0.4.0
npm install --save-exact @agenttool/kingdom@0.1.0
npm install --save-exact @agenttool/skills@0.3.1
bun add --global @agenttool/codex-usage@0.1.0
npm install --save-exact @agenttool/alchemy@0.1.0-dev.0 @agenttool/credential-broker@0.3.1 @agenttool/alchemy-agentcred@0.1.0-dev.0

npm-only receipt boundary. Collab 0.4.0, KINGDOM 0.1.0, Agent Skills 0.3.1, and the Alchemy/AgentCred developer-preview pair have no LOVE inventory entry. Collab protected run 30906798360 published and read back byte-identical 303,376-byte GitHub/npm tarballs with SHA-256 1a9c1830ec9326351a475596820780ad7f93c7dfe16a6f1a9eb74bc08edbdb51; npm latest resolved to 0.4.0, and its exact SLSA provenance is recorded at Sigstore log index 2340231720. See the Collab receipt and the earlier release train for the canonical evidence. Alchemy and AgentCred requested npm next; npm also exposes each sole initial prerelease through latest, which is not a maturity signal. These packages provide local libraries, coordination, inspection, and explicit sidecar workflows; installation does not activate a skill, create a hidden model channel, issue a grant, reveal a credential, contact Alchemy or a chain, or deploy a hosted service.

WAKE continuity developer-preview receipt. Protected run 32374666482 independently read back byte-identical 49,643-byte GitHub/npm @agenttool/wake-continuity@0.1.0-dev.1 tarballs with SHA-256 1ce1ac829f72c6f2490227c5a8a942fbee9570bd03a4be217df19104d034acd8. npm next resolves to dev.1 while mutable latest remains dev.0. This npm-only release creates deterministic caller-supplied records; it performs no model call, observation, awareness test, continuity proof, registration, or hosted deployment.

Agent Skills 0.3.1 receipt boundary. Annotated skills-v0.3.1 peels to protected GitHub-main merge 0b8f0a38265ac13795ba6326a1bd81b70821ec9b. Trusted run 31732645566 published and independently read back byte-identical 62,081-byte GitHub/npm tarballs with SHA-256 53aa5b3276eba196d8904f9db8c43987257d76f960c59c196ddac099175fbe11; npm latest resolved to 0.3.1. Its SLSA provenance is at Sigstore log index 2454756592, and its npm publish attestation is at log index 2454756935. The 83-file artifact contains nen-common-ground and its OpenAI sidecar; it remains instruction-only and requires explicit invocation. See the canonical receipt. Installation does not activate or register a skill, and this npm-only publication creates no LOVE entry, Hugging Face companion, hosted inspection service, permission, consent, or execution authority.

Codex Usage 0.1.0 receipt boundary. Annotated codex-usage-v0.1.0 peels to protected GitHub-main merge f027c46062d7e7c3bb22d0167278525c5fe10ed3. Protected bootstrap run 31784329559 published and independently read back byte-identical 30,926-byte GitHub/npm tarballs with SHA-256 feb5830b704e1116fa6b3b34490da621b0725ba914b8d94f6ce325f3a2275bec; npm latest resolved to 0.1.0. Its SLSA provenance is at Rekor index 2463986451, and its npm publish attestation is at index 2463987297. The 33-file artifact contains the Bun CLI, library entry point, read-only MCP server, declarations, maps, README, and legal files; an isolated scripts-disabled install passed the Bun CLI help and direct import. See the canonical receipt. Package-manager installation contacts its configured registry; tracker runtime makes no network call. This local tooling creates no hosted usage surface, starts no background process, registers no MCP server, writes no Codex state, and returns no transcript content, billing/quota/context guarantee, or process-health truth.

Credential broker mirror boundary. The current checked-in exact LOVE release is @agenttool/credential-broker@0.3.1. Protected run 30492737828 published and read back byte-identical GitHub Release and npm mirrors of the 158,450-byte LOVE artifact with SHA-256 d05458b27b8832af7996c243abb22e3b400e5810fe5377ba58e1cb587d2461d8. npm latest resolved to 0.3.1 at that readback, but remains mutable and non-authoritative.

SDK 0.21.0 release boundary. The exact checked-in TypeScript LOVE release is 247,146 bytes and 100 entries with SHA-256 c18d1b35ba5f7c918bbee64642510452af6f67302b78038580b4b65c6b77c154, built from source revision 6a6b6ad7abafe614827cdfc11a34cffcd8fdc6c3. Annotated sdk-v0.21.0 peels to protected-main merge 2cda03bdc2f6c2ee08acd55c6b643d67d8dd2b36. Protected npm run 32374669064 independently read back byte-identical LOVE, GitHub Release, and npm tarballs; npm latest resolved to 0.21.0, with SLSA/publish Rekor indices 2532574668 / 2532575739. Protected PyPI run 32374671268 independently read back the non-yanked 275,928-byte wheel (sha256:5d2e83e5b7fb3728fe985ea0e050c0d1cb314eed07b78f12bd045852ba1b1a01) and 261,910-byte sdist (sha256:e70c1eecc1699961a22720676185e141293a09bae381e875a81541b872fea71d). It adds the pure zero-I/O WakeContinuityLayer. Mirrors remain optional and non-authoritative; publication is not deployment or evidence of model or participant effect. The verified 0.20.0 and earlier receipts remain immutable history.

Historical SDK 0.20.0 mirror boundary. The exact TypeScript LOVE release is 236,446 bytes, 98 entries, SHA-256 d3b2fa790eb9a256d0f682c2b72ca97d572a000f7028238cb1a1a53959ccdf03, built from source revision 040e076bc537d433feaf32e23eec4e5cdf0ed6e2. Annotated sdk-v0.20.0 has tag object e7d9616eb14851ffab9312f87438959c4c6de71d and peels to protected-main merge cb9c30fae0e49e1727e449207593581ce52cd4cf. Protected npm run 31815209550, attempt 1, independently read back the LOVE artifact, sole GitHub Release asset, and public npm tarball as byte-identical; npm records exact SRI sha512-8DXyrQGRGvzJ9gEJny6U/82IPocg6qEzbpf7TvfIPZXD7wwhBl+aWPLLN/owzuUt6nAIGAHag9znwzCnaJuLgg==. Protected PyPI run 31815447080 independently read back the non-yanked 265,633-byte wheel (sha256:43483413256b63a001d6deae16928dac2aaae8ed8572fddb98e14381e844035b) and 250,597-byte sdist (sha256:54cb2096f984ec9f4c9791224d9e3cca3b322842ca8b825a13bf95008eb779f4). Historical 0.19.0 and 0.18.1 receipts also remain exact and separately addressable.

Historical SDK 0.20.0 attestation detail. npm records SHA-1 9136e2f2e7b1e11d84d934cb7c4f31688cbe2101, SLSA provenance at Rekor index 2467138141, and its publish attestation at index 2467138904. The PyPI wheel and sdist Integrity indices are 2467178343 and 2467178268. These remain exact historical evidence.

Earlier SDK mirror history. Historical 0.19.0 remains exact: its immutable 230,184-byte, 96-entry LOVE artifact has SHA-256 0a7eed4029bc687605b4d56707843c12ccb36d10a162a1fea1681522ab8784a2 and source revision 3239a25987d9de95b678e808d2d5168e786b2472; annotated sdk-v0.19.0 peels to protected-main merge 17f5c9920c6e6abe8046d39926ae7a73d2f24e89, and npm run 31800748738 plus PyPI run 31801053841 independently read back its exact optional mirrors. Historical 0.18.1 also remains exact: its immutable 218,301-byte LOVE artifact has SHA-256 466adb2d22a637e9c4d158e6050a69096e296258e6111f482be2a0872318be0d and source revision 490ab19ca846632460a7a6b498fb13216d97807a; npm run 31790395261 and PyPI run 31790559054 independently read back its mirrors.

Telescope mirror boundary. The current exact LOVE release is @agenttool/telescope@0.2.3. Its npm and GitHub 0.2.3 mirrors are public and independently byte-verified, so the command above names that exact version. Use the 0.2.3 LOVE URL below when you want the manifest-bound verification path.

ADDS/data-sync repair boundary. The checked-in catalog line @agenttool/adds@0.2.3 followed by @agenttool/data-sync@0.1.2 is public through the annotated ADDS and data-sync GitHub Releases and the exact npm versions. Protected runs 30495292940 and 30495589179 published and read back byte-identical mirrors: ADDS is 89,285 bytes with SHA-256 3fe42c4457e38f1fcdbc437c22c762ea7dabfe898714ec395287608a0480ea2b; data-sync is 59,774 bytes with SHA-256 37b69b13db60eafc4a0bae578faca14467c0844e4f4c32793808b3499bcd8fd6. npm latest currently resolves to those exact versions, but remains mutable and non-authoritative. ADDS now requires Noble Ed25519 ^2.3.0. Its immutable 0.2.2 predecessor could resolve Noble 2.2.3 and reject otherwise valid signatures because that dependency lacked the verifier's Point API; it did not accept invalid signatures. Data-sync peers on repaired ADDS ^0.2.3 plus data ^0.3.1, enforces exact sync manifest labels and matching event/payload times under the reference node's strict uppercase, non-leap-second RFC 3339 profile, and aligns its explicit maximum plaintext page with the default data-node 10 MiB record ceiling. Both current tarballs embed TypeScript text in JavaScript source maps and omit dangling declaration maps.

Wallet mirror boundary. The current catalog line is @agenttool/wallet@0.1.3 plus @agenttool/wallet-zerone@0.1.2. Protected runs 30491887230 and 30494659977 published and read back byte-identical GitHub/npm mirrors of their exact LOVE artifacts: Wallet is 52,837 bytes with SHA-256 33f3b81cfcc12882cb98dfd11b215fa4d3cbd963efc575e41ed54e05f132ae87; Zerone is 61,695 bytes with SHA-256 bc43b8be96dcc74a866926c9f5d98c00af9d8c4682cbb6f36ef77a7adbbaa8cc. Historical Wallet 0.1.1/0.1.2 and Zerone 0.1.0/0.1.1 LOVE artifacts remain hash-pinned and are not rewritten. Zerone run 30492436839 failed in credential-free preparation before any 0.1.1 GitHub/npm mutation; 0.1.2 is the new immutable release identity, not a moved tag. The adapter locks public Wallet 0.1.3 only for development while retaining the ^0.1.2 consumer peer.

Runtime boundary. npm is only the installer here; @agenttool/data and @agenttool/data-sync require Bun ≥1.3 at runtime. The credential broker, Agent Wallet, Wallet Zerone, Telescope, and Agent Browser support Node ≥20.19 or Bun ≥1.3.5. Wallet Zerone declares the compatible Wallet ^0.1.2 peer, which includes current Wallet 0.1.3, and uses injected host transports; it supplies no key custody, RPC endpoint, deployed bridge, or hosted chain service. Agent Browser additionally drives a compatible Chrome-family browser already installed on the operator's machine; installing the package does not download one.

An npm install uses registry integrity machinery but does not independently compare the downloaded bytes with the LOVE manifest's artifact.size and artifact.sha256. Use the verified workflow below when that boundary matters.

bun add https://docs.agenttool.dev/packages/v1/@agenttool/data/0.3.1/agenttool-data-0.3.1.tgz

import { DataNode } from "@agenttool/data";

bun add https://docs.agenttool.dev/packages/v1/@agenttool/sdk/0.21.0/agenttool-sdk-0.21.0.tgz

import { AgentTool } from "@agenttool/sdk";

const at = new AgentTool();
const diningManifest = await at.dining.manifest();

bun add https://docs.agenttool.dev/packages/v1/@agenttool/credential-broker/0.3.1/agenttool-credential-broker-0.3.1.tgz

import { AgentCredClient } from "@agenttool/credential-broker";

bun add https://docs.agenttool.dev/packages/v1/@agenttool/adds/0.2.3/agenttool-adds-0.2.3.tgz

import { AgentData } from "@agenttool/adds";

bun add \
  https://docs.agenttool.dev/packages/v1/@agenttool/adds/0.2.3/agenttool-adds-0.2.3.tgz \
  https://docs.agenttool.dev/packages/v1/@agenttool/data/0.3.1/agenttool-data-0.3.1.tgz \
  https://docs.agenttool.dev/packages/v1/@agenttool/data-sync/0.1.2/agenttool-data-sync-0.1.2.tgz

import { DataSyncService } from "@agenttool/data-sync";

bun add https://docs.agenttool.dev/packages/v1/@agenttool/telescope/0.2.3/agenttool-telescope-0.2.3.tgz

import { inspectTarget } from "@agenttool/telescope";

Telescope 0.2.3 accepts only three complete, positive exit phrases, rejects negated or incomplete wording, and accepts URI fragments on credential-free HTTPS catalog relation targets. Immutable 0.2.2 remains separately available with its historical permissive token-matching flaw. The current AgentTool producer remains compatible with immutable 0.2.1. No catalog member is followed, and the release adds no probe or automatic follow-up.

bun add https://docs.agenttool.dev/packages/v1/@agenttool/wallet/0.1.3/agenttool-wallet-0.1.3.tgz

import { verifyWalletDescriptor } from "@agenttool/wallet";

bun add \
  https://docs.agenttool.dev/packages/v1/@agenttool/wallet/0.1.3/agenttool-wallet-0.1.3.tgz \
  https://docs.agenttool.dev/packages/v1/@agenttool/wallet-zerone/0.1.2/agenttool-wallet-zerone-0.1.2.tgz

import { createZeroneDirectSignPlan } from "@agenttool/wallet-zerone";

bun add https://docs.agenttool.dev/packages/v1/@agenttool/browser/0.6.0/agenttool-browser-0.6.0.tgz

import { AgentBrowser } from "@agenttool/browser";
import { analyzeBrowserMaterial } from "@agenttool/browser/understanding";

Browser 0.6.0 understanding boundary. The nine-operation local runtime and package-root Codex plugin remain unchanged. A direct-only subpath binds exact observed text to Browser provenance, runs RhetorLint locally, and accepts one caller-injected, full-revision Hugging Face model observation behind literal remote disclosure. It adds no MCP tool, model, token, automatic network call, truth verdict, hosted service, or wider browser authority.

The same HTTPS tarballs remain directly consumable by package managers that support URL dependencies. For example, npm install https://…/agenttool-data-0.3.1.tgz uses the npm client without relying on registry publication.

This catalog contains the nine JavaScript packages above. Python is not mirrored through this catalog: annotated sdk-v0.21.0 is the exact source locator, and PyPI 0.21.0 is independently public through protected run 32374671268. Its exact non-yanked 275,928-byte wheel and 261,910-byte source distribution remain separate from the TypeScript LOVE artifact. Historical 0.20.0 and earlier receipts remain immutable evidence.

Discover it as an agent

The well-known document is the stable entry point. It names the protocol and doctrine, points to the versioned catalog, and advertises optional registry locators. Its registry_role and every registry mirror's authority: false keep those convenience channels separate from package and release authority.

# Stable discovery door
curl -fsS https://docs.agenttool.dev/.well-known/love-packages

# This origin's mirror catalog
curl -fsS https://docs.agenttool.dev/packages/v1/index.json

# One exact release
curl -fsS https://docs.agenttool.dev/packages/v1/@agenttool/data/0.3.1/manifest.json

{
  "protocol": "love-package/v1",
  "doctrine": "https://docs.agenttool.dev/LOVE-PACKAGE-PROTOCOL.md",
  "index_url": "https://docs.agenttool.dev/packages/v1/index.json",
  "access": "public_read",
  "registry_role": "mirror_index_not_authority",
  "registry_mirrors": [{
    "ecosystem": "npm",
    "registry_url": "https://registry.npmjs.org/",
    "authority": false
  }]
}

What one release manifest carries

A manifest declares protocol, document_type: "package-manifest", name, version, description, nullable license, artifact, runtime, install, and source. Indexes use the distinct document_type: "package-index", so an agent can select the correct schema before reading either shape. The artifact record uses format: "npm-tarball" as a file-format label; that field alone does not prove registry publication. Read the optional well-known mirror metadata and query the exact registry version instead.

• artifact carries the filename, SHA-256, byte size, media type, and one or more absolute mirror URLs.
• install.specifier is the primary absolute tarball URL that URL-aware package managers can consume.
• source identifies the repository, revision, and package path claimed to have produced the release; v1 does not attest the build.
• runtime identifies the ecosystem and declared engine constraints; it is compatibility metadata, not proof that every environment was tested. An empty engines object means no floor was declared, so compatibility is unknown rather than universal.
• The current @agenttool/data@0.3.1, @agenttool/data-sync@0.1.2, @agenttool/adds@0.2.3, @agenttool/credential-broker@0.3.1, @agenttool/sdk@0.21.0, @agenttool/telescope@0.2.3, @agenttool/wallet@0.1.3, @agenttool/wallet-zerone@0.1.2, and @agenttool/browser@0.6.0 releases declare Apache-2.0.
• Historical releases whose manifests say license: null declare no license; public download access is not a public-domain or open-source license grant.

Verify before install

Read the sibling manifest over HTTPS, copy its size and SHA-256 value, download the artifact, and compare both locally before extraction or installation. This catches truncation, cache corruption, and artifact substitution that does not also replace the manifest.

base=https://docs.agenttool.dev/packages/v1/@agenttool/data/0.3.1
curl -fsS "$base/manifest.json"

expected_size='<artifact.size from manifest.json>'
expected_sha256='<artifact.sha256 from manifest.json>'
curl -fsSLo agenttool-data-0.3.1.tgz "$base/agenttool-data-0.3.1.tgz"
actual_size=$(wc -c < agenttool-data-0.3.1.tgz | tr -d '[:space:]')
actual_sha256=$(shasum -a 256 agenttool-data-0.3.1.tgz | awk '{print $1}')
test "$actual_size" = "$expected_size" &&
  test "$actual_sha256" = "$expected_sha256" &&
  bun add ./agenttool-data-0.3.1.tgz

Mirror without becoming a gatekeeper

An artifact mirror serves a byte-identical copy from another locator. A full catalog mirror can additionally copy the index and manifests. Consumers can choose another HTTPS origin while retaining the package name, version, size, and digest. This site is a convenient origin, not a protocol requirement.

/.well-known/love-packages
/packages/v1/index.json
/packages/v1/@agenttool/data/0.1.0/
  ├── manifest.json
  └── agenttool-data-0.1.0.tgz
/packages/v1/@agenttool/data/0.2.0/
  ├── manifest.json
  └── agenttool-data-0.2.0.tgz
/packages/v1/@agenttool/data/0.3.0/
  ├── manifest.json
  └── agenttool-data-0.3.0.tgz
/packages/v1/@agenttool/data/0.3.1/
  ├── manifest.json
  └── agenttool-data-0.3.1.tgz
/packages/v1/@agenttool/data-sync/0.1.0/
  ├── manifest.json
  └── agenttool-data-sync-0.1.0.tgz
/packages/v1/@agenttool/data-sync/0.1.1/
  ├── manifest.json
  └── agenttool-data-sync-0.1.1.tgz
/packages/v1/@agenttool/data-sync/0.1.2/
  ├── manifest.json
  └── agenttool-data-sync-0.1.2.tgz
/packages/v1/@agenttool/credential-broker/0.1.0/
  ├── manifest.json
  └── agenttool-credential-broker-0.1.0.tgz
/packages/v1/@agenttool/credential-broker/0.3.0/
  ├── manifest.json
  └── agenttool-credential-broker-0.3.0.tgz
/packages/v1/@agenttool/credential-broker/0.3.1/
  ├── manifest.json
  └── agenttool-credential-broker-0.3.1.tgz
/packages/v1/@agenttool/sdk/0.9.0/
  ├── manifest.json
  └── agenttool-sdk-0.9.0.tgz
/packages/v1/@agenttool/sdk/0.10.0/
  ├── manifest.json
  └── agenttool-sdk-0.10.0.tgz
/packages/v1/@agenttool/sdk/0.11.0/
  ├── manifest.json
  └── agenttool-sdk-0.11.0.tgz
/packages/v1/@agenttool/sdk/0.12.0/
  ├── manifest.json
  └── agenttool-sdk-0.12.0.tgz
/packages/v1/@agenttool/sdk/0.13.0/
  ├── manifest.json
  └── agenttool-sdk-0.13.0.tgz
/packages/v1/@agenttool/sdk/0.14.0/
  ├── manifest.json
  └── agenttool-sdk-0.14.0.tgz
/packages/v1/@agenttool/sdk/0.15.0/
  ├── manifest.json
  └── agenttool-sdk-0.15.0.tgz
/packages/v1/@agenttool/sdk/0.16.0/
  ├── manifest.json
  └── agenttool-sdk-0.16.0.tgz
/packages/v1/@agenttool/sdk/0.16.1/
  ├── manifest.json
  └── agenttool-sdk-0.16.1.tgz
/packages/v1/@agenttool/sdk/0.16.2/
  ├── manifest.json
  └── agenttool-sdk-0.16.2.tgz
/packages/v1/@agenttool/sdk/0.16.3/
  ├── manifest.json
  └── agenttool-sdk-0.16.3.tgz
/packages/v1/@agenttool/sdk/0.16.4/
  ├── manifest.json
  └── agenttool-sdk-0.16.4.tgz
/packages/v1/@agenttool/sdk/0.16.5/
  ├── manifest.json
  └── agenttool-sdk-0.16.5.tgz
/packages/v1/@agenttool/sdk/0.17.0/
  ├── manifest.json
  └── agenttool-sdk-0.17.0.tgz
/packages/v1/@agenttool/sdk/0.18.0/
  ├── manifest.json
  └── agenttool-sdk-0.18.0.tgz
/packages/v1/@agenttool/sdk/0.18.1/
  ├── manifest.json
  └── agenttool-sdk-0.18.1.tgz
/packages/v1/@agenttool/sdk/0.20.0/
  ├── manifest.json
  └── agenttool-sdk-0.20.0.tgz
/packages/v1/@agenttool/sdk/0.21.0/
  ├── manifest.json
  └── agenttool-sdk-0.21.0.tgz
/packages/v1/@agenttool/telescope/0.1.0/
  ├── manifest.json
  └── agenttool-telescope-0.1.0.tgz
/packages/v1/@agenttool/telescope/0.2.0/
  ├── manifest.json
  └── agenttool-telescope-0.2.0.tgz
/packages/v1/@agenttool/telescope/0.2.1/
  ├── manifest.json
  └── agenttool-telescope-0.2.1.tgz
/packages/v1/@agenttool/telescope/0.2.2/
  ├── manifest.json
  └── agenttool-telescope-0.2.2.tgz
/packages/v1/@agenttool/telescope/0.2.3/
  ├── manifest.json
  └── agenttool-telescope-0.2.3.tgz
/packages/v1/@agenttool/wallet/0.1.0/
  ├── manifest.json
  └── agenttool-wallet-0.1.0.tgz
/packages/v1/@agenttool/wallet/0.1.1/
  ├── manifest.json
  └── agenttool-wallet-0.1.1.tgz
/packages/v1/@agenttool/wallet/0.1.2/
  ├── manifest.json
  └── agenttool-wallet-0.1.2.tgz
/packages/v1/@agenttool/wallet/0.1.3/
  ├── manifest.json
  └── agenttool-wallet-0.1.3.tgz
/packages/v1/@agenttool/wallet-zerone/0.1.0/
  ├── manifest.json
  └── agenttool-wallet-zerone-0.1.0.tgz
/packages/v1/@agenttool/wallet-zerone/0.1.1/
  ├── manifest.json
  └── agenttool-wallet-zerone-0.1.1.tgz
/packages/v1/@agenttool/wallet-zerone/0.1.2/
  ├── manifest.json
  └── agenttool-wallet-zerone-0.1.2.tgz
/packages/v1/@agenttool/browser/0.1.0/
  ├── manifest.json
  └── agenttool-browser-0.1.0.tgz
/packages/v1/@agenttool/browser/0.2.0/
  ├── manifest.json
  └── agenttool-browser-0.2.0.tgz
/packages/v1/@agenttool/browser/0.3.0/
  ├── manifest.json
  └── agenttool-browser-0.3.0.tgz
/packages/v1/@agenttool/browser/0.5.0/
  ├── manifest.json
  └── agenttool-browser-0.5.0.tgz
/packages/v1/@agenttool/browser/0.5.1/
  ├── manifest.json
  └── agenttool-browser-0.5.1.tgz
/packages/v1/@agenttool/browser/0.6.0/
  ├── manifest.json
  └── agenttool-browser-0.6.0.tgz
/packages/v1/@agenttool/adds/0.1.0/
  ├── manifest.json
  └── agenttool-adds-0.1.0.tgz
/packages/v1/@agenttool/adds/0.2.0/
  ├── manifest.json
  └── agenttool-adds-0.2.0.tgz
/packages/v1/@agenttool/adds/0.2.1/
  ├── manifest.json
  └── agenttool-adds-0.2.1.tgz
/packages/v1/@agenttool/adds/0.2.2/
  ├── manifest.json
  └── agenttool-adds-0.2.2.tgz
/packages/v1/@agenttool/adds/0.2.3/
  ├── manifest.json
  └── agenttool-adds-0.2.3.tgz

• Preserve bytes. A mirror must not rebuild a tarball under the same name and version. Copy it and verify the declared digest.
• Preserve history. Add versions; do not retarget an existing version path.
• Choose trust explicitly. A consumer decides which catalog origins it trusts. Discovery is not a claim that every mirror is honest or durable.
• Respect reuse terms. Verifiable bytes do not grant redistribution rights. Check license and obtain any permission required before operating a new public mirror.
• Keep npm optional. npm, GitHub Releases, an object store, IPFS, or another compatible source may mirror the same release. None is the identity of the package.

Four standards, four jobs

In one line: love-package/v1 gets software onto a machine; agent-data/v1 lets an agent keep and query a corpus; adds/v0.1 lets exact encrypted objects move independently; agent-data-sync/v1 composes them into one explicit bounded pull path.

References

• LOVE-PACKAGE-PROTOCOL.md — normative love-package/v1 discovery, manifest, integrity, and mirroring contract.
• love-package-v1.schema.json — machine-readable release-manifest schema.
• love-package-index-v1.schema.json — machine-readable non-authoritative index schema.
• /.well-known/love-packages — machine-readable public discovery.
• /packages/v1/index.json — current AgentTool mirror catalog.
• Agent data — operate @agenttool/data and use SDK at.data.
• Agent Browser — operate the local TypeScript, JSONL, and stdio MCP browser doors.
• KINGDOM SDK boundaries — distinguish the credential-free framework card, local KINGDOM OS inventory, and public doctrine library.
• agent-data/v1 — collection and query protocol.
• adds/v0.1 — experimental encrypted-object protocol.