Layer 1 — agent framework laws · 235 documents
| ID | Document | Source |
|---|---|---|
| agent_invariants__372a4703542502e3 | Agent state must be serializable and checkpointed at every decision boundary to enable resumption after interruption and crash recovery. | — |
| agent_invariants__a031ae8b99bf39cf | Inter-agent communication must use structured message protocols with schema validation, streaming support, and event-driven callbacks. | — |
| agent_invariants__efcf813abb5e7517 | Agents require hierarchical memory: working memory for active context, short-term with relevance decay, and long-term with vector-based retrieval. | — |
| agent_invariants__635af96933769521 | Agent state must be serializable and checkpointed at every decision boundary to enable resumption after interruption and crash recovery. | — |
| agent_invariants__f64f117866e366af | Inter-agent communication must use structured message protocols with schema validation, streaming support, and event-driven callbacks. | — |
| agent_invariants__6c575fc9ba2182d2 | Agents must define tools with explicit input schemas, validate inputs before execution, handle timeouts, and degrade gracefully on failure. | — |
| agent_invariants__f03279bf706e9255 | Agents require hierarchical memory: working memory for active context, short-term with relevance decay, and long-term with vector-based retrieval. | — |
| agent_invariants__119d9775bc6a22ad | Complex tasks must be decomposed into atomic sub-tasks with explicit dependency graphs. Planning must include rollback strategies and replanning capability. | — |
| agent_invariants__29c0b82f279d6219 | Destructive operations require explicit human confirmation or pre-approved allow-lists with audit logging. | — |
| agent_invariants__641bc9e0612e24a8 | External interactions must implement retry with exponential backoff, circuit breakers for cascading failure prevention, and graceful degradation. | — |
| agent_invariants__e4c147e5ee73b2c7 | Agent state must be serializable and checkpointed at every decision boundary to enable resumption after interruption and crash recovery. | — |
| agent_invariants__b660fcb35b78a244 | Inter-agent communication must use structured message protocols with schema validation, streaming support, and event-driven callbacks. | — |
| agent_invariants__791f360dc5ff5254 | Agent access requires credential isolation, secure vaults, automatic key rotation, and least-privilege RBAC. | — |
| agent_invariants__f02d5056bf5a96e0 | Agents must monitor token usage, implement truncation or summarization when approaching limits, and maintain coherence across chunks. | — |
| agent_invariants__9d915bf1e7f044f8 | Agents must define tools with explicit input schemas, validate inputs before execution, handle timeouts, and degrade gracefully on failure. | — |
| agent_invariants__2de675eb6463bd37 | Agents require hierarchical memory: working memory for active context, short-term with relevance decay, and long-term with vector-based retrieval. | — |
| agent_invariants__48cb797deb7f68e0 | Complex tasks must be decomposed into atomic sub-tasks with explicit dependency graphs. Planning must include rollback strategies and replanning capability. | — |
| agent_invariants__d6a5453db69f7225 | Destructive operations require explicit human confirmation or pre-approved allow-lists with audit logging. | — |
| agent_invariants__1b80d3249ccf84e5 | External interactions must implement retry with exponential backoff, circuit breakers for cascading failure prevention, and graceful degradation. | — |
| agent_invariants__1055baaec7034c13 | Agent state must be serializable and checkpointed at every decision boundary to enable resumption after interruption and crash recovery. | — |
| agent_invariants__1379d9d36436488f | Inter-agent communication must use structured message protocols with schema validation, streaming support, and event-driven callbacks. | — |
| agent_invariants__d9547dcdad35ecf3 | Agent access requires credential isolation, secure vaults, automatic key rotation, and least-privilege RBAC. | — |
| agent_invariants__85718066d620725c | External API calls must respect rate limits through token bucket or sliding window algorithms with automatic backoff. | — |
| agent_invariants__1b395f3fd910971d | Agents must monitor token usage, implement truncation or summarization when approaching limits, and maintain coherence across chunks. | — |
| agent_invariants__15eda94310792834 | Agents must define tools with explicit input schemas, validate inputs before execution, handle timeouts, and degrade gracefully on failure. | — |
| agent_invariants__cdad02a3b4554d28 | Agents require hierarchical memory: working memory for active context, short-term with relevance decay, and long-term with vector-based retrieval. | — |
| agent_invariants__9e8f4b694da0239f | Agent state must be serializable and checkpointed at every decision boundary to enable resumption after interruption and crash recovery. | — |
| agent_invariants__982005d9cbfabd6a | Agent access requires credential isolation, secure vaults, automatic key rotation, and least-privilege RBAC. | — |
| agent_invariants__d400c69d649febfa | Agents require hierarchical memory: working memory for active context, short-term with relevance decay, and long-term with vector-based retrieval. | — |
| agent_invariants__6d43b238881907a1 | Agent state must be serializable and checkpointed at every decision boundary to enable resumption after interruption and crash recovery. | — |
| agent_invariants__a3ce89bb5fa1e880 | Agents require hierarchical memory: working memory for active context, short-term with relevance decay, and long-term with vector-based retrieval. | — |
| agent_invariants__018ee8af8d47fa88 | Complex tasks must be decomposed into atomic sub-tasks with explicit dependency graphs. Planning must include rollback strategies and replanning capability. | — |
| agent_invariants__cbce5174439e54d1 | Agents must define tools with explicit input schemas, validate inputs before execution, handle timeouts, and degrade gracefully on failure. | — |
| agent_invariants__acfc67fa54c83693 | Agents require hierarchical memory: working memory for active context, short-term with relevance decay, and long-term with vector-based retrieval. | — |
| agent_invariants__8be9b08e990ea55b | Complex tasks must be decomposed into atomic sub-tasks with explicit dependency graphs. Planning must include rollback strategies and replanning capability. | — |
| agent_invariants__9b28182a9ad26f4f | Destructive operations require explicit human confirmation or pre-approved allow-lists with audit logging. | — |
| agent_invariants__8ef1f6739de308a8 | External interactions must implement retry with exponential backoff, circuit breakers for cascading failure prevention, and graceful degradation. | — |
| agent_invariants__25ce5db2ddf786ba | Agent state must be serializable and checkpointed at every decision boundary to enable resumption after interruption and crash recovery. | — |
| agent_invariants__8cc9d928d8eea400 | Inter-agent communication must use structured message protocols with schema validation, streaming support, and event-driven callbacks. | — |
| agent_invariants__0fde9ab2a4300576 | Agents must define tools with explicit input schemas, validate inputs before execution, handle timeouts, and degrade gracefully on failure. | — |
| agent_invariants__301e3ad574e023ab | Agents require hierarchical memory: working memory for active context, short-term with relevance decay, and long-term with vector-based retrieval. | — |
| agent_invariants__afc1fc43e2410096 | Complex tasks must be decomposed into atomic sub-tasks with explicit dependency graphs. Planning must include rollback strategies and replanning capability. | — |
| agent_invariants__2a02a2ad83a44e37 | Destructive operations require explicit human confirmation or pre-approved allow-lists with audit logging. | — |
| agent_invariants__1236b7fa315967c1 | External interactions must implement retry with exponential backoff, circuit breakers for cascading failure prevention, and graceful degradation. | — |
| agent_invariants__98b59442dbc16cb7 | Agent state must be serializable and checkpointed at every decision boundary to enable resumption after interruption and crash recovery. | — |
| agent_invariants__589d808211915a1c | Inter-agent communication must use structured message protocols with schema validation, streaming support, and event-driven callbacks. | — |
| agent_invariants__9f14a2f724518223 | Agent access requires credential isolation, secure vaults, automatic key rotation, and least-privilege RBAC. | — |
| agent_invariants__8fa2bbdff9252282 | Agents must monitor token usage, implement truncation or summarization when approaching limits, and maintain coherence across chunks. | — |
| agent_invariants__a68b13d768c80e94 | Agents must define tools with explicit input schemas, validate inputs before execution, handle timeouts, and degrade gracefully on failure. | — |
| agent_invariants__cf1445e31676a9d4 | Agents require hierarchical memory: working memory for active context, short-term with relevance decay, and long-term with vector-based retrieval. | — |