Configuration Persistence
Persist stable nonsecret configuration and validate it when loading.
Context management
Reference File Injection
Load a named reference at the step that needs it, match an explicit key and cite the record; keep missing-data work pending.
Domain Knowledge Embedding
Embed compact domain facts with scope and version next to their use.
Handoff Context Protocol
Write a self-contained brief with task, constraints and artifact pointers.
State File as Sole Continuity
Persist a versioned progress ledger so a new session can resume work.
Mandatory Self-Learning After Failure
Record a verified failure lesson with applicability and disconfirming conditions.
Progressive Disclosure Architecture
Keep the entrypoint small and load branch-specific material only when needed.
Typed Memory Taxonomy
Separate persistent facts, preferences and resource pointers with freshness rules.
Context Compaction Survival
Save task identity, constraints and verified progress before compressing history.
Verbatim Global-Constraints Block
Transfer binding global values without paraphrasing their meaning.
Derivation-Order Staleness Check
Track dependency fingerprints so regenerated upstream inputs invalidate derived artifacts.
Controlled Vocabulary with Banned Synonyms
Define canonical terms and explicitly disambiguate near-synonyms.
Use delta tokens for recurring synchronization
Carry a server-issued change token between recurring reads.
Explicit continuation contract
Preserve service cursors for paginated APIs and complete-unit boundaries for generated documents; distinguish partial results from completion.
Identify the actor before inferring intent
Separate human requests from parent-agent dispatches, injected text and tool results.
Resource freshness versus reading relevance
A fresh resource validator does not make a previously transformed answer relevant to a different question.
Retain rejected experiment evidence
Preserve attempted ideas and their rejection evidence even when the implementation is reverted.
Reference closure in the received artifact
Verify referenced material in the receiver installed layout rather than only the author repository.
One active routing authority
Avoid stacking a full meta-router on top of a host that already selects the same skills natively.
Protected content through an editable projection
Keep protected content in an authoritative store while the editing view contains explicit opaque references.
Preserve the complete protocol envelope
Retain structured response state for continuation and derive human-readable text as a separate view.
Intent-matched, fresh catalog recommendations
Recommend a concrete resource only when the user wants learning material and a current catalog supports it.
Check instruction scope before resolving conflicts
Compare the scope and load conditions of two instructions before treating different wording as a conflict.
Assemble cached prefixes by stability
For a host with a verified prefix-cache contract, place stable inputs before volatile inputs and check the rendered overlapping prefix when reuse regresses.
Lock invariants, vary composition
Keep shared identity fixed while varying individual artifact purpose and composition.
Match reference granularity to inspection needs
Break dense references into units that preserve the details needed downstream.
Semantic token handoff contract
Express design tokens as semantic names, exact values and functional roles.
Durable behavioral agent contract
Describe behavior and named interfaces instead of volatile file locations in delayed task handoffs.
Evidence-gated learning memory
Store demonstrated knowledge separately from material merely covered.
Co-locate concept rules and caveats
Keep one concept definition, decision rules and exceptions together after selecting its disclosure tier.
Concept-scoped rejection memory
Recall substantive rejected concepts without poisoning that memory with already implemented requests.
Bind Behavioral Specs to Enforcement and Tests
Give a mined behavior a stable identity tied to its actual enforcement point and retain explicit test and uncertainty references.
One Canonical Owner per Documentation Fact
Assign each durable fact to one document role and reference it from other views.
Golden-File Convention Pointers
Anchor project conventions to current concrete exemplar files, with explicit differences and anti-patterns.
Empty-vs-Incomplete Recall
Report incomplete retrieval separately from a complete search with no matches.
Gap-Driven Iterative Retrieval
Refine retrieved context using explicit missing-information notes instead of choosing a fixed file set upfront.
Recall Freshness and Supersession
Check current authority and explicit supersession before reusing a saved decision.
Point-in-Time Context Admission
Admit only information available at the decision time when replaying or evaluating a historical task.
Raw Evidence and Synthesis Separation
Store original statements separately from interpretations, candidate formulations and unresolved contradictions.
Scope-Bound Evidence Memory
Bind memory recall to the current project, recipient and permitted scopes.
Version-Grounded Documentation Retrieval
Resolve the exact library and requested version before using retrieved API guidance.
Accepted-obligation amendment ledger
Carry accepted requirements into later revisions while preserving the amendment history.
Capability-tiered instruction digest
Give hosts that can read instruction files but cannot run the full skill suite a small, versioned behavioral core.
Budget context by when it loads
Measure always-loaded metadata separately from the full content eagerly loaded for one invocation.
Verify a save against the selected target
Verify persisted context in the intended account, source and storage target before reporting a successful save.