Promote immutable probe evidence for a configured connection.
Persists a server-promoted immutable probe report. `promotedByPrincipalRef` is never a request field: `operator_validation` is attributed to the calling principal and capped at `integration_verified` by store policy, while `smoke_evidence` and `release_gate` are attributed to the system harness-authority promoter and require the deployment-issued promoter credential in `X-Rensei-Harness-Promoter`. Only a release gate sourcing an exact durable system-smoke report can mint `production_eligible`. A connection outside the authenticated organization is a 404.
AuthorizationBearer <rsk_live_*>Rensei API key presented as Authorization: Bearer rsk_live_. Required API-key scopes are recorded per operation in x-rensei-required-scopes.
connectionId*string1 <= length <= 256X-Rensei-Harness-Promoter?stringDeployment-issued harness-authority promoter secret. Required for smoke_evidence and release_gate promotions; ignored for operator_validation.
application/json- body
reportId*string^[A-Za-z0-9][A-Za-z0-9._@+-]*(?:[:/][A-Za-z0-9._@+-]+)*$1 <= length <= 256connectionRevision*string^[A-Za-z0-9][A-Za-z0-9._@+-]*(?:[:/][A-Za-z0-9._@+-]+)*$1 <= length <= 256observerPlacement*observedAt*string^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))T(?:(?:[01]\d|2[0-3]):[0-5]\d:[0-5]\d(?:\.\d+)?(?:Z|([+-](?:[01]\d|2[0-3]):[0-5]\d)))$date-timettlMs?integer0 < value <= 90000promotionTier*string"declared""implemented""unit_verified""integration_verified""smoked""production_eligible"provenance*evidence*The durable promoted report.
application/json- response
created*booleancurrent*booleanreportId*string^[A-Za-z0-9][A-Za-z0-9._@+-]*(?:[:/][A-Za-z0-9._@+-]+)*$1 <= length <= 256reportDigest*string^[0-9a-f]{64}$promotionTier*string"declared""implemented""unit_verified""integration_verified""smoked""production_eligible"observedAt*string^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))T(?:(?:[01]\d|2[0-3]):[0-5]\d:[0-5]\d(?:\.\d+)?(?:Z|([+-](?:[01]\d|2[0-3]):[0-5]\d)))$date-timevalidUntil*string^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))T(?:(?:[01]\d|2[0-3]):[0-5]\d:[0-5]\d(?:\.\d+)?(?:Z|([+-](?:[01]\d|2[0-3]):[0-5]\d)))$date-timecurl -X POST 'https://app.rensei.ai/api/cli/harness/connections/string/probes' \ -H 'Content-Type: application/json' \ -d '{ "reportId": "string", "connectionRevision": "string", "observerPlacement": { "id": "string", "kind": "host", "resolution": "exact" }, "observedAt": "2019-08-24T14:15:22Z", "promotionTier": "declared", "provenance": { "source": "operator_validation", "sourceEvidenceRef": "string", "sourceReportDigest": "string" }, "evidence": { "observedHarness": { "id": "string", "version": "string" }, "harnessHealth": "ready", "endpointHealth": "ready", "authHealth": "ready", "inventoryCompleteness": "complete", "models": [ { "model": { "id": "string", "author": "string" }, "remoteModelId": "string", "availability": "available", "evidenceTier": "declared" } ], "capabilities": [ { "name": "string", "state": "supported", "evidenceTier": "declared", "adapterVersion": "string" } ], "sanitizedDiagnostics": [ "harness_unavailable" ] }}'{ "created": true, "current": true, "reportId": "string", "reportDigest": "string", "promotionTier": "declared", "observedAt": "2019-08-24T14:15:22Z", "validUntil": "2019-08-24T14:15:22Z"}Grant a configured HarnessConnection to one project.
Binds a live connection to a live project in the authenticated organization. The project is resolved by id or slug WITHIN that organization, so a cross-tenant project reference 404s. Re-submitting an identical grant id and tuple is idempotent; re-using the id for a different tuple is a 409. Requires org-admin (human) or an unfenced credential holding `harness:write`/`*` (machine).
Author an org-scope harness compatibility declaration.
Declares the protocols, session modes, and capability ceiling for one exact harness version, scoped to the authenticated organization. The compatibility digest is always recomputed from the submitted body, so a caller can never claim a ceiling its declaration does not contain. `scope: "system"` is refused: a system-scope entry is the cascade root for every organization without an override and is not a tenant write.