Second steer from the 2026-11-06 discussion: the document-vs-code
split carries a false distinction. The core is contexts + templates +
partials to text; HTML, Rust, and WGSL are three data points of the
same shape (handlebars native case, reader POC, alkminer kernel
builder). Per-target residue is only the template set, context shape,
emit posture, and validity pinning. WGSL recorded as confirmed coming
(JS runtime needs codegen generating WGSL); AGENTS.md lifecycle
phrasing aligned.
Principal steer: generalize the shared core across HTML generation
(branch 0), Rust codecs (branch 1), and WGSL/wasm-JIT (branch 3
territory); dev-tool emit demoted from the crate's definition to one
projection. Records the core/per-target split and the render-purity
requirement the wasm JIT fixes for Phase 1; refines OQ-GN-09.
- AGENTS.md: adopt alkssh conventions (conventional commits, small
focused commits, taskgraph section, lifecycle status, verification
grep gate); add convention 12 (no em dashes in prose, U+2014)
- README.md: note the unpaused status and the alkforge SSR consumer
- phase-0.md: alkforge SSR enters as branch 0 (in-library HTML
rendering, two target classes bound the core generality), new
OQ-GN-09 for the SSR library posture, unpause context section,
alktype 0.4.0 revalidation notes
- reader-poc-summary.md: re-validation note for alktype 0.4.0
(parity + bench unchanged); em dashes restructured repo-wide
- (b) direct codecs resolved AND validated: generated types+codecs,
ReadResult<Packet>, no serde/serde_json/alktype in output
- benchmark: ~10x faster than Value-shaped generated, ~15-20x faster
than interpreter, ~4x off raw no-alloc baseline (String/Vec allocs)
- F-6: names come from the BAST doc (plan erases $defs names);
OQ-GN-02 refined: plan for semantics, BAST for names
- V{key} variant naming for numeric discriminator keys
- clarification: alkcall is a library others build on; alkgen branches
1+2 are a dev tool generating static files into downstream projects
(protocol crates alktty/alktunnels/sftp, cloud integrations vast.ai/
runpod) from provided schemas (BAST or jsonschema/openapi)
- OQ-GN-01 resolved: module-level output for v1; fragments out
(defeats dev-tool purpose), crate generation out for v1 (composed
from modules later if asked). Residue: file partitioning policy
- OQ-GN-06 reframed: generated files land in projects that don't
depend on alktype today, so dependency footprint is consumer's
choice, not wire-shaped; leaning self-contained, POC decides
- branch 2 reframed: static counterpart of alkhttp from_* adapters
- plans for offsets/sizes (already computed+validated by the engine,
free at generation time since alktype is already a dep), BAST for
descriptive metadata; drift risk inverts into ordinary
dependency-upgrade tracking of alktype's plan API
- residue: exact plan->context projection is the Phase 1 context-
builder spec task
- OQ-GN-03 resolved as posture: interpreter/compiler duplication is
the point (dynamic vs static deployment profiles); alktype near
schema-method floor, ~20x off hand-rolled; alkgen's value prop is
recovering most of that gap. Drift stays the standing risk.
- OQ-GN-08 POC 1 calibration: three-way benchmark (plan-walk vs
generated vs hand-rolled) doubles as drift check + perf validation;
OQ-GN-05 boundary reframed as performance trade
glm-5.3-flash