Project
Changelog
What changed, one entry per working session, newest first; each links the pull requests and issues behind it. Entries come from the project record, not from a marketing calendar. RSS feed
- APIExplorerCommunityDocs
S6.1, S7.1 and S7.2 built; the follow-ups
STIX 2.1 bundles and TagPacks leave the API and are documented; the ops-agent runner, its playbooks and the kill switch at the key are built and not armed; the changelog and the roadmap pages are live from the codex; four follow-ups landed (the Caddy reload, the claim's canonical content, the status cache, the whole…
Routes:
/v1/export/stix·/v1/export/tagpack·/v1/claims/{claim_id}.stix·/v1/claims/{claim_id}·/v1/ops/operators/{id} - APIExplorerCommunity
S5.1 identity and writes; the relay gauge fix; an unattended session
api#63 (deployed 15:50 UTC): the relay's connection gauge went negative because khatru runs OnDisconnect once per goroutine of a connection; each connection is now counted once; a test drops raw sockets without a close frame (the old counter reads −5).
Routes:
/v1/status - APIExplorerCommunity
S4.2: the Community read API and MCP tools
S4.2 built in two PRs: api#60 (the read model — comments per subject in three orders, counts, the label lens, threads, the firehose, the public directory — and internal/community/zaps: a minimal BOLT11 reader, NIP-57 receipt validation, the P26 aggregation safeguards, the on-demand fetcher cached 10 min) and api#61…
Routes:
/v1/community/{kind}/{key}·/v1/community/labelers·/v1/community/recent - APICommunity
S4.1: the relay and the ingester are live (read-only)
S4.1 built and deployed in four PRs plus one fix: api#55 (migration 006, the event store, the subject index, the lens, the relay policy, the door rules), api#56 (the khatru relay at /relay, NIP-11, metrics, status), api#57 (status.community absent, never null — the merge of #56 had turned CI's contract check red and…
Routes:
/v1/status.community.relay·/v1/mempool·/v1/community/{kind}/{key} - APIExplorerCommunityDocs
Formal specifications per Phase 3 ticket
specs/: one formal specification per ticket (S0.1–S9.4, CP1–CP3, 42 files) — purpose, scope, numbered functional requirements, data model, API contract, rules and algorithms, non-functional requirements, observability, test plan mapped to the requirements, rollout and rollback, definition of done. Design tickets keep…
Routes:
/v1/taxonomy/concepts - APISourcesCommunityDocs
intel layer: research, ADR-0004, coherence pass
Landscape research for the intel layer merged (btcintel-codex#6): sources with licence and confidence class, attribution products, standards (DW-VA, GraphSense, STIX 2.1, MISP, ATT&CK, Nostr NIPs), Phase 3 starting set — research/2026-09-21-intel-layer-landscape.md.