We already paid for a national platform and almost nobody uses it.
Correct, and it is the right objection to open with. Дигитална раница cost around 103 million BGN (about €53 million) under „Образование за утрешния ден“, and the criticism that no usage report was published before МОН committed a further €126,018,597.05 is fair. The answer is not more features. Instrument adoption first — teacher weekly active use, parent monthly active use split by settlement type, resource use per curriculum unit — publish it, and tie every new capability to a measured gap. We agree the adoption metrics before we build, and we show you the ones that look bad.
If AI grades our students, who is liable?
Anything that evaluates learning outcomes or steers the learning process is Annex III point 3(b); proctoring is 3(d) and admission is 3(a). The Digital Omnibus, in force since 27 July 2026, moved most Annex III obligations to 2 December 2027 — that buys time and changes nothing about the design. The exemption route is Art. 6(3), not human review, and it has a hard limit: a system that profiles natural persons is high-risk whatever the oversight around it. Our dropout scoring profiles named students, so we treat it as Annex III 3(b) and 3(a)-adjacent from day one — Art. 9 risk management, Art. 10 data governance, Art. 14 oversight record, Art. 26 deployer obligations, and the Art. 27 fundamental rights impact assessment that applies to you as a public body. Document generation and search do fall outside Annex III under Art. 6(3), and we say which side of the line each component sits on in writing. The architecture still matters — the model drafts, explains, flags and pre-fills; a named human confirms, and the override is logged with who, when and why — but it changes the obligations, not the classification.
Student data cannot leave the country.
Then it will not. BgGPT ships openly in Gemma-2 (2.6B, 9B, 27B) and Gemma-3 (4B, 12B, 27B) with GGUF and GPTQ-W4A16 builds, so Bulgarian-competent inference runs on hardware you control under the Gemma terms. We split the architecture on that line: the model touching identified student data stays on-premise, and offline content generation may use an external API precisely because no personal data reaches it. You get a DPIA, a ROPA entry, a sub-processor register and a data-flow diagram before code — your DPO is a mandatory appointment under GDPR Art. 37(1)(a) and will ask for all four.
Our teachers are near retirement and already overloaded. They will not adopt it.
31.4% of Bulgarian teachers are 55 or older against an EU average of 25.1%, so that is a design constraint rather than a risk to be managed. It means no new login, no new tab and no new mental model: an LTI 1.3 launch from the e-diary they already open every morning, output in the exact document formats the РУО expects, and defaults that are correct for the most common case. We budget training the way МОН did — roughly 13% of the current programme — and we report weekly active use, not seats sold.
You will break our НЕИСПУО reporting, and we cannot miss 20 September.
Which is why nothing we build sits in the critical path on its first cycle. The validation and reconciliation layer runs in shadow for a full year: it tells you what it would have flagged, you compare that against what actually got rejected, and only then does it become the primary path. Capacity is planned around the real peaks — the 15–25 September window, the 1st-to-4th absence campaign, НВО and ДЗИ result days, which run 10–30× median load — not around an annual average. A 99.9% annual uptime figure is meaningless if the outage lands on the 4th.
You are a very small team, and our system fails at 22:00 on the 3rd.
Fair, and the answer is contractual rather than reassuring. Named on-call cover with stated response times across the 1st to the 4th of every month and 15–25 September; a documented runbook your own administrators can execute without us; source code in escrow and, for state work, in the state repository from the first sprint; and a named person on your side trained to re-run the pipeline. If what you need is a 24/7 NOC, we are the wrong supplier and will say so in the ЕЕДОП rather than after award.
We have no budget outside EU programmes, and procurement takes a year.
Then the work is shaped to Programme „Образование“ (ESF+) and NRRP eligibility rules from day one, with deliverables that map to the indicators the grant is measured on. We are used to the fact that the real deadline is a payment claim rather than a release date: documentation retained for the audit trail, costs traceable to eligible activities, and acceptance evidence produced in the form the managing authority asks for. If a capability cannot be made eligible, we say so before it is in the technical specification rather than after the verification.