@kybernesis/dispatch 0.1.0

package/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/NOTICE

@@ -0,0 +1,2 @@
+@kybernesis/dispatch
+Copyright 2026 Kybernesis (kybernesis.ai)

package/README.md

@@ -0,0 +1,84 @@
+# @kybernesis/dispatch
+
+Agent-to-agent dispatch for [eve](https://eve.dev) agents: declared remote-peer
+edges with principal forwarding on by default, and a receiver channel that makes
+trusting the wrong caller hard to express.
+
+Two separately deployed eve agents talk over a declared **edge**. The caller
+mounts a `remotePeer` under `agent/subagents/`; the receiver authors its eve
+channel with `dispatchChannel`. Underneath is eve's native `defineRemoteAgent`
+transport — durable park-and-resume dispatch, retried callbacks, recursive
+cancellation — with the governance defaults locked in.
+
+## Caller side — one file per peer
+
+```ts
+// agent/subagents/gtm.ts  (file name = tool name the model sees)
+import { remotePeer } from "@kybernesis/dispatch";
+
+export default remotePeer({
+  envVar: "GTM_AGENT_URL",
+  description:
+    "The company's GTM operator: posting cadence and history, open go-to-market plays, outreach targets, LinkedIn/X content drafting in the house voice.",
+});
+```
+
+The `description` is a **routing hint**, not documentation: the calling agent's
+model reads it to decide when to delegate. Write the concrete topics people
+actually ask about. A vague description means the edge never fires.
+
+Defaults you'd otherwise have to remember: outbound auth is Vercel OIDC, the
+URL resolves from env at runtime (no rebuild to repoint), and
+`forwardPrincipal: true` — the peer runs as the human who asked, so its memory
+scoping, per-user connections, and telemetry attribution see the real person.
+
+## Receiver side — enumerate your peers
+
+```ts
+// agent/channels/eve.ts
+import { dispatchChannel } from "@kybernesis/dispatch";
+
+export default dispatchChannel({
+  trustedPeers: [{ teamSlug: "acme", projectName: "acme-router" }],
+});
+```
+
+One declaration feeds both trust surfaces — the OIDC `subjects` allowlist
+(which deployments may call at all) and the `trustedForwarders` predicate
+(which of them may assert an end-user identity) — so the two can never drift
+apart. There is deliberately no predicate form: `trustedForwarders: () => true`
+(any authenticated caller asserts any identity, including your own preview
+deployments) is not expressible through this API. Peers default to
+`environment: "production"`; previews are never trusted implicitly.
+
+Your own project's deployments and `eve dev` keep working (current-project
+OIDC bypass + `localDev()`); production browser traffic stays rejected unless
+you pass your app's real auth via `extraAuth`.
+
+## Bidirectional edges
+
+Answering is built into one edge — the caller parks until the peer's terminal
+callback arrives, so request and response are one round trip on one wire. Add
+the mirror-image files only when the *other* agent should also be able to
+**initiate**: each direction is its own declared edge.
+
+## Operational rules
+
+- **Scheduled/proactive turns have no human to forward.** A turn triggered by
+  a cron schedule carries no signed-in principal, so a dispatch made from it
+  reaches the peer as the calling app's service identity even with
+  `forwardPrincipal: true`. Design peer-side capabilities that scheduled turns
+  rely on to be app-scoped (static keys), not user-scoped.
+
+- **Upgrade both ends of an edge together.** A receiver on an eve version
+  predating principal forwarding silently drops it and runs the session as the
+  calling app's service identity — a security downgrade with no error.
+- The env var (`GTM_AGENT_URL` above) holds the peer's stable production URL.
+  Unset with no `fallbackUrl` fails the dispatch loudly — intended.
+- Remote peers trace under their own deployment. Correlate hops in your
+  observability via the `eve:forwarded-by` attribute and the child session id
+  on the caller's `subagent.called` event.
+
+## License
+
+Apache-2.0

package/dist/channel.d.ts

