RAGdoll · Architecture note
Architecture and trust boundaries
How provider, scholarly-source, storage, evidence, and terminal boundaries preserve user control and keep model output outside domain logic until validation succeeds.
Read the artifactTechnical notes
Work explained far enough to be questioned.
A curated index of architecture notes, theory chapters, experiment reports, and engineering contracts already maintained with their source projects. This is not a publication list or a posting schedule.
RAGdoll · Product contract
Evidence and cited dossiers
The distinction between metadata, abstracts, acquired full text, page-aware passages, and the citations that support synthesized claims.
Read the artifactsmaLLM · Theory handbook
From tensors to a GPT
A zero-prerequisite path through tensors, probability, tokenization, autograd, causal attention, the decoder-only Transformer, training, evaluation, and the source implementation.
Read the artifactsmaLLM · Experiment report
Final capacity-controlled tokenizer panel
The preregistered final comparison of boundary-aware ByteBPE512 and matched character controls, including every seed, corpus, checkpoint identity, reversal, and limitation.
Read the artifactinsIGht · Engineering note
Privacy by design for local archive analytics
Why official exports, local persistence, bounded archive parsing, no telemetry, and explicit limitations are product behavior rather than implementation details.
Read the artifactAudioLab · System design
Hardware, firmware, and host boundaries
The repository contract separating an implemented TLV320AIC3104 daughterboard, STM32 firmware, host tooling, specifications, and future verification work.
Read the artifact