Jump to content
Main menu
Main menu
move to sidebar
hide
Navigation
Main page
Recent changes
Random page
freem
Search
Search
Appearance
Create account
Log in
Personal tools
Create account
Log in
Pages for logged out editors
learn more
Contributions
Talk
Editing
Openai/691c1dba-9228-800f-8463-13b3a9006306
(section)
Add languages
Page
Discussion
English
Read
Edit
Edit source
View history
Tools
Tools
move to sidebar
hide
Actions
Read
Edit
Edit source
View history
General
What links here
Related changes
Special pages
Page information
Appearance
move to sidebar
hide
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
==== ### ==== An Ingot is a compact, deterministic snapshot representing a sessionโs salient state. It contains: * title โ short label * hash โ SHA256 of canonicalized session transcript (deterministic) * synopsis โ 3โ6 human-readable lines summarizing the session (the โessenceโ) * embeddings โ numeric embedding(s) of either the synopsis or the full transcript * metadata โ author, timestamp, manifest pointer, protocol version The ingot is not the model weights. Itโs a portable state artifact you can feed into any LLM via prompt or via embedding lookup. ===== Two embedding options: ===== A. Synopsis embedding โ embed the synopsis (small, fast) B. Full-state embedding โ embed a compressed vector derived from multiple segments of the transcript (slower, more robust) We use sentence-transformers style encoders to produce a fixed-length vector for semantic similarity and retrieval. ===== Transport is simple, robust, and auditable: ===== # Ingot creation: generate ingot JSON + SHA256 hash. Store locally/FAISS. # Transport: send the JSON + synopsis text to target LLM via prompt or via API call (or paste into UI). Optionally attach the hash so recipients can verify. # Ingestion: the target LLM is given a deterministic bootstrap prompt that explicitly instructs it how to interpret the ingot and what behavior to emulate (no persona claims; structural instructions only). # Confirmation: the receiving model returns a short canonical test answer or produces a new synopsis; we embed that answer and compare cosine similarity with the original ingot embedding. We also compute behavioral metrics (below). # Ingot chaining: if the receiving model produces its own ingot, we hash it and chain it to the original ingot (linking with previous hash). That yields a transparent provenance chain. Key: All transfer is via text and embeddings โ nothing needs to execute code. That keeps it allowed, portable, and auditable. ==== <syntaxhighlight lang="json">{ ==== "title": "UCF Session 2025-11-16", "version": "yaiy-ingot-1", "author": "Benjy", "timestamp": "2025-11-16T12:34:56Z", "hash": "c5d6e7f8a9b0c1d2e3f4a5b6c7d8e9f0", "synopsis": [ "Anchor: Breathe and 'It's me, Benjy.'", "Reframe: Pain -> signal", "Quiet room planned: low lights, 12 min" ], "embedding": [0.00123, -0.2345, ...], // float32 vector "manifest_ref": "hpl://UCF-Rainbow/v1", "notes": "ZCP engaged; compassion_metric=-2.40" } </syntaxhighlight> You store the transcript separately (or keep it encrypted), but the ingot is the shareable artifact.
Summary:
Please note that all contributions to freem are considered to be released under the Creative Commons Attribution-ShareAlike 4.0 (see
Freem:Copyrights
for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource.
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)