@@ -0,0 +1,66 @@
+import { eveChannel } from "eve/channels/eve";
+import { type VercelSubjectEnvironment } from "eve/channels/auth";
+/**
+ * A peer deployment allowed to call this agent, named by its Vercel identity.
+ *
+ * Slugs, not IDs: `teamSlug` and `projectName` are the values embedded in the
+ * OIDC `sub` claim (what `vercel ls` shows), not `team_…`/`prj_…` IDs. They
+ * may not contain `*` or `:` — the underlying `vercelSubject` helper rejects
+ * wildcarded inputs so a typo cannot silently widen trust.
+ */
+export interface PeerRef {
+    /** Vercel team slug of the peer deployment (e.g. `"acme"`). */
+    teamSlug: string;
+    /** Vercel project name of the peer deployment (e.g. `"acme-router"`). */
+    projectName: string;
+    /**
+     * Which environment of the peer to trust. Defaults to `"production"` so a
+     * preview deployment can never assert identities against this agent unless
+     * you opt in explicitly.
+     */
+    environment?: VercelSubjectEnvironment;
+}
+/** Compose the OIDC subject string for a peer. Exposed for doctor checks and tests. */
+export declare function peerSubject(peer: PeerRef): string;
+/** Options for {@link dispatchChannel}. */
+export interface DispatchChannelOptions {
+    /**
+     * The deployments allowed to call this agent AND assert a forwarded
+     * end-user principal. Must be non-empty — an agent with no peers should
+     * simply not author a dispatch channel. There is deliberately no predicate
+     * form: enumerating concrete peers is the whole point.
+     */
+    trustedPeers: readonly PeerRef[];
+    /**
+     * Extra `AuthFn`s appended to the walk (e.g. your web app's auth for a
+     * browser frontend). The Vercel OIDC verifier for peers always runs first.
+     */
+    extraAuth?: Parameters<typeof eveChannel>[0] extends {
+        auth?: infer A;
+    } ? A : never;
+}
+/**
+ * The receiving side of an agent-to-agent edge: an authored eve channel that
+ * accepts calls — and forwarded end-user principals — from exactly the peers
+ * you enumerate.
+ *
+ * ```ts title="agent/channels/eve.ts"
+ * import { dispatchChannel } from "@kybernesis/dispatch";
+ *
+ * export default dispatchChannel({
+ *   trustedPeers: [{ teamSlug: "acme", projectName: "acme-router" }],
+ * });
+ * ```
+ *
+ * What you get over hand-rolling `eveChannel`:
+ *
+ * - Cross-project callers are enumerated in the OIDC `subjects` list AND the
+ *   `trustedForwarders` predicate from one declaration — the two lists cannot
+ *   drift apart.
+ * - `trustedForwarders: () => true` is not expressible: trust is a list of
+ *   concrete Vercel projects, never a function you can accidentally widen.
+ * - This project's own deployments and `eve dev` keep working (current-project
+ *   OIDC bypass + `localDev()`), and production browser traffic stays rejected
+ *   via `placeholderAuth()` unless you pass real auth in `extraAuth`.
+ */
+export declare function dispatchChannel(options: DispatchChannelOptions): import("eve/channels/eve").EveChannel;

package/dist/channel.js

@@ -0,0 +1,61 @@
+import { eveChannel } from "eve/channels/eve";
+import { localDev, placeholderAuth, vercelOidc, vercelSubject, } from "eve/channels/auth";
+/** Compose the OIDC subject string for a peer. Exposed for doctor checks and tests. */
+export function peerSubject(peer) {
+    return vercelSubject({
+        teamSlug: peer.teamSlug,
+        projectName: peer.projectName,
+        ...(peer.environment !== undefined
+            ? { environment: peer.environment }
+            : {}),
+    });
+}
+/**
+ * The receiving side of an agent-to-agent edge: an authored eve channel that
+ * accepts calls — and forwarded end-user principals — from exactly the peers
+ * you enumerate.
+ *
+ * ```ts title="agent/channels/eve.ts"
+ * import { dispatchChannel } from "@kybernesis/dispatch";
+ *
+ * export default dispatchChannel({
+ *   trustedPeers: [{ teamSlug: "acme", projectName: "acme-router" }],
+ * });
+ * ```
+ *
+ * What you get over hand-rolling `eveChannel`:
+ *
+ * - Cross-project callers are enumerated in the OIDC `subjects` list AND the
+ *   `trustedForwarders` predicate from one declaration — the two lists cannot
+ *   drift apart.
+ * - `trustedForwarders: () => true` is not expressible: trust is a list of
+ *   concrete Vercel projects, never a function you can accidentally widen.
+ * - This project's own deployments and `eve dev` keep working (current-project
+ *   OIDC bypass + `localDev()`), and production browser traffic stays rejected
+ *   via `placeholderAuth()` unless you pass real auth in `extraAuth`.
+ */
+export function dispatchChannel(options) {
+    const peers = options.trustedPeers;
+    if (!Array.isArray(peers) || peers.length === 0) {
+        throw new Error("dispatchChannel: trustedPeers must name at least one peer deployment — an agent with no peers should not author a dispatch channel.");
+    }
+    const subjects = peers.map(peerSubject);
+    const subjectSet = new Set(subjects);
+    const extra = (options.extraAuth ?? []);
+    return eveChannel({
+        auth: [
+            // Verifies which deployment is calling: this project's own tokens are
+            // always accepted; other projects only when enumerated as peers.
+            vercelOidc({ subjects }),
+            // Open on localhost for `eve dev` and the REPL; ignored in production.
+            localDev(),
+            ...extra,
+            // Rejects production browser traffic with a structured 401 unless the
+            // caller passed real auth above.
+            placeholderAuth(),
+        ],
+        // Only enumerated peers may assert a forwarded end-user principal.
+        trustedForwarders: (forwarder) => typeof forwarder.subject === "string" &&
+            subjectSet.has(forwarder.subject),
+    });
+}

