Humuhumu33 commited on
Commit
eca2bfd
verified
1 Parent(s): cb5ac87

Add branded Hologram model card

Browse files
Files changed (1) hide show
  1. README.md +84 -0
README.md ADDED
@@ -0,0 +1,84 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ ---
2
+ license: apache-2.0
3
+ base_model: allenai/OLMoE-1B-7B-0924-Instruct
4
+ pipeline_tag: text-generation
5
+ inference: false
6
+ tags:
7
+ - hologram
8
+ - q
9
+ - kappa-object
10
+ - holo
11
+ - moe
12
+ - olmoe
13
+ - allenai
14
+ ---
15
+
16
+ <div align="center">
17
+
18
+ # Hologram 路 OLMoE-1B-7B
19
+
20
+ **Mixture of experts (64 x 8)**
21
+
22
+ `q4 路 MoE` 路 `3.6 GB` 路 streamed to Q as a **key-addressable `.holo` object**
23
+
24
+ [Hologram](https://gethologram.ai) 路 [Live Space](https://huggingface.co/spaces/HOLOGRAMTECH/hologram) 路 [Organization](https://huggingface.co/HOLOGRAMTECH) 路 [Code](https://github.com/Hologram-Technologies)
25
+
26
+ </div>
27
+
28
+ ---
29
+
30
+ ## What this is
31
+
32
+ The first resident-MoE key object: 64 experts held in memory with an 8-of-64 top-k router. About 1.3B active parameters of a 7B model per token.
33
+
34
+ This repository is **not** a GGUF or Transformers checkpoint. It is a **Hologram key object**: the weights of `allenai/OLMoE-1B-7B-0924-Instruct` re-encoded into Hologram's content-addressed `.holo` format so they stream, one verified block at a time, into **Q**, the on-device brain of the Hologram web OS. It runs in the browser on WebGPU, serverless, with nothing to install.
35
+
36
+ ## How it streams
37
+
38
+ The object is laid out for cold streaming from an untrusted CDN:
39
+
40
+ | File | Role |
41
+ |---|---|
42
+ | `manifest.json` | the root. Names every tensor and the key (content hash) of its block. |
43
+ | `b/sha256_*.gz` | the tensor blocks. Each filename **is** the SHA-256 of its bytes. |
44
+ | `tokenizer.gguf` | bundled header (where present), so loading is fully serverless. |
45
+
46
+ Q fetches the manifest, then pulls each block by its key and re-derives `sha256(block)` on arrival. If a byte is wrong, the block is rejected. Nothing is trusted; everything is proven.
47
+
48
+ ## Verify (Law L5)
49
+
50
+ The object's identity is the SHA-256 of its manifest, pinned in Q's catalog before a single byte of weight is trusted:
51
+
52
+ ```
53
+ did:holo:sha256:9cf97ec1c761fd4ef51bc0cd4ac37a0cd8eaa11f1b19b3ae6a141486ad3fe5ad
54
+ ```
55
+
56
+ ```bash
57
+ # the manifest hash equals the pinned identity above
58
+ curl -sL https://huggingface.co/HOLOGRAMTECH/q-olmoe-1b-7b/resolve/main/manifest.json | sha256sum
59
+ ```
60
+
61
+ ## Specifications
62
+
63
+ | | |
64
+ |---|---|
65
+ | Architecture | OLMoE (64 experts, 8 active) |
66
+ | Precision | q4 路 MoE |
67
+ | Object size | 3.6 GB |
68
+ | Hidden size | 2048 |
69
+ | Layers | 16 |
70
+ | Heads (Q / KV) | 16 / 16 |
71
+ | FFN | 1024 x 64 experts |
72
+ | Vocab | 50304 |
73
+ | Context | 3000 |
74
+ | Format | `holo-2bit/1` |
75
+
76
+ ## Provenance and license
77
+
78
+ Derived from [`allenai/OLMoE-1B-7B-0924-Instruct`](https://huggingface.co/allenai/OLMoE-1B-7B-0924-Instruct). The re-encoding is lossless-by-construction at the key level: every block is content-addressed, so the object either re-derives to its pinned identity or it is refused.
79
+
80
+ ## Run it
81
+
82
+ These weights load through Q, not a standard runtime. Open the [Live Space](https://huggingface.co/spaces/HOLOGRAMTECH/hologram) or visit [gethologram.ai](https://gethologram.ai) to run Hologram, then pick **OLMoE-1B-7B** from Q's model list.
83
+
84
+ <div align="center"><sub>Composed on the golden ratio. One key, everything.</sub></div>