@evident-ai/runner-cdk 0.1.1-dev.0fe02fb → 0.1.1-dev.d96ef8a

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -1,12 +1,19 @@
1
1
  # `@evident-ai/runner-cdk`
2
2
 
3
- A reusable AWS CDK construct for running **one scale-to-zero [Evident](https://evident.run)
4
- agent runner** on Fargate, in **your** AWS account, against **your** repo.
5
-
6
- The runner sleeps when nobody is talking to it: after `idleTimeoutSeconds` of inactivity
7
- the task scales its own service to `desiredCount 0`, and an HMAC-authenticated waker
8
- Lambda scales it back up on the next message. You pay for the time the agent is actually
9
- working.
3
+ Reusable AWS CDK constructs for running an [Evident](https://evident.run) agent runner in
4
+ **your** AWS account, against **your** repo. Two runner strategies:
5
+
6
+ - **`EvidentScaleToZeroConstruct`** **one scale-to-zero agent runner** on Fargate,
7
+ covered by the rest of this README. The runner sleeps when nobody is talking to it:
8
+ after `idleTimeoutSeconds` of inactivity the task scales its own service to
9
+ `desiredCount 0`, and an HMAC-authenticated waker Lambda scales it back up on the next
10
+ message. You pay for the time the agent is actually working.
11
+ - **`EvidentMicrovmConstruct`** — a per-session AWS Lambda MicroVM that boots on demand
12
+ and suspends between messages. It is not yet at Fargate's install-only parity here:
13
+ building its runner image still means cloning the `sroze/evident` repo (tracked in
14
+ [#1528](https://github.com/sroze/evident/issues/1528)). See
15
+ [the AWS runner doc](https://evident.run/docs/aws-runner) for the full picture of both
16
+ strategies.
10
17
 
11
18
  ## What it creates
12
19
 
@@ -108,14 +115,12 @@ built from a `Dockerfile` you control. The generic runner image lives separately
108
115
 
109
116
  ## Status / limitations
110
117
 
111
- - **Publishable, but not yet published.** The package is `@evident-ai/runner-cdk`
112
- (MIT), buildable to a self-contained `dist/` (`pnpm --filter @evident-ai/runner-cdk
113
- build`) with no `workspace:`/`@evident/*` runtime dependency see
114
- [#957](https://github.com/sroze/evident/issues/957). The **first** `npm publish` is a
115
- one-time human bootstrap step (OIDC/Trusted Publishing can't perform a package's
116
- first publish, same as [#612](https://github.com/sroze/evident/issues/612) was for
117
- `@evident-ai/runner-synchroniser`) and hasn't happened yet; until then this repo's own
118
- consumer (`infrastructure/evident-runner`) keeps consuming it as a `workspace:*`
119
- dependency, and following this guide outside this repo means working from a checkout.
118
+ - **Published to npm** as `@evident-ai/runner-cdk` (MIT) — see
119
+ [#957](https://github.com/sroze/evident/issues/957). Install it with `npm install
120
+ @evident-ai/runner-cdk` (or `pnpm add`/`yarn add`); no checkout of this repo is
121
+ required. It builds to a self-contained `dist/` (`pnpm --filter @evident-ai/runner-cdk
122
+ build`) with no `workspace:`/`@evident/*` runtime dependency. This repo's own
123
+ consumer (`infrastructure/evident-runner`) still consumes it as a `workspace:*`
124
+ dependency for dogfooding.
120
125
  - **AWS/ECS-specific.** Non-AWS clouds are an open question on the epic, not a supported
121
126
  path.