网页
综合
更新时间 2026-10-28 10:31:30
GitSéance: An Offline Digital Ofrenda Where Local Gemma Summons Deleted Code (And Refuses to Guess Why It Died) - DEV Community
自动蜘蛛
dev.to
正文约 5999 字
Posted on Oct 28 • Edited on Oct 29 • Originally published at git-seance-q032.onrender.com
Hacktoberfest Open-Source AI Challenge: Ghost in the Machine Submission 👻🌼
This is a submission for the Hacktoberfest Open-Source AI Challenge Week 4: Ghost in the Machine
"The code you delete never truly dies: it becomes the silent foundation of every commit that follows. Viva Open Source!" — Spirit #000dead (Mictlán Relic)
git blame only speaks for the living.
It tells you who touched the lines that survived in HEAD—but every mature repository is built on the bones of hundreds of excised functions, retired prototypes, and emergency midnight bugfixes that were quietly erased from history.
When a regression resurfaces two years later, modern teams often commit the exact same architectural mistakes of 2022. Why? Because the reasoning behind deleted code is buried deep inside git log -p, where nobody looks.
For Hacktoberfest 2026: Week 4 ("Ghost in the Machine"), bridging Halloween with the sacred Mesoamerican tradition of Día de los Muertos (Day of the Dead), I created GitSéance:
An offline-first developer archaeologist and interactive Digital Ofrenda that scans your repository's graveyard, builds a marigold-adorned altar for departed code, and lets you conduct grounded séances with excised functions powered by Google Gemma (gemma2:2b) running 100% locally on your own machine.
🌐 Live Interactive 3D Web Ofrenda: https://git-seance-q032.onrender.com (Deployed on Render with zero cold starts, offline client-side Ollama bridge, and instant fallback mode).
Figure 1: The interactive altar with real-time 3D Three.js volcanic tiers, 1,200 instanced cempasúchil marigolds, 4 CRT holographic monitors, glowing neon data cables, and the unlocked #000dead Mictlán relic verifying real-time FNV-1a DOM attestation.
Figure 1b: Dedicated close-up of the Three.js r128 procedural altar: 4 CRT holographic terminals (amber, matrix green, cyan, magenta) with scanlines and blinking cursors, pulsating neon cables, and 1:10 cirios scale.
Figure 2: Real-time telemetry dashboard monitoring ai.seance spans, Chart.js latency and token distributions, and pre-flight interception of vague commits (0.02ms latency, 0 hallucinations).
Figure 2b: Production transaction trace in live Sentry.io dashboard (summon_legacy_payment_retry_loop span ai.seance) validating real-time telemetry, tag attributes (death_sha, engine_source, grounded_sha), and sub-millisecond execution.
Figure 3: Running python git_seance.py --mictlan in the terminal, decoding the embedded hex cipher, inspecting 38KB of AST nodes, and channeling departed spirits with zero network calls.
"The code you delete never truly dies: it becomes the silent foundation of every commit that follows. Viva Open Source!" — Spirit #000dead (Mictlán Relic)
Creado por Francisco Grandón Vergara
🌐 Live Web Ofrenda (Render): https://git-seance-q032.onrender.com 📰 Official DEV.to Submission: GitSéance: An Offline Digital Ofrenda Where Local Gemma Summons Deleted Code 📦 Source Repository: https://github.com/FranciscoGrandon/git-seance (Release v1.1.0 · 47 Automated Tests · 0 AST Violations)
📦 Official Repository & Release: FranciscoGrandon/git-seance (Release v1.1.0) 🧪 Quality Gate: 49 Automated Unit Tests (Ran 49 tests in 29.4s OK) · 0 AST Violations · Full Python 3.10 / 3.11 / 3.12 CI/CD Matrix
When I first fed deleted git diffs into local 2B language models and asked, "Why was this function removed?", Gemma did what small language models do best: it hallucinated.
If a commit message was informative—such as "Drop parse_xml_invoice_soap to patch XXE vulnerability (CVE-2026-0412)"—Gemma recited a magnificent, respectful memorial.
But what happened when the commit was a Friday 4:59 PM rush job that literally said "wip" or "cleanup"? The model immediately fabricated an elaborate, fictional backstory about microservice migrations, imaginary database locks, or phantom compliance audits!
In software archaeology, a fictional story is worse than silence.
To make GitSéance an authentic developer tool rather than a toy, I engineered a multi-stage deterministic safety pipeline:
GitSéance executes 100% on the Python Standard Library by default (Air-Gapped Mode with zero third-party dependencies required). For production environments and observability, it includes an optional adapter for Sentry (sentry-sdk 2.x) that activates when SENTRY_DSN is configured.
Every séance transaction is instrumented with custom OpenTelemetry spans under the ai.seance namespace:
Initially, I was sending cryptic commits ("wip cleanup") directly to gemma2:2b and attempting to curb hallucinations via system prompt alone. Sentry span data revealed that we were burning ~610ms and ~75 tokens per cryptic commit while still failing referential grounding 25% of the time. Moving is_cryptic_commit into a deterministic pre-flight interceptor dropped cryptic-commit latency from 610ms to 0.02ms and reduced hallucinations to 0%.
GitSéance is deployed on Render as a Python Web Service via a declarative Infrastructure-as-Code Blueprint (render.yaml):
GitSéance was engineered through a disciplined pair-programming workflow combining developer vision with autonomous agentic tools:
Software engineering often treats deleted code as trash—something to discard with git commit -m "cleanup" and forget.
But code is human intention crystallized in logic. Every excised helper function was once someone's late-night breakthrough, someone's urgent fix that kept production alive, or an architectural hypothesis that taught the team what not to build.
By fusing the technological ghost in our version control systems with the sacred Mesoamerican tradition of Día de los Muertos, GitSéance shifts the developer mindset from reckless refactoring to respectful archaeology:
When you light a virtual candle for an excised function, listen to the bronze altar chimes, and watch the marigold petals drift over the code that came before you, you realize: our current systems
本页为82搜索生成的网页快照,内容来自站内索引;演示数据的原文链接仅作示例。