ozDNA · AI Verifiability Infrastructure

Claims you can check. It's in the DNA.

Cite. Sign. Verify. AI output earns trust when the evidence travels with it.

Check a record Mandates
Verification trace · recomputed in your browser on each pass Demo data
01 · FingerprintFingerprint—
02 · SignatureSignature—
03 · TimestampTimestamp—
04 · VerifyVerified—
STATUS · pre-launchLOG · hash-chained, append-onlyBY · Kolaxa

[01] Principle

Evidence first. Claim second.

Three moves, one principle. Every output shows its source, carries a verifiable record, and can be checked independently.

A / CITE

Cite.

Every statement links to the source it rests on. A statement without a source is flagged, not hidden.

B / SIGN

Sign.

The content is fingerprinted and given a trusted timestamp; cryptographic signing at creation is planned.

C / VERIFY

Verify.

Anyone can recompute the record and compare. No trust required. Checking is enough.

[02] Mandates

Three lines. One verification logic.

Early access

ComplyDNA

Citation-first compliance intelligence. Every answer links to the regulatory text behind it.

Request access

Your request goes to the team as a short email. Replies depend on fit and capacity. Access is not guaranteed.

STATUS
Early access
MARKET
Türkiye · regtech
CLOCK
Onboarded in request order
Waitlist

OriginDNA

Provenance for AI-generated content. Fingerprint, timestamp, verification live today; signature planned.

Join the waitlist

Your email is used only for OriginDNA access announcements. When access opens, invitations go out in list order. It is not shared for other purposes.

STATUS
Waitlist
MARKET
Global
CLOCK
No launch date announced
Pilot

Contract DNA

A decision-ready map of what changed between two contract versions. Clause-level diff, business impact, evidence, audit record. Not a legal opinion.

Request pilot access

Pilot seats are limited and onboarded concierge-style on real or anonymised documents. The product page is in English for now.

STATUS
Pilot
MARKET
Global · contracts
CLOCK
Onboarding pilot customers now

[03] Verify

Check a record yourself.

The left panel queries the live OriginDNA registry (api.ozdna.com). The text trace on the right is an illustration of the steps.

Live registry
Deep verify →

Your image never leaves your browser; only its SHA-256 hash is sent. This panel looks for an exact file match. For re-encoded or screenshotted copies, use deep verify.

  1. 01
    Fingerprint (SHA-256)—
  2. 02
    Signature (illustrative)—
  3. 03
    Timestamp (illustrative)—
  4. 04
    Record—
  5. 05
    Verification—

The hash is a real SHA-256. Signature and timestamp are illustrative and do not come from a live system.

[04] Method

Sources. Engine. Output.

The log is hash-chained and append-only. Anyone can recompute the chain and check each record.

Sources

Regulatory texts
Organisation documents
AI-generated content

ozDNA engine

CITElink to source
SIGNfingerprint, timestamp; signature planned
LOGhash-chained append-only record

Output

Cited answer
Provenance record
Independent verification
01FingerprintSHA-256 digest of the content
02SignatureCryptographic signature (planned)
03TimestampTrusted timestamp
04RecordAppended to the log
05VerificationRecompute and compare

[05] Why now

The calendar, with its scope.

The EU AI Act (Regulation 2024/1689) applies in stages. Dates may shift because of a proposed postponement package.

Article 50. Transparency obligations.

Obligations such as marking AI-generated content and disclosing AI interaction.

Annex III. High-risk systems.

The date for Annex III high-risk systems under the proposed postponement. It covers that category only, not every system.

Systems embedded in products.

The date for high-risk systems embedded in regulated products.

Dates must be re-checked against official sources (EUR-Lex, European Commission) before publishing. This is not legal advice.

[06] Research integrity

A score is not evidence.

Kolaxa's academic platform, tezmakale, is moving toward treating AI use in academic writing with evidence rather than a score. ozDNA's provenance layer is the planned foundation for that direction.

This is a planned direction. It does not mean tezmakale uses ozDNA today.

[07] Proof

What we do. What we don't claim.

Principle

  • Evidence comes before the claim.
  • Verification must work without trusting us.
  • What cannot be measured is not written.

Methodology

  • Content is digested with SHA-256.
  • The digest is timestamped and recorded; signing is planned.
  • The record goes into a hash-chained, append-only log.
  • Accuracy measurements will be published with their method once they exist.

What we don't claim

  • We show that content is unchanged and where it came from, not that it is true.
  • There is no published accuracy rate, customer, award, or certification yet.
  • We give no legal advice and no compliance guarantee.

[08] FAQ

Questions

What is ozDNA?

Infrastructure for the verifiability of AI output: ComplyDNA and OriginDNA.

How can I check a record myself?

Records live in a hash-chained, append-only log. You recompute the hash chain and check the signature with the public key.

Is the verifier live?

Yes, the registry lookup is live: the image's SHA-256 hash is computed in your browser and looked up in the api.ozdna.com registry. The text trace beside it is illustrative.

Is this legal advice?

No. Regulatory information is general information only.

[09] Behind ozDNA

A Kolaxa product.

Kolaxa is a technology company built as a house of brands. Shared thesis: verification-first infrastructure for complex decisions. Data, verification, provenance, evidence, decision.

BRANDS
ozDNA · MetalTakip · Signal
THESIS
Verification-first

Kolaxa Yazılım Teknoloji Sanayi ve Ticaret Limited Şirketi · Teknokent, Balıkesir Üniversitesi Çağış Yerleşkesi, Altıeylül/Balıkesir