Why determinism is the more interesting property than speed
AI assistants make generation cheap. The bottleneck moves to where it was already tight — and determinism is what reopens it.
When generating code costs nothing, writing is no longer the bottleneck — everything after it is: understanding, checking, proving. All three presuppose that identical inputs produce identical results.
What determinism means here, concretely
For aSPARK, determinism does not mean a language model produces the same text twice — it doesn't, and it doesn't need to. What is deterministic are the derived models: two builds of an unchanged repository produce a byte-identical graph.json. The same commitment holds for the sealed snapshots in aSPARK-insights.
That is a deliberately narrow claim. It is enough to enable three things:
- Comparability. A diff between two snapshots shows a real change in the project, not tooling noise.
- Traceability. A query answer can be reproduced instead of merely believed.
- Auditability. An audit can rebuild the state instead of relying on a snapshot in time.
What it costs
Determinism costs expressiveness. A graph allowed to guess could find more connections. aspark-graph does not guess — it tags weak edges as inferred and fails loudly on template drift instead of quietly bridging it.
That is the right trade for a tool whose answers feed gate decisions. A graph answer is a map, never a verdict.
This post is the template for further articles. New posts go in as a Markdown file under src/blog/en/ and appear in the index and feed automatically.