Glean 拾遗
Recent picks

5picks · chronological

06-28

Loop Engineering: A Technical Roadmap for an Autonomous Loop

This is a technical roadmap for building reliable autonomous loops, arguing that a loop is fundamentally different from a prompt—a prompt requires manual initiation while a loop drives itself: set a goal once, then the system finds work, executes, checks, fixes, and repeats until completion. The author emphasizes that the ceiling is set not by prompting skills but by engineering a loop that converges toward truth rather than becoming an expensive random walk. The piece provides step-by-step guidance (Step 0 through Step 7) with working code (Bash scripts), explaining the mechanics of stateless iteration (fresh context per turn to combat context rot), building a narrow relevant context with a token budget, designing incorruptible checks (external deterministic oracle + reward-hacking defense gates + adversarial judge on a different model), dual-level state persistence (human-readable STATUS.md + machine-parseable JSON), physical isolation (git worktree, container with --network none), brakes with observability (structured JSONL log, circuit breakers for stuck/repeated failures, liveness heartbeats), and nonlinear cost analysis (why stateless keeps per-iteration cost constant while stateful grows quadratically). This is aimed at production engineers building AI agent pipelines who need practical, verifiable techniques.

06-26

ECC: Cross-Harness Agent Operating System for Claude Code, Cursor & Beyond

ECC is a comprehensive agent harness operating system designed to enhance multiple AI coding assistants including Claude Code, Cursor, Codex, OpenCode, and GitHub Copilot. It's not a standalone AI tool but a collection of 260+ skills, 67+ agents, persistent memory, continuous learning, cost optimization, and security auditing features. By providing unified rules, hooks, and MCP configurations across platforms, it addresses issues of inconsistent agent behavior, context loss, and inadequate security. Ideal for professional developers deeply using AI coding assistants and teams seeking standardized agent engineering practices.

github.com · 94 min · Agent Engineering · Claude Code · Context Engineering
06-15

Decomposing the agent harness into swappable workers: the iii engine architecture

Mike Piccolo argues that monolithic agent frameworks force a tradeoff by bundling the loop, tools, memory, and orchestration into one block, which long-running teams inevitably rewrite. He walks through the iii engine's production worker stack, where all thirteen harness responsibilities—credential resolution, policy checks, turn FSM, session persistence, budget tracking, etc.—are decomposed into 11 independently replaceable workers. Each worker connects to the engine via WebSocket and registers functions and triggers using a single primitive (iii.trigger()), making the harness a composable set of installable workers. The post provides a step-by-step trace of a turn through provisioning, streaming, policy-gated tool dispatch, and reactive approval wake-ups, alongside concrete examples of swapping the model catalog, adding a provider, or integrating a Slack approval surface. The core bet: an agent harness should be a slider of composable workers rather than a framework you fork. This is for backend engineers building or scaling custom agent infrastructure who are hitting the composability limits of existing frameworks.

06-08

Maple: An Open-Source Observability Platform Built on OpenTelemetry and ClickHouse

Maple is an open-source observability platform for traces, logs, and metrics, built on OpenTelemetry and ClickHouse. It features an OTLP ingest gateway with key-based auth, a chat agent, alert evaluation, and SQLite/Turso-backed dashboard persistence. The monorepo ships with Clerk or self-hosted auth modes and a full suite of CI/CD workflows for Cloudflare Workers, targeting teams that want to own their observability stack in a TypeScript-native codebase.

github.com · 9 min · ClickHouse · Cloudflare · Monorepo
06-05

OpenTelemetry Launches Blueprints Initiative to Simplify Enterprise Observability Adoption

OpenTelemetry has launched the Blueprints initiative to reduce the complexity of large-scale observability adoption. It provides prescriptive architectural patterns, operational best practices, and implementation steps for common scenarios, along with reference implementations from Adobe, Mastodon, Skyscanner, and others. The article explains how accidental complexity—fragmented pipelines, inconsistent semantic conventions, broken context propagation—emerges when organizations adopt OpenTelemetry organically without central standards. Blueprints focus on Kubernetes observability, non-Kubernetes infrastructure, and centralized telemetry platforms, aiming to operationalize telemetry consistently. The initiative reflects a broader shift toward opinionated operational frameworks in cloud-native infrastructure, targeting platform engineering, DevOps, and SRE teams grappling with observability sprawl.

www.infoq.com · 5 min · Cloud Native · Kubernetes · Observability