01
Adapter families
The project defines three adapter lanes: ADP1 raw f32 task deltas, ASP1 sparse f32 task deltas, and ALR1 low-rank task deltas. Each exists to update model behavior without shipping an entire replacement .slm artifact.
- ADP1 raw delta
- ASP1 sparse delta
- ALR1 low-rank delta
- Manifest-bound artifacts
02
Rust validation before apply
The browser may fetch and checksum adapter bytes, but Rust remains the authority for semantic validation. validate_adapter_delta checks tensor identity, tokenizer identity, layout checksum, shape compatibility, finite values, sparse bounds, and low-rank dimensions before apply_adapter_delta mutates model state.
- validate before apply
- Reject incompatible packages
- Clear KV cache after success
- Record adapter diagnostics
03
Auto-assembly
Generated roots can declare a receipt-preferred adapter stack. The browser verifies module plans, adapter-family receipts, adapter manifests, artifact byte counts, and stack budgets before Rust validation and application. Generation is authorized only after the declared stack reaches the required state.
- 1 MiB adapter auto-apply budget
- Module-plan phases
- Family receipt verification
- Stack preflight
Portal delivery details
Server rendering: Routes are handled by index.php; content lives in data/pages.php; HTML and Markdown share the same page data.
Dependency boundary: No WordPress bootstrap, database, Composer package, npm build, CDN script, Bootstrap, or jQuery dependency.
Deployment: The package targets the subdomain root with Apache or equivalent clean-route rewriting.