Skip to content

Commit 930bfa9

Browse files
Ronald Tseronaldtse
authored andcommitted
docs: paper C draft — neural artifacts under a deterministic contract
1 parent 3f26a6e commit 930bfa9

1 file changed

Lines changed: 84 additions & 0 deletions

File tree

‎docs/paper-c.adoc‎

Lines changed: 84 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,84 @@
1+
= Neural Artifacts Under a Deterministic Contract: Verified Model Delivery for the Client Tier
2+
Ronald Tse
3+
v0.1 draft, 2026-09-03
4+
:doctype: article
5+
:toc: macro
6+
:numbered:
7+
8+
toc::[]
9+
10+
== Abstract (draft)
11+
12+
Deterministic transliteration systems ship as machine-readable maps
13+
that produce byte-identical output across runtimes; neural conversion
14+
models (diacritization, grapheme-to-phoneme) have historically shipped
15+
as loose weights with none of that discipline. We present the Interscript
16+
Model Format (IMF v1) and its delivery channel: content-addressed zips
17+
(per-member SHA-256) resolved through a tag-pinned index with sidecar
18+
verification, served from release assets through a CORS front door,
19+
cached once per client, and executed byte-identically across
20+
TypeScript, Python, and Ruby runtimes. We measure the cost of this
21+
discipline across three tiers — node, server, and browser — and find
22+
it effectively free: whole-file hashing adds ~0.1 s against 7-13 s
23+
session creation, verified reloads complete in ~0.4 s from cache, and
24+
a 202 MB int8 model runs end-to-end in a headless browser over WASM.
25+
A margins-based quantization gate (keeping the 1.2M-parameter head in
26+
fp32) cuts silent int8 flips 36x at +0.4% artifact size. Eleven-to-17
27+
models ship under the contract with full provenance.
28+
29+
== 1. Introduction
30+
- the deterministic-map discipline (OGC ISC context) and why learned
31+
functions deserve the same contract
32+
- threat model: untrusted channels, silent quantization flips, stale
33+
replicas, mojibake label provenance (the run-004 forensics)
34+
35+
== 2. The artifact contract (IMF v1)
36+
- zip + metadata.yaml + per-member sha256; fixed ByT5 byte table
37+
(byte+3, trailing EOS); opset-14 floor; KV decoder graphs
38+
- cross-runtime parity: byte-identical decode in TS/Py/Ruby
39+
- provenance: labels sha256 recorded in every verdict; per-paragraph
40+
predictions saved with every evaluation
41+
42+
== 3. The delivery channel
43+
- tag-pinned index (index-vN) + .sha256 sidecar; never a branch head
44+
- GitHub Releases as origin; the CORS front door (the github.com
45+
redirect hop lacks ACAO — measured); Range-resumable downloads
46+
- client cache: download-once Cache API with stale-entry eviction and
47+
offline index fallback
48+
- OIDC trusted publishing end-to-end (npm, PyPI, RubyGems)
49+
50+
== 4. Tier measurements (E1/E2/E3)
51+
| tier | cold | warm | verify tax | decode (short/long) |
52+
|---|---|---|---|---|
53+
| node (M-series) | 25 s net / 0.5 s cache | 0.4 s | 0.11 s | 1.0-2.8 s |
54+
| server (4-vCPU) | 3.9-4.0 s | — | included | 0.13-0.97 s |
55+
| browser (WASM) | 44-74 s | 20 s (session rebuild) | included | end-to-end |
56+
57+
- int4 vs int8: 2x faster load, ~2.5x slower decode — int8 default
58+
- confidence signal: per-step top-2 logit gap exposed to clients
59+
60+
== 5. The quantization gate
61+
- margin analysis across the catalog; the Hebrew int8 artifact flipped
62+
9.34% of positions invisibly to the CER gate
63+
- controlled probe matrix isolates the head; fp32 head = 36x fewer
64+
flips at +0.4% size; now the export default + release gate
65+
66+
== 6. Reproducibility discipline
67+
- subset-overstatement: five instances, up to 3.2x inflation
68+
- full-set-only rule; paired sentence-level bootstrap CIs on every
69+
verdict; provenance hashing (identical numbers must mean identical
70+
data — the run-004 lesson)
71+
72+
== 7. Related work
73+
- content provenance: statistical watermarks, C2PA content credentials
74+
(Fable 5.1) — our sha256 chain is the artifact-side analog
75+
- model zoos and packaging formats; speculative serving tiers
76+
77+
== 8. Limitations
78+
- browser tier session rebuild ~20 s per page load (persisted warm
79+
state is future work); WebGPU unmeasured; single-manufacturer
80+
hardware for E1
81+
82+
== 9. Artifacts
83+
All benchmarks, the index workflow, and the 17-model catalog are
84+
public; every number in this paper regenerates from committed scripts.

0 commit comments

Comments
 (0)