PUBLICATION CONTRACT

Content Principles

How pages are researched, how teaching examples differ from personal experience, where AI assistance stops and how changing information is versioned.

Last checked: 27 July 2026Binding publication policy
ROLES

Four types of content on the site

Teaching guide

Teaches through explanation, example, application, quiz and sources; it does not claim personal experience.

Example or scenario

Demonstrates a method and is not presented as a real personal event.

Personal record

Information about Doruk that has been verified and judged suitable to publish.

Changing information

Dates, fees, programmes, quotas and rules that require sources and a check date.

EVIDENCE LADDER

How is source strength assessed?

How is source strength assessed? table
LevelSourceUse
1MEB, ÖSYM, YÖK, YÖK Atlas, MYK, KVKK and other official primary sourcesMain basis for changing rules, programmes and conditions
2Current documents published directly by a university, institution or programmeCurriculum, application, practice and accreditation detail
3International standards and frameworksAccessibility, child safety, AI and occupational change
4High-quality secondary sourceContext and comparison; it does not replace the primary source
5Personal observation or teaching exampleClearly labelled; it does not become an official rule or general fact
PERSONAL CLAIM

The publication gate for information about Doruk

An award, certificate, project, sports result, school event, institutional relationship or future education record is published only with verifiable evidence and permission. A gap is never filled with a plausible claim merely to make the profile look stronger.

An Academy guide is not a personal project. An AI-generated scenario is not a personal memory. The presence of a photograph does not create permission to disclose the exact event date, location or other participants.

ARTIFICIAL INTELLIGENCE

Where can AI assist, and where can it not decide?

  • It may assist with outlines, title alternatives, language checks and teaching examples.
  • It does not make an unverified source reliable.
  • It cannot invent memories, projects, awards or opinions on Doruk’s behalf.
  • It cannot replace primary sources in rules, health, law or safety decisions.
  • Generated code, questions and explanations require testing before publication.
  • English content requires semantic parity and natural-language review, not mechanical translation alone.
FRESHNESS

Version records for changing information

Curricula, examinations, preferences, scholarships, competitions, fees, quotas, regulations and programme data carry an academic year, source date and last-check date. When a new announcement appears, the previous information is not silently erased; it may move to an annual archive.

A “current” label means checked on a stated date, not permanently true. A user taking action should reopen the official source.

PUBLICATION GATES

When is a page considered complete?

  • The title and content answer the same question.
  • Turkish and English counterparts are updated together.
  • Navigation and footer are consistent on every page.
  • A topic-specific example, application or decision tool is present.
  • Changing information has a source and date.
  • Personal data and child-safety risks are reviewed.
  • Broken links, keyboard use, mobile layout and overflow are tested.
  • Unverified areas are marked unknown or not yet published.
RETURN AND REVIEW

Correction and withdrawal method

When an error is found, the site does not merely replace one sentence and forget the earlier state. The issue is classified as a personal claim, changing date, source interpretation, translation, technical function or accessibility problem. If the same pattern may exist elsewhere, the entire site is searched.

Content carrying a serious personal-data or safety risk is removed first and corrected afterwards. Lower-risk factual errors receive an updated source and check date. A correction is applied to the English counterpart and all related pages at the same time.

Correction history is kept not to suggest that the site never makes mistakes, but to show how errors are found and closed. A page can pass automated tests while remaining editorially wrong, so human review is a separate gate.

  • Classify the error type
  • Search the whole site for the pattern
  • Remove first when risk is high
  • Correct Turkish, English and all related pages together
PRACTICAL CHECK

Language and translation review

Turkish and English pages do not need identical word counts, but they must carry the same information scope, warnings, tables, quiz identities, sources and freshness dates. Türkiye-specific institutions and examinations are explained in context on English pages.

A stronger marketing phrase in one language cannot create a new unsupported claim in the other. Translation does not intensify personal tone, increase certainty or add conclusions absent from the official source.

  • Scope parity
  • Source and date parity
  • Explain Türkiye-specific terms
  • Do not increase certainty
  • Do not add personal claims