glm-5.3-flash
ab87d53751
- survey the 28.3.0 gitea feature catalog schema-derived from the sqlite snapshot plus a read-only production-db pass; 117 tables grouped into 26 feature areas with draft dispositions anchored to workflows, user classes, and ADR-002 (no observed-usage bias) - record production-db ground truth the walk lacked: zero 2FA, zero real OAuth apps, one unverified GPG key, and the exact ten-repo push-mirror roster (a direct OQ-FG-07 migration input) - re-anchor the phase 0 requirements work: requirements derive from a vision plus workflows, user classes, and ADRs with zero version-based hedging; the walk and survey are sizing/validation inputs, never the requirements source - fix the walk-rule vocabulary: every disposition lands at a named roadmap milestone or is explicitly rejected; 'deferred without a named home' removed - rewrite the convergence checklist into session-sized line items (vision.md, requirements.md, roadmap/feature map, 0.1 as milestone 1, then the existing downstream items) Verification: em-dash grep clean across AGENTS.md scope; docs-only change (no Cargo manifest in the repo yet, cargo set not applicable)
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.