SECURITY / BOUNDARIES THAT CAN BE EXPLAINED
Specific controls. Clear limits.
Understand how the service handles sources, permissions and review records. These are product controls, not independent security certification.
Established product mechanisms
These describe controls in the current product foundation. Deployment configuration and service availability still matter.
01Source traceability
A reference belongs to a source version.
Source traceability
A reference belongs to a source version.
Document records carry version, node identity, source locator, and source hash. Location precision remains explicit; an unresolved location is not an exact citation.
A reference identifies the source. It does not establish that a conclusion is correct.
02Organization-scoped access
Document and review access checks include organization context.
Organization-scoped access
Document and review access checks include organization context.
Resource access is checked against the requesting organization. A document or review identifier alone is not authorization to access it.
Membership and authorization checks are product controls, not a guarantee against every access risk.
03Isolated document processing
Untrusted documents cross a restricted processing boundary.
Isolated document processing
Untrusted documents cross a restricted processing boundary.
The supported Linux processing path applies per-job filesystem and process restrictions before parsing. If the required sandbox cannot be established, processing fails closed.
These restrictions depend on the supported processing environment. Uploaded content remains untrusted data.
04Human and system separation
A reviewer’s disposition is a separate record.
Human and system separation
A reviewer’s disposition is a separate record.
Machine outcome, certainty, run state, and human disposition are distinct. Recording a human decision does not rewrite the machine artifact.
A completed run is not human approval, and missing evidence is not a pass.