Skip to content

EXPLAINME.adoc

Latest commit

 

History

History
111 lines (82 loc) · 3.37 KB

EXPLAINME.adoc

File metadata and controls

111 lines (82 loc) · 3.37 KB
Raw

empty-linter: Negative-Space Diagnostics — Show Me The Receipts

Table of Contents

The README makes claims. This file backs them up.

It acts as the "Eyes" for agents, enforcing symbolic structural intent over hidden "crap-voids."

— README

How to reproduce every claim

bun test                                   # 152 tests, 525 expectations
bun run scripts/empty-lint-ci.js .         # audit this repo: exit 0
bun run sync:check                         # downstream tables in sync
bun run src/cli/Main.bun.js audit \
  tests/fixtures/ietf-incident/draft-rfc-style.txt

The last command prints three findings at the exact recorded offsets: the incident NBSP (line 9), the semantic ZWJ (line 10), and the zalgo run (line 11). tests/IetfIncident_test.js then walks plan → approve → apply-to-copy → verify over the same file and asserts issue #74’s fixture conditions end to end.

Technology choices

Technology Role (honest)

Bun

The runtime. The expanded engine is plain, reviewed Bun JavaScript with no build step.

AffineScript

Semantic source language of the legacy minimum detector (stdlib/ByteDetector.affine → checked-in reviewed artefact). The expanded catalogue is not yet AffineScript-native (upstream promotion pending).

Nickel subset / JSON

Live configuration (config.ncl), parsed and validated in-repo.

Idris2 ABI

Not currently connected. Template scaffolding was removed for implying verification that did not exist (see PROOF-NEEDS.adoc); domain proofs tied to the active scanner/repair are roadmap M8.

File map

Path What’s there

src/core/

Expanded engine: augmented Unicode catalogue, scalar scanner, renderer, settings, repair state machine, JSON-Schema validator, report emitter

src/containers/

OOXML / XLSX / PDF / hidden-style detectors plus a minimal zip reader

src/cli/

Product CLI (audit · show · plan · approve · apply · verify · tui)

src/tui/

Interactive UI: pure model, renderer, key decoder + thin IO shell

schemas/

Versioned JSON schemas: diagnostic, repair-plan, provenance, rescan

tests/

Bun suite (13 active files); tests/planned/ holds planned-API specs outside the gate

tests/fixtures/ietf-incident/

The originating incident as an executable acceptance fixture

scripts/empty-lint-ci.js

Implemented read-only repository audit (the stable CI gate)

scripts/sync-downstream.js

Regenerates userscript / extension tables from the catalogue; --check

userscript/, vscode-extension/

Downstream surfaces consuming marked, regenerated catalogue regions

adapters/

Composition docs + tested reference consumer for suite repos

.well-known/groove/manifest.json

Groove capability manifest with honest per-capability statuses

What this file does not claim

Computed-style resolution, OCR-image PDF text, an AffineScript-native expanded catalogue, connected Idris proofs, and live third-repo adapters are not implied by anything above. configured, wired, implemented, tested, proved, and deployed remain separate statuses in every claim this repository makes.

Questions?

Open an issue or reach out directly — happy to explain anything in more detail.