Google Cloud and the Philippines DICT Bring Public Sector AI Agents Into Deployment
The expanded collaboration uses Gemini Enterprise, AI agents, cybersecurity and connectivity programs for Philippine public services.
Key takeaways
Google Cloud and the Philippines Department of Information and Communications Technology announced an expanded multi-year collaboration in June 2026. The program includes public sector AI agents, Gemini Enterprise, Google Workspace, a cross-agency cyber defense alliance and connectivity infrastructure. For AI tool users, the case highlights governance, permissions, data grounding and measurable workflow impact.
Google Cloud announced on June 22, 2026 that it had expanded a multi-year collaboration with the Philippines Department of Information and Communications Technology. The work covers enterprise AI for public services, cyber defense and connectivity infrastructure.
Under the AI Agents for Public Sector program, DICT plans to use Gemini Enterprise Agent Platform to build, govern and optimize AI agents for e-government services. The agents are expected to help citizens ask about administrative procedures in local languages through text or voice interactions.
The case is useful beyond government. It shows that practical AI agent deployment depends on business data access, connector control, permission boundaries, security operations and measurable adoption metrics, not only model quality.
What this means for everyday users
For ENHE users, the main lesson is that AI agents should be evaluated as governed workflows. Teams need to check data access, connector permissions, auditability, security controls, account costs and productivity metrics before scaling adoption.
Tools you may use
Related tutorials
Related Tools And Tutorials
Use the following ENHE AI sections to continue from the news signal into tool selection, account-service guidance, or practical learning.
Related reading
Google Cloud Introduces the Gemini Agent for Work
Google Cloud introduced the Gemini agent at Gemini at Work on October 8, 2026. Google describes it as a universal work agent that can use an organization's business context, plan work, call skills and tools, connect to business systems, and return completed results inside documents, inboxes, and developer environments. The announcement also highlights model selection, cost controls, security, administration, and governance. Those claims define a product direction, not automatic permission to connect every data source. Before rollout, start with one bounded workflow, list the records and tools the agent can reach, separate read from write access, cap spend, require confirmation before messages or irreversible changes, verify the destination of generated work, and keep a human owner for exceptions and acceptance.
Gemini Live Avatar reaches general availability for enterprise real-time agents
Google Cloud announced general availability for Gemini 3.8 Live with Live Avatar in Gemini Enterprise on September 24. The service combines native speech-to-speech dialogue, synchronized video avatars, live camera or screen understanding, and background tool calls in one real-time session, with support for 97 languages. Google says curated avatars are available, while custom-avatar creation still requires enterprise allowlisting and identity verification. Generated audio and video streams carry SynthID watermarks. Enterprise pilots still need permission for a person's image and voice, clear disclosure that users are interacting with AI, and tests for interruption, weak networks, tool failure, language switching, and human takeover.
Google Cloud Storage Intelligence brings proactive governance to fast-growing AI data
Google Cloud announced general availability for Storage Intelligence advisor and expanded Cloud Storage batch operations on September 25. Google says AI training and inference pipelines create data quickly and change access patterns often, so problems may surface only after they appear on a bill. The advisor analyzes inventory and access behavior to produce actionable recommendations, while batch operations can apply remediations across large object sets. Teams should not turn every recommendation directly into an automated command. Confirm the affected objects, regions, retention policies, compliance obligations, and estimated cost, test on a limited scope, and retain audit evidence for misclassification, access disruption, and rollback.
Google's Gemini RLFT guide puts reward design at the center of quality control
Google Cloud published a practical guide to Gemini reinforcement-learning fine-tuning on September 25. Its managed RLFT service lets teams provide prompts and a reward function while the platform handles training infrastructure and proprietary model internals. Google says the method fits tasks that are difficult to demonstrate but easy to score, and only when the base model already succeeds some of the time. Prompting and supervised fine-tuning should be exhausted first. The reward function is the main control surface, so teams need offline tests for malformed outputs, length bias, reward hacking, and train-evaluation leakage, then should stop at validation saturation rather than automatically choosing the last checkpoint.
A durable agent-harness checklist for context, tools, and stop conditions
Google Cloud published an Agent Factory interview recap on September 25 that defines an agent harness as everything around the language model: intent handling, live tools, context assembly, workspace interaction, and execution control. The post argues that a gap remains between theoretical frontier-model capability and useful work extracted in production, and that teams should shift interventions left by preparing context, environments, and validation before a task begins. This makes a durable engineering checklist: whenever a model, tool, permission, or workspace changes, revalidate context provenance, tool contracts, state persistence, stop conditions, human takeover, and results in the real target environment. Teams should verify every vendor-reported result against their own workloads, controls, data boundaries, and operating environment before making a production decision.
AlloyDB introduces PostgreSQL for agents with isolated real-time access
Google Cloud announced a preview of PostgreSQL for agents in AlloyDB on September 24. The architecture can provision isolated sandbox database instances in seconds and give them up-to-date read-only access to production data, absorbing bursty query loops from agent workloads before scaling down when the work ends. Google also highlights IAM authentication, VPC Service Controls, customer-managed encryption, and auditing. Preview capacity, latency, cost, and consistency still need measurement with representative queries. Read-only access reduces write risk but does not replace sensitive-field controls, tenant isolation, query budgets, or stopping rules for a looping agent. Teams should verify every vendor-reported result against their own workloads, controls, data boundaries, and operating environment before making a production decision.
Summary
Public sector AI agents are moving toward governed and measurable deployment. Enterprises and small teams can apply the same logic when piloting AI workflows: start with clear data, permission, security and measurement boundaries.
Sources
FAQ
What is this ENHE AI article about?
Google Cloud and the Philippines Department of Information and Communications Technology announced an expanded multi-year collaboration in June 2026. The program includes public sector AI agents, Gemini Enterprise, Google Workspace, a cross-agency cyber defense alliance and connectivity infrastructure. For AI tool users, the case highlights governance, permissions, data grounding and measurable workflow impact.
Why is this AI update worth watching?
Google Cloud and DICT announced an expanded multi-year AI and cybersecurity collaboration in June 2026. DICT plans to use Gemini Enterprise Agent Platform to build and govern AI agents for public services. More than 50,000 public servants will initially receive Gemini Enterprise app access, with a plan to reach over 200,000 in 18 months. The case underlines the importance of data grounding, permissions, account governance, security and ROI metrics.
What does it mean for everyday AI users?
For ENHE users, the main lesson is that AI agents should be evaluated as governed workflows. Teams need to check data access, connector permissions, auditability, security controls, account costs and productivity metrics before scaling adoption.
Where can readers continue learning on ENHE AI?
Readers can continue with ENHE AI software apps, AI skill tutorials, and AI account service guidance to turn the news signal into practical action.
Table of contents
Google Cloud and the Philippines DICT Bring Public Sector AI Agents Into Deployment