glm-5.3-flash
9888922ff6
Answers for the four sect 5 questions: minimal human-only authenticated surface (console-vs-server-side stays open for requirements.md), archive downloads with a named trigger, per-identity email over the alk.dev catch-all as a stated transparency requirement, and an admin-action audit trail accepted as family-posture material
alkforge
The alk family's near-term assembly: a minimal forge replacing the
gitea deployment, built as an assembly on alkgit's core (family
ADR-002, /workspace/@alkdev/alkfamily/docs/architecture/decisions/002-alkforge-gitea-replacement.md).
It composes family crates rather than re-implementing them: alkgit (+ alkgit-substrate) as the git core, alkssh (git feature) and alkhttp as the transport doors, alkgen for server-side rendering, alkstore and alkblobs for persistence, alkvault for secrets, and alkcall as the substrate underneath. reverse-proxy fronts the deployment.
Status: SDD phase 0 (research docs only). See
docs/research/phase-0.md and the family docs for the current design
direction. The README proper gets written when the crate is near
publish (v0.1.0).
License: MIT OR Apache-2.0.