AI Spark: Governed Entry Point for AI in Regulated Environments

Maintenance release for the AI Spark full stack deployment. The CAP Agent engine moves to build 30180 and now reports 12.1.14 B30180: an agent that cannot load a deployed configuration now reports the cause to the CAP Console and is left without a running configuration, instead of restarting its previous configuration against files the deploy had already replaced. The deployment's initial configuration snapshot is re-cut against this release and carries Base Rules build 30180. The embedded Jetty runtime stays at 12.1.14 and Java moves to 21.0.13. This is a drop-in replacement for cap-agent:48a29b4: the CloudFormation template URL, launch steps, template parameters, task definition shape, environment variables, EFS mount path, port mappings (8080 web, 20001 management), ALB health check path, and CAP Console connection workflow are all unchanged.

Upgrading to this release: Existing stacks pick up the new image on their next service update (force a new deployment of the agent service); no template change or stack update is needed. Install Base Rules 30180 through the CAP Console update workflow and redeploy to bring existing agents current - the configuration snapshot only seeds new deployments. Apply CAP Console 12.1.14:30180 as well to see the cause of a failed configuration load on the agent status panel; an earlier CAP Console still does not start an agent whose load failed, but the cause is then only in the agent log. If you are upgrading from an image older than cap-agent:48a29b4, the first configuration deploy to each agent sends the full set of extensions once. Step-by-step upgrade instructions: https://tomorrowx.com/go/cap-distribution-refresh 

Documentation: https://docs.tomorrowx.com/cap/vZHo2144m1e79o3WX0RU  Support: help@tomorrowx.dev 

Engine fix: When a deployed configuration could not be loaded, for example because an extension it needs was missing, the agent logged the error but told the CAP Console the reload had succeeded. The CAP Console then started the agent, which revived its previous configuration against files the deploy had already replaced, and the error that surfaced pointed at the wrong thing. In build 30180 the agent reports the failure and its cause to the CAP Console and is left without a running configuration, the same state as an agent that has not yet been deployed to; the CAP Console shows the cause on the agent status panel and does not start the agent. Correct the cause and deploy again. After a failed load, loads triggered by incoming web requests are retried at most every 30 seconds. Agents whose configuration loads normally are not affected.

Base Rules 30180: Agents using scoped deploys no longer fail to load for want of the Apache Commons IO library, which now ships with Base Rules. File and batch input keep to the Concurrent thread limit, so an agent with a low value may process files more slowly; raise the setting where needed. Socket listeners can limit how many connections they serve at once and close connections that have gone idle. UDP messages and replies now arrive complete and at their real length rather than cut at 512 bytes. The file output log adaptor writes each line without holding up other agent work. Rule execution semantics are otherwise unchanged.

Snapshot refresh: The initial configuration snapshot the stack restores on first launch is re-cut against this release. It carries the 12 extensions used by the AI Spark deployment, including Base Rules build 30180 and the November 2026 release of the data set rules, from which the unused Sync Data Sets rule has been removed; the other extensions are the same releases as in the previous snapshot. The snapshot includes the agent's record of its active extensions, so the first deploy to a new stack sends only extensions that differ from it. Deployments created from this image start current; existing deployments update their extensions through the CAP Console update workflow as before.

Dependency review: Java moves to 21.0.13 (Temurin 21.0.13+9), the October 2026 Java update. No other library changes in the image: Jetty 12.1.14 with virtual threads on HTTP ingress, pgjdbc 42.7.13, and all prior CVE remediations are retained. Ubuntu 24.04 LTS base OS packages are refreshed to current at image build time. A healthy CAP Agent launch continues to log zero WARN, zero ERROR.

Compatibility: No breaking changes for existing customers. No CloudFormation template changes in this release - stacks launched with the same inputs behave identically. No session cookie changes, so no sign-out on update. CAP rulesets and extensions run unchanged on this image, except that a rule set still using the removed Sync Data Sets rule fails to load and now reports that on the agent status panel. The protocol between the CAP Console and the agent gains a failure reply to a reload; CAP Console and agent builds from before and after this release work together.