Reference
Read current state.
Freeze a declared fact and its source/evidence path.
Hack Hydra 2026 · static judge fallback
See what changed. Trace why.
This static artifact mirrors the live judge narrative when a live service is unavailable. It preserves the golden path, executed Track 03 result, model boundaries, cryptographic status, citations and licensing without pretending HydraDB controls are active inside the static page.
STATIC_PRESENTATION_ONLY · no live HydraDB mutation · no local-model inference in this document.
01 / GOLDEN PATH
Reference → poison → antidote.
Gold identifies the prescribed judge path. Scientific state semantics remain separate.
Poison
Introduce conflict.
Retain the predecessor while adding explicit contradiction/supersession relationships.
Antidote
Restore without erasing.
Represent recovery as a successor while counterevidence remains traversable.
02 / EXECUTED TRACK 03 RESULT
The graph ran. The tested retrieval advantage did not appear.
The completed LongMemEval-S full500 K=5 retrieval ablation did not establish a positive B/C/D Hit@5 signal relative to route A. HydraDG retains that null/negative result.
Cases500
Sessions23,867
Facts3,506
Entities4,776
MODEL=NONE · extractor=heuristic · model=null · ollarma_url=null
Claim ceiling: LONGMEMEVAL_FULL500_RETRIEVAL_ABLATION_ONLY_NOT_END_TO_END_QA
03 / MODELS USED
Deterministic core first. Local analyst second.
Primary experiment
No LLM
Track 03 full500 K=5 used the heuristic extractor. No frontier API is required to reproduce that submitted result.
Local open-weight diagnostics
Qwen 2.5 7B family
qwen2.5:7b and qwen2.5-coder:7b are bounded local analyst references after deterministic freeze. Their outputs are probabilistic.
Frontier comparison
Not controlled / not run
No local-vs-frontier superiority claim is established. Synthetic design matrices do not become execution evidence.
04 / CRYPTOGRAPHIC CUSTODY
SHA-256 identity is present. HydraDG project signing is pending.
Current project
NOT PROJECT-SIGNED
Current FCO/FCG objects use SHA-256 identity. No admitted detached Ed25519 signature receipt seals every current HydraDG project object.
Private key
External secret
Never ship an authentic private key in Git, HydraDB, browser code, HTML, CSS, environment variables or image pixels.
Signed publication lineage
FCO publication v1
Publication FCG public-key fingerprint:
f496a067808026d45fbbad785bf83c6acd66429c2d257d246cc103c6d7ff460d
Scope: publication FCG, not automatic HydraDG project signing.
05 / TRACK LENSES
One custody spine. Three graph problems.
Track 01
Enterprise identity + ontology
Core data is downloaded/hashed; real ontology ingestion/evaluation remains pending.
Track 02
Dependency blast radius
Synthetic structural canary remains bounded; real npm snapshot evaluation remains pending.
Track 03 · primary
Memory + context retrieval
500-case full500 run executed; null/negative retrieval outcome retained.
06 / EVIDENCE
Every unfamiliar object should resolve backward.
01Term / hash
02FCO
03FCG edge
04Source
05Claim ceiling
Executed Track 03 identities
HydraDB pin: 6a2fbb192f37f51a93690a2ae2d2f5e27e6e4219
LongMemEval source SHA-256: d6f21ea9d60a0d56f34a05b609c79c88a451d2ae03597821ea3d5a9678c3a442
result SHA-256: bdecb4b62cf90040c7f346d283efe78459825b427557cec8d4998f3499ee0324
statistics SHA-256: 8dcf57f5ac60418d16d3c945ad678b4d17b557b9425fededbd6684add7cff7cc
receipt identity: 21a29046de961e252372d06fd85d98db767b900982f90421cc720dfb85069365