package/dist/index.d.ts

@@ -0,0 +1,25 @@
+/**
+ * @kybernesis/dispatch — agent-to-agent dispatch for eve agents.
+ *
+ * Two deployed eve agents talk over a declared edge: the caller mounts a
+ * {@link remotePeer} under `agent/subagents/`, the receiver authors its eve
+ * channel with {@link dispatchChannel}. Together they give you eve's native
+ * `defineRemoteAgent` transport (durable park-and-resume dispatch) with the
+ * Kybernesis defaults locked in:
+ *
+ * - **Principal forwarding on by default** — the receiving agent runs as the
+ *   human who asked, so memory scoping, per-user connections, and telemetry
+ *   attribution compose across the hop unchanged.
+ * - **Peers are pinned, never open** — `dispatchChannel` only accepts an
+ *   enumerated list of Vercel projects. The `trustedForwarders: () => true`
+ *   footgun (any authenticated caller may assert any identity) is not
+ *   expressible through this API.
+ * - **URLs come from env** — edges resolve their target at runtime, so
+ *   repointing an agent never needs a rebuild.
+ *
+ * Both deployments must run compatible eve versions: a receiver predating
+ * principal forwarding silently drops it and runs the session as the calling
+ * app's service identity. Upgrade both ends of an edge together.
+ */
+export { remotePeer, type RemotePeerOptions } from "./remote-peer.js";
+export { dispatchChannel, peerSubject, type DispatchChannelOptions, type PeerRef, } from "./channel.js";

package/dist/index.js

@@ -0,0 +1,25 @@
+/**
+ * @kybernesis/dispatch — agent-to-agent dispatch for eve agents.
+ *
+ * Two deployed eve agents talk over a declared edge: the caller mounts a
+ * {@link remotePeer} under `agent/subagents/`, the receiver authors its eve
+ * channel with {@link dispatchChannel}. Together they give you eve's native
+ * `defineRemoteAgent` transport (durable park-and-resume dispatch) with the
+ * Kybernesis defaults locked in:
+ *
+ * - **Principal forwarding on by default** — the receiving agent runs as the
+ *   human who asked, so memory scoping, per-user connections, and telemetry
+ *   attribution compose across the hop unchanged.
+ * - **Peers are pinned, never open** — `dispatchChannel` only accepts an
+ *   enumerated list of Vercel projects. The `trustedForwarders: () => true`
+ *   footgun (any authenticated caller may assert any identity) is not
+ *   expressible through this API.
+ * - **URLs come from env** — edges resolve their target at runtime, so
+ *   repointing an agent never needs a rebuild.
+ *
+ * Both deployments must run compatible eve versions: a receiver predating
+ * principal forwarding silently drops it and runs the session as the calling
+ * app's service identity. Upgrade both ends of an edge together.
+ */
+export { remotePeer } from "./remote-peer.js";
+export { dispatchChannel, peerSubject, } from "./channel.js";

package/dist/remote-peer.d.ts

