---
type: "post"
stable_id: "post:agents-md-constitution-after-60b-tokens"
slug: "agents-md-constitution-after-60b-tokens"
title: "AGENTS.md Becomes The Operating Constitution"
description: "A long-running coding-agent practice turns AGENTS.md from a prompt convenience into an operational boundary for scope, verification, and local habits."
retrieval_nugget: "A long-running coding-agent practice turns AGENTS.md from a prompt convenience into an operational boundary for scope, verification, and local habits. A project instruction file starts as a convenience. After enough real agent work, it becomes something closer to operations infrastructure."
status: "published"
published_at: "2026-08-04"
updated_at: "2026-08-04"
record_date: "2026-08-04"
date_kind: "published_at"
topics: ["coding-agents","operations","developer-tools","memory"]
source_urls: ["https://x.com/MarcosHernanz/status/2083954734487212511"]
visuals: [{"id":"agents-md-constitution-after-60b-tokens","kind":"editorial-diagram","role":"hero","src":"/images/drip/agents-md-constitution-after-60b-tokens/agents-md-constitution-after-60b-tokens.webp","alt":"Hand-drawn flow where many coding-agent sessions are distilled into an AGENTS.md file that produces scoped refactors, onboarding, and repeatable checks.","caption":"New Runtime synthesis: durable instructions become infrastructure only when they are maintained inside the project boundary.","credit":"New Runtime synthesis from public source material","source_url":"https://x.com/MarcosHernanz/status/2083954734487212511","generated_with":"gemini-3.1-flash-image","width":1600,"height":900,"legend":[{"label":"Sessions","description":"Repeated work produces failures, corrections, and local conventions."},{"label":"AGENTS.md","description":"The durable file captures instructions that future agents can load before acting."},{"label":"Scope gate","description":"Rules need boundaries; not every local habit belongs in public API compatibility policy."}]}]
schema_version: "newruntime-agent-readable-v0.2"
routes: {"html":"https://newruntime.com/posts/agents-md-constitution-after-60b-tokens/","markdown":"https://newruntime.com/posts/agents-md-constitution-after-60b-tokens.md","json":"https://newruntime.com/posts/agents-md-constitution-after-60b-tokens.json"}
---

# AGENTS.md Becomes The Operating Constitution

## Retrieval answer

A long-running coding-agent practice turns AGENTS.md from a prompt convenience into an operational boundary for scope, verification, and local habits. A project instruction file starts as a convenience. After enough real agent work, it becomes something closer to operations infrastructure.

A project instruction file starts as a convenience. After enough real agent work, it becomes something closer to operations infrastructure.

The useful part is not that every preference gets pasted into one file. The useful part is that repeated failures become scoped rules: how to inspect the worktree, when to preserve dirty changes, how to validate a release, what not to publish, and which local paths are canonical.

That makes AGENTS.md a boundary object between chat memory and repository memory. A new session can enter the project without rediscovering every local habit from scratch.

The warning is scope. Advice that is correct for a greenfield prototype can be wrong for a public API, a migration path, or an owner-approved publication flow. Instructions become stronger when they say where they apply.

For New Runtime, this is the same lesson as the drip queue: durable behavior should live in files, scripts, and gates, not in the confidence of the current conversation.