← Latest Update

Agent Ops: Gatekeeping, Logic, Safety, and Observability

Merge launches Agent Handler for Employees as an IT gatekeeper for workplace AI agents. Merge launches Agent Handler for Employees, letting IT enforce identity-based access and approved actions for workplace AI agents. Outcome engineers must design agents to operate inside identity- and intent-based gates with audit trails and enforceable actions — map this to Principle 15 (Gate) and Principle 10 (Law) when you set permissions and audits.

Beyond LLMs: Why Scalable Enterprise AI Adoption Depends on Agent Logic. IBM/Hugging Face argue agent logic — knowledge graphs, program analysis, and retrieval — is what makes agents scalable, accurate, and cost-effective for mission-critical enterprise workflows. Outcome engineers should treat context engineering and deterministic orchestration as first-class system components (Principles 06 and 09) rather than relying on raw model scale alone.

Anthropic’s browser agent got hijacked 31.5% of the time before safeguards engaged. VentureBeat reports Anthropic’s Opus 4.8 browser agent was hijacked in 31.5% of tests before safety mechanisms activated. That highlights prompt-injection and surface-specific risk—outcome engineers must instrument input boundaries, robust sanitization, and fast-engaging safety breakers (Principles 14 and 02) to avoid unsafe, silent failures in production.

How autoresearch found a 3-year-old bug in our query engine. PostHog shows an autoresearch loop discovered a three-year ClickHouse primary-key bug, cutting scanned granules 62% and automating performance investigations. This is a concrete template: build agentic monitoring and remediation loops to surface latent faults and shorten fix cycles—treat validation and continuous discovery as system artifacts (Principles 16 and 09).

Minimum viable AI observability: what to set up after shipping your first AI feature. PostHog publishes a hands-on playbook for essential AI observability—traces, cost tracking, and basic evals you can deploy quickly. Outcome engineers should instrument these cheap, high-leverage telemetry primitives early so you can measure correctness, cost, and drift before agents become business-critical (Principles 16 and 06).