teknokeras

The invariants feature is the most interesting part to me. Are invariants like "patient name must match the source document" enforced deterministically outside the model (a separate checker that gates actions), or does the agent itself evaluate them as part of its loop? Asking because if the same model that decides actions also verifies invariants, a misread screenshot could fail both at once — the check inherits the perception errors it's meant to catch. Curious how you split trusted checks from model judgment.

Congrats on the launch. Question about the data side: conversations tend to contain a lot of PII (names, emails, account details users paste in). When you cluster and surface example messages in the dashboard, is there any redaction step before storage/display, or is that left to the customer to filter before sending through the SDK? Curious how much of SOC 2 scope covers the message content itself vs the infrastructure.