DigitableCourses
Local and account-free. No account, no sign-up: whatever you type into the tools stays in this browser's localStorage and never reaches a server.
Our own counter records page opens and finishes: the address leaves, plus one tenth-of-the-text figure. No cookies, no outside trackers, your IP is not stored, Do Not Track is honoured. How to check that
The portal's own repository is not published, so we do not call it open source. What is open:
The portal lives on donations, paid consultations and requested write-ups, and on Workbench sales.
There are no plans to make the courses paid.
Deployment of 16 September 2026, snapshot 95043e5
What has changed on the portal since your last visit. The full list of deployments is in the “What has changed” section on the About page.
31 articles on this topic.
A walk through the digitdisk source tree: the decisions live in a flang core with 14 postconditions, the conversation with the operating system lives in a Go host with …
Eight stages with tasks that the compiler checks, five solution patterns, and one honest answer to the question of why this language is needed.
The entire flang in a single listing without tabs or folds: each language form with all its variations and each construct with an explanation – a page for a complete …
A rule in Russian is transformed into an FTS specification, compiled by a real compiler, and passes a fallacy detector; there are three outcomes, not two.
All forms of flang and FTS: each has a working example that can be opened in the sandbox by clicking and edited there.
What is the flang language: two classes of programs, printing in nine languages, self-application, fspec — specs written in flang — and a clear boundary between proven …
Two Digit MCP servers – a deterministic catalog of utilities and a verification gateway over FTS – as Digitable Workbench integrations: what already works and what still …
Three sources of content instead of generation, two modes with a ban on silent degradation, and a rejection that accepts code, not a model.
How to check a new business requirement for consistency with already accepted ones before writing code: interval arithmetic over rule conditions, constitution invariants …
Half of the lodash calls in the project are business rules without a model, the other half have been in standard JavaScript for a long time. flang takes only the first.
How to replace check, prove, certify, and visualize with one pipeline call and what exactly the mermaid diagram of category, morphisms, and proof shows.
Step-by-step migration of a live business rule from nested ifs to the model with a proof of equivalence until the old code is turned off.
Nothing matched that query.