0001 Aligning with what already exists
The Korean version is authoritative. This page was translated by AI (Claude) and has not yet been checked by a person. 한국어 원문
While writing the Hahoe Genesis Protocol (HGP) documents for the first time, we read what already existed: the September HGP specification draft, arkive, secretary, and the personal archive and cheroki. We decided to align the twelve places where they had drifted apart as follows.
| # | What | How it had diverged | What we decided | Documents updated |
|---|---|---|---|---|
| 1 | Name of the owner | Specification “speaker”, arkive “depositor”, secretary “user” | Depositor | 01 |
| 2 | Does the administrator see the original? | Specification: does not see it. arkive: no encryption, the institution sees private records. secretary: encrypted from v0.2 | “Cannot see it” is the principle. Until encryption is in place, we state that it is kept only by promise. arkive’s “institution” is a viewer | 00, 01 |
| 3 | When fingerprints are taken | secretary twice (phone and server), arkive once (server), cheroki no audio fingerprint | Twice, on the device and in the store. If the device cannot take one, keep the received file as is + bundle fingerprint | 02 |
| 4 | Unit of the fingerprint | Specification: chunks + Merkle tree, arkive: one scan (two faces) | The leaves of the Merkle tree are the original files. A face is a region inside a file | 02, 03 |
| 5 | Daily bundle fingerprint | Specification: anchored in two places; the personal archive’s anchoring tool was never run | The daily fingerprint is defined now. Anchoring comes with secretary v2 | 02 |
| 6 | How far a record is from the original | Specification L0 to L3, arkive and the personal archive use other names | Specification terms: L0 original, L1 draft, L2 confirmed, L3 derived | 03, 04 |
| 7 | “layer 0/1/2” | Same meaning as the specification’s layers (protocol, sovereignty, gateway), but clashes with L0 to L2 (provenance grade) | Layers written like “0층 규약” (layer 0 protocol), provenance grade written like “L0” | 04 |
| 8 | Who can see a record | arkive 7 fields, specification 4 fields, the 9/10 decision text 5 fields | Separate scope into 5 values (sealed, private, relation, community, public) and use into 3 fields | 00, 03 |
| 9 | Principles | secretary 8, blueprint 7, specification 5 invariants | The 8 are the main text. The three of the specification’s 5 that were missing become “additional commitments” | 00 |
| 10 | manifest fields | secretary code, arkive fixity.tsv and the personal archive hashes.jsonl all differ. No field for AI contribution |
Use secretary’s field names as the base, and add fields for specification version, provenance grade and AI contribution | 03 |
| 11 | Originals never change | secretary and arkive are read-only, cheroki renames originals | The personal archive and cheroki are not changed. HGP applies from new recordings on | 04 |
| 12 | Other people’s voices | secretary: one consent line on the onboarding screen (planned), personal archive: no consent field | A person’s passages belong to that person. Until they consent, only the two people can open them | 01 |
One point under #10: the fingerprint fields sha256_phone and sha256_server do not fit scans of old documents, so their names were broadened to sha256_device and sha256_store. secretary will align at its next data structure change (03-manifest section 11).
- If the documents drift away from the code, nobody follows them. We took the secretary and arkive code that is already running, and the September specification that was already written, as the base.
- The “canonical terminology” (2026-09-11) of the September specification had already separated “layer” and “provenance grade”. We carried that decision forward as it was.
Other options
Section titled “Other options”| Option | Why not chosen |
|---|---|
| Bring over all 44 documents of the September specification | They are still drafts and overlap a lot (as the axis map points out). We cut them down to five documents in plain Korean and point to them as sources |
| Follow only secretary’s names | Some fields do not fit old documents (arkive) (sha256_phone) |
Where it has effect
Section titled “Where it has effect”- secretary: add the fields
hgp,level,source_type,action,made_by,scope,consentto the manifest. Align fingerprint field names. Daily fingerprint. Regular fingerprint checks. (This is a data structure change, so it needs separate approval on the secretary side.) - arkive: naming the depositor, encryption, login, volume fingerprint, attaching fingerprints to IIIF canvases, regular fingerprint checks.
- Personal archive and cheroki: not changed.
To look at separately (outside this decision)
Section titled “To look at separately (outside this decision)”- How to reconcile arkive protocol article 10 (with consent, “learning how to read” is allowed) with principle 8 (not used for training).