- behavior-only walk of git.alk.dev (gitea 28.3.0): findings in docs/research/deployment-walk.md - headline: forge is a git host + public landing page only (issues/ PRs/wiki/releases/LFS/CI all zero-usage inertia); whole-org anonymous read is the operative grant; single-branch direct-push model by per-agent accounts; tags are the release surface - phase-0.md: sect 3 filled with summary + link, OQ-FG-01 resolved with residues, asks list gains the verified web-browse-queries item, POC item 1 marked done, checklist item checked
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.