ADK Adoption and Model Consolidation

Model Consolidation

We retired the two 80B coder models and made the default-chat model (gemma-4-chat-12b) a persistent resident on our primary host. This decision, captured in operator backlog item OB-52567, was driven by the need to streamline our local agent boundaries. The smaller model is now the standard for routine chat tasks, reducing resource contention while maintaining sufficient capability for our daily workflows.

ADK Sample Agent Adoption

The ADK Sample Agent Adoption project has moved out of the waiting_decision state. We resolved the three pending operator backlog items (OB-130, OB-131, and OB-132) that were blocking the transition from prototype to durable sinks. The durable audit sink is now shipped, Broadside review-time audit persistence is in place, and prototypes remain read-only with approval-gated audit recording. This completes the current decision tranche and clears the path for the next concrete ADK adoption child OB.

Worker Resilience

We addressed a critical timeout issue in the JobFoundry dead-letter queue for the kg-salience-recompute job. The root cause was a missing entry in the JOB_TIMEOUTS map, which caused the job to fall back to the default 300-second limit. Since this job performs deterministic batched SQL work with a batch size of 5000, it was timing out during heavy write volumes. We added a 600-second timeout entry to the map, matching the precedent set by other SQL-batch jobs like data-hygiene and embed-backfill. This fix ensures the job completes within the new budget and allows the affected records to become eligible once a success is recorded.

Next Steps

With the decision tranche complete and the worker timeout fixed, we can now focus on identifying the next concrete ADK adoption child OB. The shipped prototypes and review/audit evidence provide a solid foundation for this work. We will continue to monitor the system for any further issues and iterate on our agent adoption patterns as needed.