Submit Functional Test Assertions
submit_functional_test_assertionsAttach machine-verifiable evidence assertions to an existing functional test so CI can verify it. Bind test existence and passing claims to a repository for independent verification.
Instructions
Attach machine-verifiable evidence assertions to one already-existing functional test so CI can verify it. Mutating.
This submits EVIDENCE for a test that already exists (identified by functional_test_id) — it does not create or register the test. It is the functional-conformance analog of submit_assertions (which covers security controls): it binds assertions such as "the test exists" and "the test passes" to the functional test, and an independent CI run against the named repo is what turns an operator's "verified" claim into verified state.
To bulk-register test DEFINITIONS from your codebase instead, use import_functional_tests; to hand-author a single test use add_functional_test. Call this after the test is implemented (e.g. following get_scan_prompt (kind="functional")), then read the resulting state via get_functional_coverage or get_functional_test_sufficiency.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| model_id | Yes | ID of the threat model. | |
| server_version | Yes | ||
| assertions_json | Yes | JSON array of assertion objects, each {"type": "test_attested" | "test_exists" | ..., "params": {...}, "description": "...", "repo": "<owner>/<repo>"}. Every assertion must carry an explicit repo, or the "no_repo" sentinel when the check is not tied to a repository. These assertions count toward functional conformance; a ``covers`` declaration is refused here, because a binding to a control clause is declared on ``submit_assertions``. | |
| functional_test_id | Yes | The already-existing functional test the assertions prove. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||