Creator control
Your evidence is not the product.
WITNESS is designed around a simple principal: the creator is the protected principal. Connected signals exist to help the creator understand the work and preserve accurate knowledge about it.
Authorization comes before observation.
Private creator data should enter WITNESS through authorized connections and principal-scoped access. Public evidence can be bounded and observed separately, but private artifacts remain tied to the creator's workspace and access boundary.
Evidence remains evidence.
Connected data is not silently converted into a public profile or training inventory. Source reports, WITNESS analysis, model output, and canonical evaluations remain distinct so the system can preserve provenance and access boundaries.
More data is not automatically better.
WITNESS is designed to use evidence relevant to the investigation. The purpose of a connector is not indiscriminate collection; it is to make the specific authorized signals needed for evidence-backed understanding available under explicit constraints.
Disconnects and provider limits matter.
Provider revocation support, token validity, reporting lag, account eligibility, and provider-specific access constraints are part of the evidence environment. WITNESS connector contracts preserve those limitations rather than pretending every integration behaves identically.