Clarifying Document Context Usage in Clay Generations
Hey y'all! I'm looking for documentation on how the Document Context is working exactly. I feel like sometimes generated text properly abides by strict rules from the documentation, other times it completely disregards. How does Clay use these documents as contexts, exactly? We've been updating our system prompts to include the main rules from the context because it keeps forgetting or is inconsistent, but this makes the prompts incredibly long and both scalability and maintenance are hurting. Any ideas?
.png)