diff options
| author | Ralph Amissah <ralph.amissah@gmail.com> | 2026-09-21 13:43:45 -0400 |
|---|---|---|
| committer | Ralph Amissah <ralph.amissah@gmail.com> | 2026-09-22 16:47:49 -0400 |
| commit | 884448835bbc63d0108f6f1391514b88fd41e280 (patch) | |
| tree | 77dbe4c2c83dfb2f910da841202ec1b263e3fc93 /test | |
| parent | dispatch: pod materialised if source required (diff) | |
dispatch: pod materialised if source required
actions requiring source first materialise the pod
One route per argument, decided by what was asked for. --source, --pod,
--pod2, --show-abstraction and --ocda-db need original markup, so an
.ocda.db given with any of them is written back out as a pod and parsed.
Asked only to render, it is read as an abstraction as before.
To ensure consistency, where a pod is materialized by an argument, that
pod is used for the whole run, including for html and epub that could
have been built from the loaded abstraction instead.
--show-abstraction and --ocda-db join the markup side deliberately.
They could be satisfied by re-serialising the abstraction already
loaded, and were. But an artefact is a statement about the source:
written from a loaded abstraction it says only that the loader is
self consistent, where written from the markup it says what this
spine (whatever current version) makes of that document today.
The chain is checkable against itself: --ocda-db from a database now
goes database, pod, parse, database, and returns the same 9,908,224
bytes it started from. --show-abstraction likewise re-emits the .ssp
files byte for byte.
A .ssp carries no markup by construction and a database written
before the format carried it has none, so both are refused for those
actions, once and by name, and the rest of the run goes on.
(assisted by Claude-Code)
Diffstat (limited to 'test')
0 files changed, 0 insertions, 0 deletions
