Skip to main content
← /blacklight

Documentation

Architecture decisions, design specs, and the pivot moments that shaped how blacklight builds. Authored alongside the source, every claim grep-cites a file in the repo.

Milestone vernacular

M13 / M14 / M15 / M16 / Path C — decoded once

expand
M13 · Path C / Skills realignment
Day 5 (2026-04-25). Retired the flat bl-skills read_only memory store and moved skill content onto the Anthropic Skills primitive (description-routed) plus eight reference Files mounted at session create. Older docs that name bl-skills predate this.
M14 · Substrate-hook (LMD trigger)
Day 6 morning (2026-04-26). Closed-loop response: LMD post_scan_hook adapter, the bl trigger verb, vendored alert_lib + tlog_lib, cPanel Stage 4 ModSec userdata, unattended-mode tier gate. Closed with the v0.4.0 version bump.
M15 · Live-API correctness
Day 6 afternoon (2026-04-26). Eight phases of drift remediation against the live Anthropic API: archive-not-delete retire verb, POST-with-CAS agent updates (not PATCH), sessions.create field rename agent_id → agent, environments body shape correction. v0.5.0 stamps on this.
M16 · Collectors + bridge + adapter
Day 6 evening (2026-04-26). Five phases that close the curator-prescription → collector-execution loop: modsec parser fix, cron --from-file fixture adapter, session-event → memstore-pending bridge, writeback emits user.custom_tool_result, args translator + 11 per-verb observe adapters. Two sentinel/FP cycles applied. Ships at v0.6.0; 399/399 hermetic on debian12 + rocky9.
Path C · Skills + Files architecture
The shipped skill-delivery shape: 6 description-routed routing Skills + 8 reference Files mounted at /skills/<basename>. Path A would have been the read_only memstore (retired on M13); Path B (callable_agents hunters) was deferred for API stability. Path C is what shipped.

Reference

First-class quick-lookup surfaces. Every verb, every flag, every config primitive bl reads. Start here if you're integrating bl into existing tooling.

Architecture

The shape of the system. What blacklight is, the layer boundaries, and the contracts that bind them.

Operating

How blacklight runs in production. Setup, evidence formats, security model.

Build History

How the project got to its current shape. The pivots that mattered, the build provenance, the patterns and anti-patterns.