Evidence for governed software decisions

Software-change decisions need durable evidence

Automated and human-associated repository events can create provenance gaps when evaluation inputs, policy results, and identifiers are not retained together. Decision Receipt creates a reviewable record; enforcement remains the responsibility of the integrating system.

Try a synthetic, non-production evaluation

The public demo endpoint accepts fictional sample input and returns a non-production demo receipt. It does not authorize, merge, deploy, or attest that the described action occurred.

curl -X POST https://decrec.summitcognitive.ai/v1/demo/evaluate \
  -H "Content-Type: application/json" \
  -d '{
    "claim_id": "my-first-receipt",
    "entity": "my-org/my-repo",
    "claim": "AI agent requests merge authority for PR #42",
    "sources": [
      {"id": "ci", "type": "ci", "uri": "https://ci/run/1",
       "confidence": 0.9, "content": "All tests pass"},
      {"id": "review", "type": "code_review", "uri": "https://pr/1",
       "confidence": 0.85, "content": "Approved by maintainer"}
    ]
  }'

The response is explicitly marked environment: nonproduction and demo: true. Production evaluation requires authentication. See full API docs →

Get your API key

Enter your email to receive an API key instantly. No credit card required.