Layer 1 — agent framework laws · 235 documents
| ID | Document | Source |
|---|---|---|
| agent_invariants__2292de23cf71733d | External interactions must implement retry with exponential backoff, circuit breakers for cascading failure prevention, and graceful degradation. | — |
| agent_invariants__82e736753a44dc89 | Agent state must be serializable and checkpointed at every decision boundary to enable resumption after interruption and crash recovery. | — |
| agent_invariants__d390ccab71cfbe7b | Inter-agent communication must use structured message protocols with schema validation, streaming support, and event-driven callbacks. | — |
| agent_invariants__9500760f96e2b06d | Agent access requires credential isolation, secure vaults, automatic key rotation, and least-privilege RBAC. | — |
| agent_invariants__2d6c7ed815ea198b | Agents must define tools with explicit input schemas, validate inputs before execution, handle timeouts, and degrade gracefully on failure. | — |
| agent_invariants__3bba00e99e2735ff | Agents require hierarchical memory: working memory for active context, short-term with relevance decay, and long-term with vector-based retrieval. | — |
| agent_invariants__c67a46c8c952bfa4 | Complex tasks must be decomposed into atomic sub-tasks with explicit dependency graphs. Planning must include rollback strategies and replanning capability. | — |
| agent_invariants__496da84b3a82fcf3 | Destructive operations require explicit human confirmation or pre-approved allow-lists with audit logging. | — |
| agent_invariants__851871b1bacd1bdb | Agent state must be serializable and checkpointed at every decision boundary to enable resumption after interruption and crash recovery. | — |
| agent_invariants__327e3162889ff070 | Inter-agent communication must use structured message protocols with schema validation, streaming support, and event-driven callbacks. | — |
| agent_invariants__37f8e6b3c587270c | Agent access requires credential isolation, secure vaults, automatic key rotation, and least-privilege RBAC. | — |
| agent_invariants__2528f2c99947e6f0 | Agents require hierarchical memory: working memory for active context, short-term with relevance decay, and long-term with vector-based retrieval. | — |
| agent_invariants__1016233f6f05408a | Agents must define tools with explicit input schemas, validate inputs before execution, handle timeouts, and degrade gracefully on failure. | — |
| agent_invariants__e76e9dc63b9e4c4a | Agents require hierarchical memory: working memory for active context, short-term with relevance decay, and long-term with vector-based retrieval. | — |
| agent_invariants__0a58bcaf2b4a5986 | Complex tasks must be decomposed into atomic sub-tasks with explicit dependency graphs. Planning must include rollback strategies and replanning capability. | — |
| agent_invariants__3553850ebc43d7f8 | Destructive operations require explicit human confirmation or pre-approved allow-lists with audit logging. | — |
| agent_invariants__cfc2e45f589038e7 | Agent state must be serializable and checkpointed at every decision boundary to enable resumption after interruption and crash recovery. | — |
| agent_invariants__8b79c27f72120052 | External API calls must respect rate limits through token bucket or sliding window algorithms with automatic backoff. | — |
| agent_invariants__64136f13f563ca1a | Agents must define tools with explicit input schemas, validate inputs before execution, handle timeouts, and degrade gracefully on failure. | — |
| agent_invariants__7cea757435604db9 | Agents require hierarchical memory: working memory for active context, short-term with relevance decay, and long-term with vector-based retrieval. | — |
| agent_invariants__d1e5be090aef2296 | Complex tasks must be decomposed into atomic sub-tasks with explicit dependency graphs. Planning must include rollback strategies and replanning capability. | — |
| agent_invariants__ad8755df5eae6fb8 | Agent state must be serializable and checkpointed at every decision boundary to enable resumption after interruption and crash recovery. | — |
| agent_invariants__325e8d5fcda4edeb | Inter-agent communication must use structured message protocols with schema validation, streaming support, and event-driven callbacks. | — |
| agent_invariants__eb3e6a9fb0a00813 | Agent access requires credential isolation, secure vaults, automatic key rotation, and least-privilege RBAC. | — |
| agent_invariants__88c0fb7844b8af99 | Agents must define tools with explicit input schemas, validate inputs before execution, handle timeouts, and degrade gracefully on failure. | — |
| agent_invariants__42799a261505df56 | Agents require hierarchical memory: working memory for active context, short-term with relevance decay, and long-term with vector-based retrieval. | — |
| agent_invariants__07d037ef291dc275 | Complex tasks must be decomposed into atomic sub-tasks with explicit dependency graphs. Planning must include rollback strategies and replanning capability. | — |
| agent_invariants__6b16d3fd2f21064d | Destructive operations require explicit human confirmation or pre-approved allow-lists with audit logging. | — |
| agent_invariants__bc9982cfc0f29cad | Agent state must be serializable and checkpointed at every decision boundary to enable resumption after interruption and crash recovery. | — |
| agent_invariants__3624263616eb9fa2 | Agents must monitor token usage, implement truncation or summarization when approaching limits, and maintain coherence across chunks. | — |
| agent_invariants__55b267a6893b7bfc | Agents require hierarchical memory: working memory for active context, short-term with relevance decay, and long-term with vector-based retrieval. | — |
| agent_invariants__45851c30345eada6 | Destructive operations require explicit human confirmation or pre-approved allow-lists with audit logging. | — |
| agent_invariants__ad88e71b5efe7c4e | Agent state must be serializable and checkpointed at every decision boundary to enable resumption after interruption and crash recovery. | — |
| agent_invariants__e187f3f86be3ee7a | Inter-agent communication must use structured message protocols with schema validation, streaming support, and event-driven callbacks. | — |
| agent_invariants__d005db920e342992 | Inter-agent communication must use structured message protocols with schema validation, streaming support, and event-driven callbacks. | — |