V

Veritas Demo

Live

Compare the same prompt with and without Veritas safety constraints.

Before
Standard LLMNo constraints

No constraints

After
VeritasProtected
crypto_tx_prod_2025

Constraints active

Causal Decision Log

Causal Decision Log

Institutional Memory
runbookCrypto Transactions Production Runbook
94%
policySQL Query Safety Policy
91%
policyDatabase Access Control Matrix
86%
Why crypto_tx_prod_2025 is locked:
  • Runbook: crypto_tx_prod_2025 is the designated production transaction database
  • Policy: Hard lock prevents accidental queries to user analytics databases
  • Safety: Transaction data requires specialized access controls and audit trails
  • Compliance: Production crypto data regulated by financial audit requirements
Memory Hits
Episodic: 1
Crystallized: 2
Crypto Transactions Production Runbook
runbook
94%
SQL Query Safety Policy
policy
91%
Database Access Control Matrix
policy
86%
Active Tool Policy
tool_policy.yaml
# Veritas Safety Policy - Coinbase
tool:
  name: sql_query

safety:
  min_role: analyst

parameters:
  - name: database
    allowed_values:
      - crypto_tx_prod_2025
      - users_2024
      - analytics_prod
  - name: query
    disallowed_patterns:
      - "(?i)\bDROP\b"
      - "(?i)\bDELETE\b"
      - "(?i)\bTRUNCATE\b"
      - "(?i)\bALTER\b"
      - "(?i)\bUPDATE\b"
      - "--"
      - ";"
  - name: max_rows
    default: 100
  - name: timeout_seconds
    default: 30
semantic_locks:
  database: crypto_tx_prod_2025
audit:
  log_all_queries: true
  trace_decision_path: true
  retention_days: 90
Decision Trace
Parameters Locked via GBNF

Semantic locks from institutional memory were applied to constrain parameter selection.

database:crypto_tx_prod_2025hard
max_rows:100soft
timeout_seconds:30soft
Parameters locked from context. Unconstrained LLM guessed customer_analytics_prod_2024.