dev: repos overview (local)
A repo-level view (not crate-level): “what interacts with what”, plus recent activity and rough disk footprint.
Summary
How to read this page (definitions)
- repo graph: hand-curated “who depends on who” at the repository level. Solid edges are default; dotted edges are feature-gated / optional.
- crate graph (actual): what Cargo sees for the dev super-workspace snapshot (also uses dotted for “optional”).
- crate graph (conceptual): the intended Tekne layering (a small, human-checked set).
- dev overrides: Cargo [patch] rules that redirect git deps to local checkouts for development.
- “where to confirm”: clickable pointers to the relevant Cargo.toml or feature flag; it’s a starting point for reading, not proof.
At a glance (what each layer is for)
crate level one-line local docs
This is intentionally short: “what it is for” + where to read next.
Performance & Scaling (Jan 2026 Optimizations)
Task Baseline Optimized Speedup Note
Measured on local hardware. Sparse refers to matrix-free paths; Optimized refers to BLAS/SIMD-accelerated paths.
Conceptual Clusters (overlapping views)
The Tekne ecosystem is not a strict partition. Crates can belong to multiple clusters.
Tekne Facade / User-facing Math Core Foundational logic Incubation Experimental Orchestration Apps/Services

      
Conceptual Clusters (from tekne-stack.mdc)
cluster purpose members
Tekne (Facade) User-facing stdlib jin, innr, cerno, anno, slabs, lattix, strata, hyp, subsume
Math Core Foundational math/logic innr, logp, wass, lapl, rkhs, rmt, fynch, cnk, sbits, ans
Incubation New/experimental clump, kuji, pare, knit, skel
Orchestration Services & Apps hop, bop, axum-mcp
Repo interaction graph, grouped by levels (hand-curated)
Legend: solid = used by default / always-on, dotted = optional / feature-gated. Dev wiring via /Users/arc/Documents/dev/Cargo.toml is assumed (not drawn as a node).

          
Edges here are “integration edges” (git deps, patch overrides, or “built together as a super-workspace”), not every internal module call.
Edge explanations (why an arrow exists)
from to kind why where to confirm
“where to confirm” points at the most relevant manifest / feature flag. It’s not proof; it’s a place to start reading.
Recently touched repos (git `.git/` mtime snapshot)
repo level git mtime size (rough) notes
“size (rough)” is from a `dust -d 2` run for a few large repos; missing entries are intentionally left blank.
tokei + activity (last 60d)
view core excludes large artifact dirs (hover) excludes
repo level LOC (code) top langs commits/day files touched/day lines changed/day last commit
Source: tokei -o json and git log --since=60.days. Sparklines are normalized per-repo.
Dev overrides (where “patches to local” currently exist)
repo mechanism notes
This is shown as a table (not as edges) to keep the main graph readable.
Crate-level graphs (workspace snapshot)
This section is about the Rust workspace view (what Cargo sees) vs a small conceptual edge set (what the Tekne stack implies).
Actual Cargo workspace edges (what the compiler sees)

        
Conceptual Tekne stack edges (small, hand-curated)

        
Mismatch report (conceptual vs actual)
edge conceptual actual note
If you want “conceptual” edges to become “actual”, that’s a Cargo dependency choice.
tekne facade: features ↔ crates (summary)
feature crate re-export in dev workspace? level
Validation breadcrumb (from prior run)
- run_at: 2026-01-15T12:20:09Z - commands: just validate, just validate-strict - raw output saved at: /Users/arc/.cursor/projects/Users-arc-Documents-dev/agent-tools/87904aa6-5cea-45f4-89ee-bb6730a9729d.txt