glm-5.3-flash
92519fa0c9
- add sect 11 correction lenses: three meanings of zero usage, residue-vs-workflow (branches are core SDD scaffolding, stale branches are cleanup debris), no incumbent surface-shape inheritance (alkcall ACL model, not gitea's anonymous OpenAPI), workarounds are unmet-need signals, the primary user (the SDD workflow) is invisible to telemetry; 0.1 = day-to-day replication, gitea catalog is a selective long-term backlog - re-bucket: branching load-bearing (was inertia residue); stale branches deferred as per-branch migration decisions - new finding (owner-stated): push-mirrors to GitHub for all public OSS repos, currently half-implemented with a plaintext PAT on gitea; alkforge posture = alkvault reference + assembly-layer bearer injection (alkhttp precedent); migration step added (enumerate + rotate, never copy); new OQ-FG-11 seeds the 0.1 scope question - clarify why issues/PRs/wiki/CI were unused: in-session workflows and distrust of gitea, not no-need-forever
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.