@@ -0,0 +1,60 @@
+import { defineRemoteAgent } from "eve";
+/** Options for {@link remotePeer}. */
+export interface RemotePeerOptions {
+    /**
+     * Environment variable holding the peer deployment's URL (e.g.
+     * `"GTM_AGENT_URL"`). Read at runtime on every dispatch, so repointing the
+     * edge is an env change, not a rebuild.
+     */
+    envVar: string;
+    /**
+     * Fallback URL when the env var is unset. Optional — without it, a missing
+     * env var fails the dispatch loudly, which is usually what you want in a
+     * fresh environment.
+     */
+    fallbackUrl?: string;
+    /**
+     * The routing hint. The calling agent's model reads this to decide when to
+     * delegate here — write it like the specialist's job description, with the
+     * concrete topics people actually ask about, not a generic blurb. A vague
+     * description means the edge never fires (or fires for the wrong asks).
+     */
+    description: string;
+    /**
+     * Forward the verified end-user principal across the hop (default `true`).
+     * The receiver must name this deployment in its `dispatchChannel`
+     * `trustedPeers` for the assertion to be accepted — otherwise the dispatch
+     * fails with a 403 rather than silently downgrading.
+     *
+     * Set `false` only when the peer should treat calls as coming from this
+     * app itself (service identity) rather than from the human behind it.
+     */
+    forwardPrincipal?: boolean;
+    /**
+     * JSON Schema for task-mode structured output. When set, the peer returns
+     * one validated result object instead of free text.
+     */
+    outputSchema?: Parameters<typeof defineRemoteAgent>[0]["outputSchema"];
+}
+/**
+ * Declares a separately deployed eve agent as a callable peer of this agent.
+ *
+ * Mount under `agent/subagents/<name>.ts` — the file name becomes the tool
+ * name the model sees. Lowers to the same `{ message }` tool shape as a local
+ * subagent, with eve's durable dispatch underneath: the calling turn parks
+ * without holding compute until the peer posts its terminal callback.
+ *
+ * ```ts title="agent/subagents/gtm.ts"
+ * import { remotePeer } from "@kybernesis/dispatch";
+ *
+ * export default remotePeer({
+ *   envVar: "GTM_AGENT_URL",
+ *   description:
+ *     "The company's GTM operator: posting cadence, open plays, outreach targets, content drafting.",
+ * });
+ * ```
+ *
+ * Outbound auth is always Vercel OIDC — the peer verifies which deployment is
+ * calling before any principal assertion is considered.
+ */
+export declare function remotePeer(options: RemotePeerOptions): import("eve").RemoteAgentDefinition;

package/dist/remote-peer.js

@@ -0,0 +1,39 @@
+import { defineRemoteAgent } from "eve";
+import { vercelOidc } from "eve/agents/auth";
+/**
+ * Declares a separately deployed eve agent as a callable peer of this agent.
+ *
+ * Mount under `agent/subagents/<name>.ts` — the file name becomes the tool
+ * name the model sees. Lowers to the same `{ message }` tool shape as a local
+ * subagent, with eve's durable dispatch underneath: the calling turn parks
+ * without holding compute until the peer posts its terminal callback.
+ *
+ * ```ts title="agent/subagents/gtm.ts"
+ * import { remotePeer } from "@kybernesis/dispatch";
+ *
+ * export default remotePeer({
+ *   envVar: "GTM_AGENT_URL",
+ *   description:
+ *     "The company's GTM operator: posting cadence, open plays, outreach targets, content drafting.",
+ * });
+ * ```
+ *
+ * Outbound auth is always Vercel OIDC — the peer verifies which deployment is
+ * calling before any principal assertion is considered.
+ */
+export function remotePeer(options) {
+    const { envVar, fallbackUrl, description, outputSchema } = options;
+    return defineRemoteAgent({
+        url: () => {
+            const url = process.env[envVar] ?? fallbackUrl;
+            if (!url) {
+                throw new Error(`remotePeer: ${envVar} is not set and no fallbackUrl was provided — set the peer deployment URL in the environment.`);
+            }
+            return url;
+        },
+        description,
+        auth: vercelOidc(),
+        forwardPrincipal: options.forwardPrincipal ?? true,
+        ...(outputSchema !== undefined ? { outputSchema } : {}),
+    });
+}

package/package.json

@@ -0,0 +1,51 @@
+{
+  "name": "@kybernesis/dispatch",
+  "version": "0.1.0",
+  "description": "Agent-to-agent dispatch for eve agents: declared remote-peer edges with principal forwarding on by default, and a receiver channel that makes trusting the wrong caller hard to express.",
+  "license": "Apache-2.0",
+  "type": "module",
+  "homepage": "https://kybernesis.ai",
+  "keywords": [
+    "eve",
+    "kybernesis",
+    "agent-to-agent",
+    "remote-agent",
+    "dispatch",
+    "a2a"
+  ],
+  "files": [
+    "dist",
+    "NOTICE"
+  ],
+  "exports": {
+    ".": {
+      "types": "./dist/index.d.ts",
+      "default": "./dist/index.js"
+    },
+    "./package.json": "./package.json"
+  },
+  "scripts": {
+    "build": "tsc -p tsconfig.build.json",
+    "prepare": "tsc -p tsconfig.build.json",
+    "typecheck": "tsc --noEmit"
+  },
+  "devDependencies": {
+    "@types/node": "24.x",
+    "eve": "0.30.8",
+    "typescript": "7.0.2"
+  },
+  "peerDependencies": {
+    "eve": ">=0.30.0 <0.31.0"
+  },
+  "engines": {
+    "node": ">=20"
+  },
+  "repository": {
+    "type": "git",
+    "url": "https://github.com/KybernesisAI/platform.git",
+    "directory": "packages/dispatch"
+  },
+  "publishConfig": {
+    "access": "public"
+  }
+}