01 / TASKWhat must someone complete?
Describe the person, starting point, desired outcome, current workaround, and the failure that matters most.
Scope ledger
You do not need a finished specification. A useful first note makes the user, current problem, systems, country connection, and decision owners visible enough to choose the next investigation.
01 / TASKDescribe the person, starting point, desired outcome, current workaround, and the failure that matters most.
02 / ESTONIA LINKName users, operations, partners, content, data, transactions, or authorities connected to Estonia. Avoid assumptions about location or market fit.
03 / LANGUAGEList the required languages, who writes or translates, who approves terminology, and how support will handle misunderstandings.
04 / DATAInclude personal fields, documents, analytics, identity, vendors, regions, access, retention, and sensitive categories.
05 / SYSTEMSNote current software, hosting, integrations, accounts, source access, constraints, and any active production behavior that must be protected.
06 / PROOFName devices, journeys, records, reviewers, dates, release authority, monitoring, handoff needs, and the safe rollback expectation.
Send the ledger
Do not email passwords, private keys, government identifiers, payment-card data, production exports, or other secrets. We can establish a safer exchange path if the scope needs sensitive material.