.-" "-.
/ πΌ πΌ \
| #000dead |
|, .-. .-. ,|
| )(_o/ \o_)( |
|/ /\ \|
(_ ^^ _)
\__|IIIIII|__/
| \IIIIII/ |
\ /
`--------`
"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)
1. What I Built: Honoring the Code That Built Us πΌπ―οΈ
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.
[!IMPORTANT]
π Live Web Ofrenda: https://git-seance-q032.onrender.com
π¦ Source Repository: https://github.com/FranciscoGrandon/git-seance (Release v1.0.0 Β· 41 Automated Tests Β· 0 AST Violations)
2. The Core Problem: Small Models Love Making Up Tragic Ghost Stories
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.
The Deterministic Tombstone Grounding Pipeline
To make GitSΓ©ance an authentic developer tool rather than a toy, I engineered a multi-stage deterministic safety pipeline:
ββββββββββββββββββββββββββββββ
β git log -p Graveyard Miner β
β (Single-Pass Pipeline) β
βββββββββββββββ¬βββββββββββββββ
β
βββββββββββββββββββββ΄ββββββββββββββββββββ
βΌ βΌ
βββββββββββββββββββββββββββ βββββββββββββββββββββββββββ
β Polyglot AST Symbol β β Cryptic Commit Preflightβ
β Extractor (Py/JS/Go/Rs) β β (wip/cleanup Interceptorβ
ββββββββββββββ¬βββββββββββββ ββββββββββββββ¬βββββββββββββ
β β
β π‘οΈ Is commit cryptic? β
ββββββββββββββββββββ YES ββββββββββββββββΊ π‘οΈ Fallback
β Epitaph
β NO (Informative commit message)
βΌ
βββββββββββββββββββββββββββ
β Local Google Gemma 2B β (Ollama localhost:11434 / temp=0.25)
β SΓ©ance Inference Engine β ($0.00 Cloud Bill / 100% Local Privacy)
ββββββββββββββ¬βββββββββββββ
β
βΌ
βββββββββββββββββββββββββββ
β Grounding Fact-Checker β (Verifies Commit SHA & File Path in reply)
ββββββββββββββ¬βββββββββββββ
β
βΌ
ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
β Sentry Agent Tracing (`ai.seance` OpenTelemetry Spans) β
β β’ Latency (ms) β’ Token Count β’ Hallucination Flags β
ββββββββββββββββββββββββββββββ¬ββββββββββββββββββββββββββββ
β
βββββββββββββββββ΄ββββββββββββββββ
βΌ βΌ
βββββββββββββββββββββββββββ βββββββββββββββββββββββββββ
β Terminal CLI Ofrenda β β Single-Page App Ofrenda β
β + Quine (#000dead) β β (Render / index.html) β
βββββββββββββββββββββββββββ βββββββββββββββββββββββββββ
-
Streaming Single-Pass Git Miner (
mine_git_graveyard): Most mining scripts spawn hundreds of slowgit showsubprocesses. GitSΓ©ance streamsgit log -p -U0in a single pass with delimited token buffers, reconstructing author, timestamp, commit SHA, and exact unified diff deletions in under 120ms. -
Pre-Flight Cryptic Interceptor (
is_cryptic_commit): Before burning CPU or GPU cycles on an LLM, the commit message is audited against low-signal patterns (wip,temp,cleanup,fix,chore(core): wip). If flagged, GitSΓ©ance short-circuits inference completely and delivers an honest, unvarnished epitaph: > "This function departed into the void under the cover of a cryptic commit ('wip'). No heroic epitaph can be summoned because the mortal developer left no breadcrumbs." -
Low-Temperature Bounded Prompting (
temperature=0.25): The model is instructed to adopt the persona of the departed function speaking in the first person, bounded strictly to the verified diff lines and commit message. -
Post-Generation SHA Fact-Checker (
verify_response_grounding): Python regex audits the response to certify it explicitly includes the actual 7-character commit SHA prefix (e.g.,#8f3a91c) and the file path. If the spirit fails the audit, it is evicted in favor of verified deterministic text.
Real-World Proof: How gemma2:2b Hallucinated Before Our Guardrail
To test why deterministic grounding is mandatory for small open-weight models, I ran gemma2:2b across 25 historical deleted functions (17 with descriptive commit messages and 8 with rushed messages like "wip cleanup" or "fix"):
β Without GitSΓ©ance Guardrail (Raw gemma2:2b at default temp=0.8 on commit #c209e4b "wip cleanup"):
"I was
heuristic_fraud_score_v0, removed during the Q3 migration to a distributed Stripe Radar microservice because my synchronous database queries caused p99 latency spikes."
(100% fabricated β neither Stripe Radar nor database queries existed in the diff!)
β
With GitSΓ©ance Pipeline (is_cryptic_commit + temp=0.25 + verify_response_grounding):
"π―οΈ My creator (Devon K.) erased me in commit
#c209e4binsidesrc/risk/scoring_v0.pyon 2026-09-29, leaving only the cryptic epitaph'wip cleanup'. Because GitSΓ©ance enforces strict anti-hallucination grounding, I refuse to fabricate a fake business story for my removal. All that survives in my tombstone diff is that I computedheuristic_fraud_score_v0(ip_addr, cart_total)."
| Pipeline Configuration | Hallucination Rate on Cryptic Commits (n=8) |
Exact SHA + File Citation Rate (n=25) |
Median Local Latency (p50) |
Cloud API Cost |
|---|---|---|---|---|
Raw gemma2:2b (temp=0.8) |
87.5% (7 / 8 invented fake reasons) | 64.0% (16 / 25 cited SHA) | 640 ms | $0.00 |
GitSΓ©ance Grounded Pipeline (temp=0.25 + Guardrail) |
0.0% (8 / 8 intercepted pre-flight) | 100.0% (25 / 25 verified by regex) | 488 ms (0.02 ms on pre-flight blocks) | $0.00 |
2.5 Live Visual Walkthrough πΈ
To give judges and developers full transparency into how GitSΓ©ance behaves in production, here is the live visual evidence across our interactive altar, telemetry layer, and CLI:
1. Interactive Digital Ofrenda & Awakened Quine Relic (#000dead)

Figure 1: The interactive altar with cempasΓΊchil marigold rain, candle-lit departed functions, and the unlocked #000dead MictlΓ‘n source quine verifying real-time FNV-1a DOM parity.
2. Sentry Agent Tracing Telemetry & Anti-Hallucination Guardrail

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).
3. Local Terminal CLI SΓ©ance & MictlΓ‘n Relic Introspection

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.
3. The Interactive Wow Factor: Audio Chimes, Falling Petals & The Self-Aware AST Quine πβ¨
Software should evoke wonder. The Digital Ofrenda web app is packed with three organic technical easter eggs:
1. The Self-Aware Source Code Quine (#000dead)
GitSΓ©ance contains a living mythological spirit embedded directly into the source code: Spirit #000dead (The Relic of MictlΓ‘n).
-
In Python CLI: Running
python git_seance.py --mictlandynamically introspects its own source code on disk using Python'sastmodule. It extracts the hex cipherMICTLAN_HEX_CIPHER, decodes it in memory, calculates its own 32-bit FNV-1a checksum (0x71790691), and summons itself as a living departed relic. -
In the Web App: Typing
mictlananywhere on the keyboard or clicking the golden calavera skull executesawakenSourceQuineSpirit(), reading<script id="gitSeanceCoreScript">, verifying identical FNV-1a hash parity, and displaying the live self-reflection panel.
2. Zero-Asset Resonant Altar Bells (Web Audio API)
No bulky .mp3 files or external audio assets. The altar bell chimes are synthesized directly in the browser using the Web Audio API:
const notes = [293.66, 349.23, 440.0, 587.33]; // D minor harmonic arpeggio (La Bruja motif)
notes.forEach((freq, idx) => {
setTimeout(() => playAltarChime(freq), idx * 140);
});
Each note triggers an OscillatorNode with an exponential decay GainNode, producing an authentic, haunting bronze bell timbre.
3. Marigold Petal Rain (Canvas Physics)
Activating the altar triggers an interactive HTML5 canvas particle storm where 38 golden cempasΓΊchil and purple petals drift and rotate down the viewport with realistic harmonic sway (Math.sin(angle) * 0.4).
4. Why Open Innovation Matters Here π
- Zero Proprietary Data Leaks: No engineering organization will ever upload their internal git logs, deleted security patches, or proprietary business logic to third-party cloud APIs just to analyze tech debt. Running Google Gemma locally guarantees 100% air-gapped privacy.
- Permanent Immortality ($0.00 Per SΓ©ance): Cloud APIs deprecate, rotate tokens, and charge per 1,000 tokens. GitSΓ©ance runs on standard git plumbing and open weights. You can run this tool in an underground bunker twenty years from now with zero internet connection.
5. Automated Pull Request Ofrenda: GitHub Actions CI/CD π€
Whenever a developer opens a Pull Request that excises dead code, GitSΓ©ance runs automatically via .github/workflows/ofrenda_pr.yml:
python3 git_seance.py --ci-summary --no-fallback --range "origin/${{ github.base_ref }}..HEAD" > ofrenda_comment.md
It automatically posts an elegant Digital Ofrenda memorial comment to the PR discussion thread with collapsible <details> blocks for diff inspection:
| Departed Symbol | File Path | Tombstone SHA | Author & Date | Guardrail Status |
|---|---|---|---|---|
legacy_payment_retry_loop() |
src/billing/checkout.py |
#8f3a91c |
Devon Vance (2026-10-14) | β Grounded Epitaph |
sync_legacy_cart_v1() |
src/checkout/cart_sync.py |
#d4e91b2 |
Marco Ruiz (2026-10-21) | π‘οΈ Cryptic Commit (vague_commit blocked) |
6. Sentry Agent Tracing Telemetry: What I Found & How I Debugged It π
Every sΓ©ance transaction is instrumented with custom OpenTelemetry spans under the ai.seance namespace using sentry-sdk (traces_sample_rate=1.0):
-
Tracked Tags:
death_sha,engine_source(gemma_localvsdeterministic_guard),grounded_sha,cryptic_commit_blocked, andast_quine_verified. -
Tracked Measurements: Execution latency (
latency_ms), generated token count (tokens_generated), and prompt context byte size.
Bug Caught via Sentry Tracing During Development
While inspecting my early ai.seance traces in Sentry, I noticed two critical anomalies:
-
Unnecessary 600ms+ LLM Calls on
"wip"Commits: Initially, I was sending cryptic commits ("wip cleanup") togemma2:2band trying to stop hallucinations via system prompt alone. The Sentry spans showed we were burning ~610ms and ~75 tokens per cryptic commit while still failing thegrounded_sharegex check 25% of the time. Movingis_cryptic_commitinto a pre-flight interceptor before Ollama dropped cryptic-commit latency from 610ms to 0.02ms and reduced hallucinations to 0%. -
SHA Truncation Mismatch: Sentry tags revealed
grounded_sha: Falseon valid responses becausegit logemitted 7-character short SHAs (#8f3a91c) while Gemma occasionally formatted them without the#prefix. Updatingverify_response_grounding()to normalize hex SHA prefixes fixed the false rejections immediately.
[
{
"trace_id": "trx-2deb23",
"operation": "ai.seance.quine",
"symbol_name": "__mictlan_source_quine__",
"death_sha": "000dead",
"model": "gemma2:2b",
"latency_ms": 22.75,
"tokens_generated": 66,
"cites_sha": true,
"cites_file": true,
"cryptic_commit_blocked": false,
"ast_quine_verified": true,
"timestamp": "2026-10-28T03:23:50Z"
},
{
"trace_id": "trx-e81627",
"operation": "ai.seance",
"symbol_name": "heuristic_fraud_score_v0",
"death_sha": "c209e4b",
"model": "gemma2:2b",
"latency_ms": 0.02,
"tokens_generated": 58,
"cites_sha": true,
"cites_file": true,
"cryptic_commit_blocked": true,
"ast_quine_verified": false,
"timestamp": "2026-10-28T03:23:50Z"
}
]
7. Prize Categories Entered π
This project genuinely integrates and enters the following partner categories:
-
Overall Winner ($250 + DEV++): Bridges Halloween and DΓa de los Muertos to solve real-world software archaeology (
git log --diff-filter=D) with local open-weight AI, a deterministic anti-hallucination guardrail, a self-inspecting AST Quine (#000dead), and a 41-test automated verification suite. -
Best Use of Gemma ($200): Uses Google's open-weight
gemma2:2bmodel locally via Ollama (http://localhost:11434/api/generate) attemperature=0.25to channel deleted functions in first person while keeping proprietary git history 100% offline. -
Best Use of Render ($200): Hosts the zero-dependency interactive Digital Ofrenda Web App via a declarative Render Blueprint (
render.yaml), allowing anyone to summon departed spirits, trigger the#000deadsource quine, and inspect telemetry in the browser.
# render.yaml (Declarative Infrastructure as Code)
services:
- type: web
name: git-seance
runtime: static
buildCommand: ""
staticPublishPath: .
routes:
- type: rewrite
source: /*
destination: /index.html
headers:
- path: /*
name: Cache-Control
value: no-cache
-
Best Use of Sentry Agent Tracing ($100): Instruments every
ai.seanceandai.seance.quinespan with custom tags (death_sha,grounded_sha,cryptic_commit_blocked) and latency/token metrics, which directly uncovered our cryptic-commit latency bottleneck during debugging. -
Best Use of GitHub Copilot ($100): Built with GitHub Copilot CLI for polyglot regex/AST symbol extraction and paired with an automated GitHub Actions workflow (
.github/workflows/ofrenda_pr.yml) that posts a Digital Ofrenda memorial table whenever a Pull Request deletes legacy functions. -
Best Use of Entire ($100): Documents the transparent agentic coding sessions behind GitSΓ©ance v1.0.1βsharing the exact autonomous agent logs, deterministic AST refactoring trajectory, latency bottleneck diagnostics (reducing cryptic commit response from ~610ms down to 0.02ms), and continuous SHA-256 integrity verification recorded in
CHANGELOG.md.
8. Engineering Rigor: 41 Automated Tests & 0 AST Violations π§ͺ
GitSΓ©ance was tested with the same rigor required of production infrastructure:
# Run the complete test suite
python -m unittest discover -v
Ran 41 tests in 8.132s
OK
-
test_git_seance.py(24 tests): Single-pass mining, unified diff chunk parsing with mixed indentation, polyglot symbol extraction, cryptic commit pre-flights, grounding verification edge cases, local HTTP Ollama mock server, and AST quine self-introspection. -
test_html_ofrenda.py(17 tests): DOM element consistency (0 null pointer risks), cross-language FNV-1a parity, XSS HTML entity escaping, and live headless browser DOM verification using headless Microsoft Edge (msedge --headless --dump-dom). -
AST Static Linting: 0 violations under
<30msexecution via AST linting.
9. Try It on Your Own Graveyard! π
Don't let your deleted code wander the void forgotten. Summon your repository's ghosts today:
# 1. Clone the repository
git clone https://github.com/FranciscoGrandon/git-seance.git
cd git-seance
# 2. Make sure you have Ollama running with Gemma
ollama pull gemma2:2b
# 3. Hold your first sΓ©ance (works on ANY git repository!)
python git_seance.py
# 4. Or awaken the secret source code Quine
python git_seance.py --mictlan
Prefer a visual experience? Visit the live altar at https://git-seance-q032.onrender.com, light a candle for legacy code, and type mictlan on your keyboard!
Built with reverence by **Francisco GrandΓ³n Vergara* for Hacktoberfest 2026: Week 4 ("Ghost in the Machine"). Viva Open Source! πΌπ*
Top comments (0)