Resources

Documents

Product, architecture, compliance and deployment documents. Turkish and English, as Word and PDF.

Sample output

What an evidence file actually looks like

The file below is not marketing copy. It is the evidence output the system produced for a single request: who asked, the rule set in force that day, the timeline, the script fingerprint, the risk rationale, the masking decision and the verified audit records.

The section worth reading is "Exceptions" near the end. In this sample the requester executed their own request, and the file records that as an exception rather than hiding it. Governance is not measured by the absence of violations but by whether they surface.

The sample data is fictional. Identifying fields in this copy were masked before publication, so the seal in this file no longer verifies. In real use the seal is what shows the record has not changed since it was generated.

In a real delivery this PDF does not travel alone. It goes inside a zip together with the machine readable form of the data, a manifest listing the digest of every file in the package, the RSA signature over that manifest, the public key and the verification script. The evidence format specification is available on request.

Document library

Document Content PDF Word
One pager A single page overview EN EN
Product overview Scope, approach and use cases EN EN
Technical specification Technical requirements and capability definitions EN EN
System architecture Components and topology EN EN
User guide Installation, configuration, daily use and audit. Twenty eight sections. EN EN
Compliance Personal data and audit requirements EN EN
Licensing and deployment Licence model and deployment requirements EN EN
FAQ Deployment, operations and compliance questions EN EN