Home / Input Output / formal-ledger-specifications
May 18, 6-7 AM (0)
May 18, 7-8 AM (0)
May 18, 8-9 AM (0)
May 18, 9-10 AM (0)
May 18, 10-11 AM (0)
May 18, 11-12 PM (0)
May 18, 12-1 PM (0)
May 18, 1-2 PM (0)
May 18, 2-3 PM (0)
May 18, 3-4 PM (0)
May 18, 4-5 PM (0)
May 18, 5-6 PM (0)
May 18, 6-7 PM (0)
May 18, 7-8 PM (0)
May 18, 8-9 PM (0)
May 18, 9-10 PM (0)
May 18, 10-11 PM (0)
May 18, 11-12 AM (0)
May 19, 12-1 AM (0)
May 19, 1-2 AM (0)
May 19, 2-3 AM (0)
May 19, 3-4 AM (0)
May 19, 4-5 AM (0)
May 19, 5-6 AM (0)
May 19, 6-7 AM (0)
May 19, 7-8 AM (2)
May 19, 8-9 AM (0)
May 19, 9-10 AM (1)
May 19, 10-11 AM (1)
May 19, 11-12 PM (2)
May 19, 12-1 PM (0)
May 19, 1-2 PM (2)
May 19, 2-3 PM (2)
May 19, 3-4 PM (0)
May 19, 4-5 PM (0)
May 19, 5-6 PM (0)
May 19, 6-7 PM (0)
May 19, 7-8 PM (0)
May 19, 8-9 PM (0)
May 19, 9-10 PM (0)
May 19, 10-11 PM (0)
May 19, 11-12 AM (0)
May 20, 12-1 AM (0)
May 20, 1-2 AM (3)
May 20, 2-3 AM (3)
May 20, 3-4 AM (0)
May 20, 4-5 AM (0)
May 20, 5-6 AM (0)
May 20, 6-7 AM (0)
May 20, 7-8 AM (0)
May 20, 8-9 AM (0)
May 20, 9-10 AM (0)
May 20, 10-11 AM (0)
May 20, 11-12 PM (0)
May 20, 12-1 PM (1)
May 20, 1-2 PM (1)
May 20, 2-3 PM (1)
May 20, 3-4 PM (0)
May 20, 4-5 PM (0)
May 20, 5-6 PM (1)
May 20, 6-7 PM (1)
May 20, 7-8 PM (0)
May 20, 8-9 PM (0)
May 20, 9-10 PM (0)
May 20, 10-11 PM (0)
May 20, 11-12 AM (0)
May 21, 12-1 AM (0)
May 21, 1-2 AM (0)
May 21, 2-3 AM (0)
May 21, 3-4 AM (0)
May 21, 4-5 AM (4)
May 21, 5-6 AM (3)
May 21, 6-7 AM (1)
May 21, 7-8 AM (0)
May 21, 8-9 AM (0)
May 21, 9-10 AM (0)
May 21, 10-11 AM (0)
May 21, 11-12 PM (0)
May 21, 12-1 PM (0)
May 21, 1-2 PM (1)
May 21, 2-3 PM (0)
May 21, 3-4 PM (0)
May 21, 4-5 PM (1)
May 21, 5-6 PM (0)
May 21, 6-7 PM (0)
May 21, 7-8 PM (3)
May 21, 8-9 PM (2)
May 21, 9-10 PM (0)
May 21, 10-11 PM (0)
May 21, 11-12 AM (0)
May 22, 12-1 AM (0)
May 22, 1-2 AM (1)
May 22, 2-3 AM (4)
May 22, 3-4 AM (3)
May 22, 4-5 AM (0)
May 22, 5-6 AM (0)
May 22, 6-7 AM (0)
May 22, 7-8 AM (0)
May 22, 8-9 AM (0)
May 22, 9-10 AM (0)
May 22, 10-11 AM (0)
May 22, 11-12 PM (0)
May 22, 12-1 PM (0)
May 22, 1-2 PM (0)
May 22, 2-3 PM (3)
May 22, 3-4 PM (0)
May 22, 4-5 PM (0)
May 22, 5-6 PM (0)
May 22, 6-7 PM (0)
May 22, 7-8 PM (0)
May 22, 8-9 PM (0)
May 22, 9-10 PM (0)
May 22, 10-11 PM (0)
May 22, 11-12 AM (3)
May 23, 12-1 AM (0)
May 23, 1-2 AM (2)
May 23, 2-3 AM (3)
May 23, 3-4 AM (5)
May 23, 4-5 AM (0)
May 23, 5-6 AM (0)
May 23, 6-7 AM (0)
May 23, 7-8 AM (0)
May 23, 8-9 AM (1)
May 23, 9-10 AM (0)
May 23, 10-11 AM (0)
May 23, 11-12 PM (0)
May 23, 12-1 PM (0)
May 23, 1-2 PM (0)
May 23, 2-3 PM (0)
May 23, 3-4 PM (0)
May 23, 4-5 PM (0)
May 23, 5-6 PM (0)
May 23, 6-7 PM (4)
May 23, 7-8 PM (5)
May 23, 8-9 PM (3)
May 23, 9-10 PM (0)
May 23, 10-11 PM (0)
May 23, 11-12 AM (0)
May 24, 12-1 AM (0)
May 24, 1-2 AM (0)
May 24, 2-3 AM (0)
May 24, 3-4 AM (0)
May 24, 4-5 AM (0)
May 24, 5-6 AM (0)
May 24, 6-7 AM (0)
May 24, 7-8 AM (0)
May 24, 8-9 AM (0)
May 24, 9-10 AM (0)
May 24, 10-11 AM (0)
May 24, 11-12 PM (0)
May 24, 12-1 PM (0)
May 24, 1-2 PM (0)
May 24, 2-3 PM (0)
May 24, 3-4 PM (0)
May 24, 4-5 PM (0)
May 24, 5-6 PM (0)
May 24, 6-7 PM (0)
May 24, 7-8 PM (0)
May 24, 8-9 PM (0)
May 24, 9-10 PM (0)
May 24, 10-11 PM (0)
May 24, 11-12 AM (0)
May 25, 12-1 AM (0)
May 25, 1-2 AM (0)
May 25, 2-3 AM (0)
May 25, 3-4 AM (0)
May 25, 4-5 AM (0)
May 25, 5-6 AM (0)
May 25, 6-7 AM (0)
73 commits this week May 18, 2025 - May 25, 2025
build pdf from legacy-latex and generate web site
1.  **PDF Jobs (`...-pdf`)**:
    * removed `uses: ./.github/workflows/build_artifact.yml`;
    * added build steps (Nix install, `fls-shake`, upload) directly into job;
    * Most importantly, there are now *two* checkout steps; the first checks out current branch (`master-markdown`); the second uses `sparse-checkout` to grab *only `src` directory* from `legacy-latex` branch and places it into workspace, overwriting `src` from `master-markdown`;
    * When `fls-shake` runs, it uses build environment from `master-markdown` (our `flake.nix`, etc.) but operates on legacy LaTeX source.

2.  **MkDocs Job (`mkdocs-site`)**:
    * new job runs only on pushes/PRs to `master-markdown`;
    * uses `_build` artifact from initial Agda compilation;
    * calls `nix develop .#markdown --command "cd _build/mkdocs/src && mkdocs build --site-dir ../../../site"`;
    * resulting `site` directory is uploaded as new artifact named `mkdocs-site`.

3.  **Artifacts Job (`upload-artifacts`)**:
    * job now depends on new `mkdocs-site` job;
    * downloads the `mkdocs-site` directory along with all other artifacts and commits them to `*-artifacts` branch, integrating new website into existing artifact deployment process.
fix "mkdocs serve" instructions output by build.py
I can't find a way to launch the server from the PROJECT_ROOT and also
have the global links file working, even if I specify the `mkdocs.yml`
config file location explicitly with the `--config-file` flag.  So (for
now at least) we must CWD to the `_build/mkdocs/src/` directory before
running `mkdocs serve` to serve/test the site locally.