Skip to content

Audit (6 reachable repos): C/.h vs pure-Zig, Idris2-ABI compliance, raw NIFs, Groove hard/soft, adapter + coprocessor footprint #114

Description

@hyperpolymath

Findings from the deep audit of the 6 session-reachable repos (affinescript, developer-ecosystem, burble, verisimdb, git-reticulator, vcl-ut). Estate-wide (~290) re-run is needed by an agent with full scope.

C / .h vs pure-Zig / Idris2 (git-tracked)

Repo .h/.hpp .c .zig .idr
affinescript 0 0 10 18
developer-ecosystem 5 4 217 336
burble 0 1 15 12
verisimdb 0 0 19 6
git-reticulator 0 0 0 0
vcl-ut 0 0 5 29

C/.h elimination candidates vs designed-C-interop exceptions:

  • burble/src/build/exec/abi_proofs.c — genuine "look closer" candidate.
  • Exceptions (keep): zig-api/generated/abi/zig_api.h (generated C adaptor — by design), czech-file-knife/.../CfkBridge.h (iOS/Swift bridge), rescript-fork *.c/idaptik_ums.h (upstream fork), example include/*.h.

Non-Idris2 ABIs → COMPLIANT

All hand-written ABIs are Idris2. Only 2 generated C headers exist (legit). No .v ABIs.

Raw NIFs (→ #109)

  • verisimdb/elixir-orchestration/lib/verisim/nif_bridge.ex — raw Rustler NIF (HTTP is the safe default; NIF path unsandboxed).
  • burble/.../coprocessor/zig_backend.ex — Zig NIFs, partial SNIF fallback.

Groove → ALL SOFT

No hard-groove anywhere; all usages (burble groove.ex/groove_plug.ex, zig-groove-bridge, zig-api connector discovery) degrade gracefully. Hard-groove would be a new pattern (see adapter issue).

Adapter → exists (extend, don't rebuild). See adapter issue.

Coprocessor footprint (→ #110)

burble = full (SmartBackend, 5 kernel domains); verisimdb = partial (raw NIF); affinescript = needs framework (HIGH); developer-ecosystem/iser-tools/futharkiser = GPU manifest exists (unify). Axiom.jl does not exist yet.


Filed via Claude Code — https://claude.ai/code/session_01JNCDaWMB8NV6nAPrvmTg4w

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bindingsABI, FFI, WASM, and cross-language interop surfacesgovernancePolicy, rulesets, standards, compliance, and their enforcementresearchOpen investigation; the outcome is knowledge, not code

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions