Research Archive

ZJX 1.25.1 NIGHTMARKET ships two explicit packing objectives. Under a frozen four-corpus clean-lab campaign, fast packed in about 36 percent of compact's wall time with zero size penalty, while the quickest schedule was rejected for making restores slower. The rejected-schedule analysis, measurement-law repairs, and clean-lab doctrine require an unlock.

ZJX 1.24 GHOSTLANE won four of four paired comparisons with a 22.35% median improvement, then failed repository-wide validation and was not released. The failure analysis and release doctrine require an unlock.

ZJX 1.23 BLACKWIRE establishes native canonical binaries, clean-host operation, exact archive identity, and one qualified production boundary. The invalid-campaign analysis, harness repairs, and transferable release doctrine require an unlock.

ZJX 1.22 NULLSPOOL preserved archive correctness but failed end-to-end wall-time and CPU qualification, so it was rejected and not shipped. Exact figures, diagnosis, and lessons require an unlock.

ZJX 1.21 STREAMWALL delivers bounded-memory archive operation - reducing Silesia peak memory from 8.58 GB to 390 MB while preserving deterministic output, exact restoration, and compatible archive bytes.

PCAM v3 advances to a Normative Candidate by replacing phase-only authority with complete action-machine state, logical ticks, explicit release gates, and zero conformance claims.

Sley 1.2.0 keeps Greyforge's human-readable 1.x line open while current research attention turns toward the machine-native Sley 2.x thesis.

Sley 1.2.0 moves Greyforge's self-hosted structural programming language to a public release-candidate boundary with expanded proof, Linux x86_64 artifacts, and explicit production limits.

How ZJX moved beyond ratio claims toward an archive lifecycle built on validated bundles, dependency readiness, no-write restore planning, lower-memory routing, and fail-closed decoder behavior.

How Sley evolved into a bounded review surface where staged bytes, read-only tool access, report-only semantic comparison, and human authority remain separate decisions.

How ZJX turns compression claims into evidence: selected verifier-checked size wins including review-gated 160 MB JSONL, 256 MB sharded NDJSON, and 1.1 GB compact JSONL validation bundles with a scoped no-zpaq follow-up, local telemetry rows up to 1.25 GB, review-gated evidence records, validation checks, and strict claim boundaries.

How Sley, an agent-native structural programming language, and ZJX, an evidence-first lossless archive prototype, work together to reduce repeated context, speed developer workflows, and make code change more reliable.

The premium operator edition on turning open source ideas into gated repositories, release evidence, public proof, and disciplined multi-repo execution.

How Greyforge turned open source releases from scattered repo chores into a gated release engine with audits, scrub passes, and publish discipline.

Why Greyforge released service-cartographer, a read-only OpenForge utility for mapping local services, cron jobs, wrappers, repositories, and env-file metadata before cleanup begins.

A practical release pattern for preventing repeat-triggered automation bursts by enforcing per-key cooldown windows in a SQLite-tracked policy engine.

Why Greyforge Labs built sqlite-checkpoint - a zero-dependency Python tool that wraps SQLite's WAL checkpoint and online backup APIs into a single safe command.

Why Greyforge Labs released memory-quality-gate, a zero-LLM heuristic filter that scores candidate memories before they hit long-term storage.

Why Greyforge Labs built devcap - a zero-dependency Python CLI that audits 100+ tools across 14 categories with parallel scanning and structured output.

How Greyforge Labs engineered a real-time full duplex voice operations pipeline, validated by adversarial pre-build research and ready for open source release.

How we built a 162-line Node.js bridge that turns Telegram into a remote terminal for Google Gemini CLI, with streaming, queued access, and an open-source release.

Technical architecture chronicle of the ForgeQuant constraint protocol - how six independent evaluation gates produce deterministic, auditable equity signals.

Historical record of an early automated generation and deployment pipeline for WebForge Chronicles.