Source preservation rule
When a new report edition arrives, preserve it under /docs and add a manifest record. Do not silently replace older editions. Duplicate hashes are acceptable because filenames, upload context, and release history are part of provenance.
Curated pages should cite the newest useful edition when it adds new material, but raw reports remain evidence until promoted.
Edition workflow
| Step | Action |
|---|---|
| Intake | Copy uploaded Markdown to /docs. |
| Hash | Record size and SHA-256. |
| Manifest | Add unique slug and summary. |
| Synthesis | Promote relevant positive claims into pages or .uai. |
| Release | Note additions in CHANGELOG and UAI ledger. |
FUNCTION add_source_edition(file)
copy_to_docs(file)
metadata = compute_size_and_sha256(file)
manifest_slug = create_unique_report_slug(file.name)
append_manifest(manifest_slug, metadata)
update_docs_source_ledger()
RETURN manifest_slug
END FUNCTIONPositive outcome
The project gains memory without confusion. Source history remains complete, and the current site remains curated.
Source reports used for this guide
These reports are preserved verbatim in the site archive. The guide above is an editorial synthesis and may narrow, qualify, or reorganize claims from the source material.
Model merging and adaptersModel Merging: Definitions, Taxonomy, Algorithms, Tooling, and Production Pipeline DesignEmerging practice · 35.7 KB
Browser and edge runtimeTeleodynamic Architecture and Rust-Native Browser Execution for Modular Tiny Language ModelsEmerging implementation architecture · 52.8 KB
Model merging and adaptersTiny-LLM Adapters and LoRA: Breeding Operators, Compatibility, Evaluation, and PromotionEmerging implementation practice · 15.3 KB