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 catalog of fourteen attempts to push effect, time, randomness, and execution order into flang — with real compiler messages and a working separation into model and …
Why there is no “today” in the specification, how to store rule revisions alongside and what to prove to the client the charge for April according to the …
flang diagnostics reference: code, exact message, minimal reproducible example, and fix — separately for walkthrough, model check, utility execution, examples, and proof.
End-to-end architecture: flang order model, examples, command guard, React form, Node.js boundary, agent, and CI.
Harness, with which you take your compile/validate/execute/generate digits and compare them to the baseline, instead of trusting others’ milliseconds.
How to generate TypeScript and node:test, check models in pull request and not edit artifacts manually.
A real Python, Go, and shell client for flang via CLI and canonical JSON: what the compiler actually prints, how to read diagnostics, and when to use HTTP instead of a …
What exactly does flang prove, how symbolic derivation differs from a verified certificate, and what is insufficient for publication or a patent.
How to integrate flang into the agent loop: read-only MCP tools, programmatic document build, guard on real data, and machine-readable refusal.
How to integrate flang into the domain layer, not turn the specification into a god-object, and protect the team with a verifiable admission.
Form schema from the flang object, controls by field types and pre-calculation in the browser, which the server still re-checks anyway.
How to load the model once, run the utility in Node.js, and not mix computation with HTTP, response codes, and request bodies.
Nothing matched that query.