输入保持字节级
Byte-level input
所有语言、符号和编码细节都保留在 byte stream 中,避免词表边界提前丢失信息。
All languages, symbols, and encoding details stay in the byte stream, so no information is lost early at vocabulary boundaries.
Chapter 01 · 研究问题Chapter 01 · Research Question
Alethic Insight Research Archive
Byte-to-Latent Decision Interface
FLUED 研究如何把原始字节流翻译成神经网络更容易处理的连续潜空间表示, 同时保留字节级可还原能力。它不是新的 tokenizer 宣传页,而是一条语言编码器路线: 让模型先在连续语义空间中理解和补全,再通过 decoder 精确回到 byte。
FLUED studies how to translate a raw byte stream into a continuous latent representation that neural networks handle more easily, while preserving byte-level recoverability. It is not a promotional page for a new tokenizer, but a language-encoder research line: let the model understand and complete in a continuous semantic space first, then return precisely to bytes through the decoder.
Can byte streams be converted into latent intelligence without freezing language into a vocabulary?
Research Question
BPE 把字符串先离散切成 token,再让 embedding 表承载大量语义先验。 FLUED 的出发点是把这一步改成可训练、可还原、可压缩的 byte-to-latent 翻译过程。
BPE first discretizes a string into tokens, then lets the embedding table carry much of the semantic prior. FLUED's starting point is to turn this step into a trainable, recoverable, and compressible byte-to-latent translation process.
所有语言、符号和编码细节都保留在 byte stream 中,避免词表边界提前丢失信息。
All languages, symbols, and encoding details stay in the byte stream, so no information is lost early at vocabulary boundaries.
readout latent 承载局部语义和位置信息,让外部 backbone 在更平滑的空间中学习。
The readout latent carries local semantics and position, letting an external backbone learn in a smoother space.
latent representation 必须能通过 tied decoder 回到 byte,不能只追求不可解释的中间特征。
The latent representation must return to bytes through a tied decoder; uninterpretable intermediate features alone are not enough.
Research Route
FLUED 的迭代不是从“小模型”走到“大模型”,而是沿一个问题逐代排雷:软切分能跑通吗、训练稳吗、 严格口径下还有效吗、压到最硬还剩什么。节点是版本,判词是结局——判死的也留在线上,点击跳到对应证据。
FLUED's iteration is not a march from a small model to a large one, but a generation-by-generation clearing of one question: does soft segmentation work, is training stable, does it survive a strict protocol, and what remains at the hardest setting. Nodes are versions and verdicts are outcomes — even the ruled-out stay on record, each linking to its evidence.
逐代展开:三代的问题意识Generation by generation: three eras of framing
v1 的价值在于把 byte stream -> latent units -> tied inverse bytes 这条链路跑通, E1v5 达到 recon_acc 0.9999、m/n 0.379、bp_std 0.443,并在历史 E3 中出现强 BPB 信号。 问题是短序列还原能力差, 压缩率、阈值和训练参数仍像 magic number,语义质量也不能只靠重建证明。
v1's value was getting the byte stream -> latent units -> tied inverse bytes chain to work: E1v5 reached recon_acc 0.9999, m/n 0.379, and bp_std 0.443, with a strong BPB signal in the historical E3. The problems: poor short-sequence recovery, compression rate, thresholds, and training hyperparameters still looking like magic numbers, and semantic quality that reconstruction alone cannot prove.
v2 加入 denoising 后三种子重建稳定,但去噪任务、压缩约束和边界分化之间存在冲突。 latent consistency 的均方误差损失曾直接触发 loss 爆炸和边界塌缩; 去噪比例扫描显示 m/n 随噪声漂移,压缩权重扫描在部分 target 上出现 NaN。
With denoising added, v2's three-seed reconstruction was stable, but the denoising task, the compression constraint, and boundary divergence conflicted. The MSE loss on latent consistency once directly triggered a loss explosion and boundary collapse; the denoise-ratio scan showed m/n drifting with noise, and the compression-weight scan produced NaN at some targets.
v3 不再把 reconstruction 当作唯一目标,而是追问 latent readout 是否真的降低外部 backbone 的学习难度。 这让 FLUED 接近 BLT、H-Net、ByteFlow、FLEXITOKENS 等方向共同面对的问题: 如何扩大计算复杂度、语义自然度、训练难度的不可能三角面积。
v3 stopped treating reconstruction as the sole goal and instead asked whether the latent readout genuinely lowers an external backbone's learning difficulty. This brought FLUED to the question it shares with BLT, H-Net, ByteFlow, and FLEXITOKENS: how to enlarge the impossible triangle of compute complexity, semantic naturalness, and training difficulty.
v1 soft-boundary autoencoder 在历史 E3 20K 设置中,相比 BPE 有约 18.1% 更低的 bits-per-byte, 并在同一历史设置下优于当时的 BLT reproduction。这是 FLUED 路线最早的强阳性信号。
In the historical E3 20K setting, the v1 soft-boundary autoencoder reached about 18.1% lower bits-per-byte than BPE, and beat the BLT reproduction of the time under the same historical setting — the earliest strong positive signal for the FLUED line.
v2 在 2048 原始 byte、100K steps、统一 downstream backbone 的矩阵下稳定但落后 BPE。 这说明 v1 信号值得重视,但不能直接外推为生产 tokenizer 替代结论。
Under a matrix of 2048 raw bytes, 100K steps, and a unified downstream backbone, v2 was stable but trailed BPE. The v1 signal deserves attention, but it cannot be extrapolated into a production tokenizer-replacement conclusion.
严格在 byte 输入层 mask 后,no-memory latent backbone 明显超过 byte baseline。 这是 v3 系列目前最干净的正向证据。
With strict masking at the byte input layer, the no-memory latent backbone clearly beat the byte baseline — currently the cleanest positive evidence in the v3 series.
最小假设:soft segmentation + tied inverse decoder,证明可微 byte codec 有信号,但短序列和超参魔数暴露完成度不足。
Minimal hypothesis: soft segmentation + tied inverse decoder showed a differentiable byte codec has signal, but short sequences and hyperparameter magic numbers exposed its immaturity.
大模型与去噪:328M tied model 三种子重建稳定,同时暴露 denoising、compression、boundary 之间的训练动力学冲突。
Scale-up and denoising: the 328M tied model reconstructed stably across three seeds, while exposing training-dynamics conflicts among denoising, compression, and boundary.
语言编码器原型:readout latent / summary memory / minimal backbone,但早期 clean encode 评估有侧漏风险。
Language-encoder prototype: readout latent / summary memory / minimal backbone, but early clean-encode evaluation risked information leakage.
严格 masked-source:先在 byte 输入层 mask,再 encode,确认 latent readout 对小 backbone 有正向作用。
Strict masked-source: mask at the byte input layer before encode, confirming latent readout helps a small backbone.
架构截止点:segmentor、interpreter、memory、decoder 职责拆开,转向系统消融和公开复现。
Architecture cutoff: segmentor, interpreter, memory, and decoder responsibilities separated; the focus turned to systematic ablation and public reproduction.
消融矩阵(2026-07):共享逆以三重证据判死、独立 decoder 成为默认;提出 CBIU(counterfactual boundary utility,反事实边界效用)协议评估单点边界贡献。
Ablation matrix (2026-07): the shared inverse was ruled out by triple evidence and a standalone decoder became the default; the CBIU (counterfactual boundary utility) protocol was proposed to score single-point boundary contributions.
KDA 世代(2026-07/08):S0 segmentor 预训 F1 0.886;组件预训 +5.8pp 判死端到端;归因矩阵确认增益全部来自 S0 动态边界;S0.5 GRPO 边界优化停于 24.3 段 ≈ 用户手标 21B;S0.7 逐段条件化证明检索瓶颈可解、路线活。
KDA generation (2026-07/08): S0 segmentor pretraining F1 0.886; component pretraining beat end-to-end by +5.8pp, ruling the latter out; the attribution matrix confirmed all gains come from S0 dynamic boundaries; S0.5 GRPO boundary optimization settled at 24.3 segments ≈ 21B human-marked granularity; S0.7 per-chunk conditioning showed the retrieval bottleneck is solvable — the line stays alive.
Current Position
地图走到这里,就是现在:v3.6(KDA 世代)把 512 字节 prompt 经动态切分、逐段摘要和 KDA 状态机串行消费后, 只保留 1 个 readout 包(1,536 标量),再由 decoder 从固定大小状态还原原文。 下面四个入口是理解当前证据的最短路径;v2 D1 等旧口径保留在研究地图,不替代当前结论。
This is where the map arrives: v3.6 (the KDA generation) consumes a 512-byte prompt through dynamic segmentation, per-chunk summarization, and a serial KDA state machine, keeps exactly one readout package (1,536 scalars), and lets the decoder restore the text from a fixed-size state. The four entries below are the shortest path into the current evidence; older protocols such as v2 D1 remain on the research map and do not replace current conclusions.
S0 动态边界、ChunkSummarizer、WriteHead 门控写入、KDA 状态机串行消费,整条 prompt 恰好读出 1×1,536 标量。
S0 dynamic boundaries, ChunkSummarizer, WriteHead gated writes, and a serial KDA state machine read out exactly 1×1,536 scalars for the whole prompt.
Read architecture单 seed、38–44M 同规模、同 20K 步同语料、同 masked infilling 口径;信息传输 1,536 vs ~97,540 标量,同指标约 60× 信息效率。
Single seed, matched 38–44M scale, same 20K steps on the same corpus, same masked-infilling protocol; 1,536 vs ~97,540 scalars transmitted — about 60× information efficiency at the same metric.
Open frontierGRPO 组内排名优化边界与写入门,质量与控制臂打平——当前价值是选粒度而非提质量,教师粒度之争了结。
GRPO optimizes boundaries and the write gate by within-group ranking, tying the control arm on quality — its current value is choosing granularity, not improving quality; the teacher-granularity debate is settled.
Read S0.5–S0.7证明检索瓶颈可解、路线活;masked 未过预注册线,canonical 维持 v36.1,此臂不设默认。
Shows the retrieval bottleneck is solvable and the line stays alive; masked did not pass the pre-registered bar, so canonical stays at v36.1 and this arm is not the default.
Watch live demoEvidence
这里保留官网摘要。完整训练历程、100-step 曲线、NaN 断点和 strict masked-source 对照表放在独立证据浏览器中,方便读者直接比较。
This page keeps the site summary. The full training history, 100-step curves, NaN breakpoints, and strict masked-source tables live in a standalone evidence browser for direct comparison.
Boundary Showcase
同一段文本,五种切分来源并排:FLUED v3.6 的 S0 / GRPO R4 两个学习切分臂、H-Net 复现(学习切分)、BLT 字节 LM 熵切分、BPE 分词器。 全部来自预计算的真实模型输出(单 seed 演示口径,offsets 为 UTF-8 字节偏移),不是示意图; 实时演示可以在本机对任意输入重跑其中的模型。
The same text, five segmentation sources side by side: FLUED v3.6's two learned arms (S0 / GRPO R4), an H-Net reproduction (learned), BLT byte-LM entropy cuts, and the BPE tokenizer. All are precomputed real model outputs (single-seed demo protocol; offsets are UTF-8 byte offsets), not illustrations; the live demo reruns these models on any input on your own machine.
切分对比加载中…Loading segmentation comparison…
S0 臂按教师标注粒度切(约 27B/段);GRPO R4 臂经 S0.5 边界优化停在约 24 段 ≈ 用户手标 21B 粒度——任务奖励自选粒度,GRPO 当前的价值是选粒度而非提质量。 BPE 切得碎且无语义(zh 148 段 / en 319 段);BLT 熵切分是纯局部统计信号(entropy > 3.5 下刀); H-Net 是字节级模型,zh 文本存在字符内部下刀(段内出现 替换符为正常行为,数据已标注 lossless_join=false)。
The S0 arm cuts at teacher-annotated granularity (~27B/segment); the GRPO R4 arm, after S0.5 boundary optimization, settles at ~24 segments ≈ 21B human-marked granularity — the task reward chooses its own granularity, and GRPO's current value is choosing granularity, not improving quality. BPE cuts finely and is semantics-blind (148 segments zh / 319 en); BLT entropy cutting is a purely local statistical signal (cut where entropy > 3.5); H-Net is a byte-level model and cuts inside characters on zh text ( replacement chars within segments are expected; the data is marked lossless_join=false).
Architecture Trace
每一代架构都是一条从上而下的流水线,节点对应公开仓库里的真实模块,结局如实记录。 这里是摘要版;逐节点完整流水线、两任务口径与代码行级对照在架构追踪页。
Every generation is a top-to-bottom pipeline whose nodes map to real modules in the public repository, with outcomes recorded as they are. This is the summary; the full node-by-node pipelines, the two-task protocol, and line-level code references are on the architecture trace page.
状态:canonical v36.1。整条 prompt 压成 1×1,536 标量;masked 0.149 打赢 HNet-DiT 瓶颈臂 0.142(单 seed 同口径)。
Status: canonical v36.1. The whole prompt is compressed to 1×1,536 scalars; masked 0.149 beats the HNet-DiT bottleneck arm's 0.142 (single seed, same protocol).
逐节点流水线与 E20 退化证据见架构追踪页。
Node-by-node pipelines and the E20 degeneration evidence are on the architecture trace page.
sigmoid(Linear(ΔH)) 软切分 + O(T²) 池化 + tied inverse。结局:共享逆三重证据判死。
sigmoid(Linear(ΔH)) soft segmentation + O(T²) pooling + tied inverse. Outcome: the shared inverse was ruled out by triple evidence.
segmentor / policy / memory / decoder 七模块职责分离。结局:架构截止点,转向系统消融。
Seven modules with separated responsibilities: segmentor / policy / memory / decoder. Outcome: architecture cutoff; focus turned to systematic ablation.
DiT block、软桥、no-self memory、rate_emit 逐个过消融。结局:memory / emit 关闭,canonical_v35 固化。
DiT block, soft bridge, no-self memory, and rate_emit ablated one by one. Outcome: memory / emit closed; canonical_v35 frozen.
Related Thinking
FLUED 不是孤立提出的结构。它吸收了 tokenizer-free、动态分块、信息论压缩、 latent diffusion、草稿修正和控制空间映射等方向的启发,但最终目标仍是语言编码器, 不是直接复刻某一种 byte-level LM。
FLUED was not proposed in isolation. It borrows from tokenizer-free modeling, dynamic chunking, information-theoretic compression, latent diffusion, draft correction, and control-space mapping — but its end goal remains a language encoder, not a replica of any particular byte-level LM.
启发 FLUED 关注 byte-level 动态分块和局部不确定性;FLUED 不依赖大型预训练 ByteLM 作为唯一边界来源。
Inspired FLUED's focus on byte-level dynamic chunking and local uncertainty; FLUED does not rely on a large pretrained ByteLM as its only boundary source.
启发 readout 数量不应只靠 reconstruction loss 控制;v3.3 保留 rate pressure 和消融入口。
Motivated the idea that readout count should not be governed by reconstruction loss alone; v3.3 keeps rate pressure and an ablation entry.
启发 signed boundary、边界置信度诊断和 ROI 可视化;FLUED 避免把硬规则当作最终 tokenizer。
Inspired signed boundaries, boundary-confidence diagnostics, and ROI visualization; FLUED avoids treating hard rules as the final tokenizer.
证明“切分可以学习”这一路线有先例;FLUED 进一步要求 latent 可被 decoder 反向还原为 byte span。
Established precedent that segmentation can be learned; FLUED further requires the latent to be decodable back into byte spans.
启发把 denoise 放在 latent refinement 上,而不是把 FLUED 变成纯 next-byte 自回归模型。
Motivated placing denoising on latent refinement rather than turning FLUED into a pure next-byte autoregressive model.
启发少量串行 correction head,但 v3.3 当前先保留一阶段接口,避免训练和推理成本过早膨胀。
Inspired a few serial correction heads, though v3.3 keeps a one-stage interface for now to avoid inflating training and inference cost too early.
启发 memory/readout 的控制与 payload 分离:memory 不直接暴露给 backbone,readout 才是外部接口。
Inspired the control/payload split between memory and readout: memory is never exposed directly to the backbone; the readout is the external interface.
启发“本段高清、历史压缩”的长上下文路线;FLUED 把该思想放在 encoder memory,而不是固定 patch。
Inspired the "current segment in high resolution, history compressed" long-context line; FLUED places this idea in the encoder memory rather than fixed patches.
Claims