Add an encrypted workflow test case and assertion contract

Test inputs and assertions are encrypted at rest. Campaign results persist hashes and bounded summaries rather than raw simulated outputs.

curl

curl -X POST \
  -H "Authorization: Bearer $FINANCEGPT_API_KEY" \
  -H "Accept: application/json"
  "https://financegptlabs.com/api/v2/workflow-studio/test-suites/{uid}/cases"

javascript

const response = await fetch("https:\/\/financegptlabs.com\/api\/v2\/workflow-studio\/test-suites\/{uid}\/cases", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${FINANCEGPT_API_KEY}`,
    Accept: 'application/json',
  },
});
const data = await response.json();

python

import json
import os
import requests

response = requests.request(
    'POST',
    'https://financegptlabs.com/api/v2/workflow-studio/test-suites/{uid}/cases',
    headers={
        'Authorization': 'Bearer ' + os.environ['FINANCEGPT_API_KEY'],
        'Accept': 'application/json',
    },
)
response.raise_for_status()
print(response.json())

php

<?php
$ch = curl_init('https://financegptlabs.com/api/v2/workflow-studio/test-suites/{uid}/cases');
curl_setopt_array($ch, [
    CURLOPT_CUSTOMREQUEST => 'POST',
    CURLOPT_RETURNTRANSFER => true,
    CURLOPT_HTTPHEADER => [
        'Authorization: Bearer '.getenv('FINANCEGPT_API_KEY'),
        'Accept: application/json',
    ],
]);
$response = curl_exec($ch);
curl_close($ch);
echo $response;

A developer credential proves application identity and permits only its scopes. It does not grant model promotion, policy override, QLM rebinding, or Financial Actions execution authority unless those separate controls are satisfied.

workflow:manage