Synchronized release projection
Current documented package release
v1.24.0
Released 2026-09-26 from npm:@nebulacomponents/citable@1.24.0. This page is a current projection, not a manually maintained release history.
- Detectors
- 186
- Namespaces
- 19
- Registries
- 29
- License
- Apache 2.0
Runtime requirement: Node.js >=24.0.0.
Release highlights
- Added passive backlink and referring-domain observations (`createPassiveBacklinkObservation`, `compareBacklinkObservations`, `backlinksForTarget`, `referringDomainsForTarget`), preserving source, target, link anchor/rel tokens, and retrieval state while strictly rejecting acquisition, exchange, outreach, or link-quality conclusions (`ER-10`).
- Added machine-consumable evidence interface (`EvidenceInterface`, `createEvidenceInterface`), exposing structured operations for observations, evidence verification, coverage, conditions, comparisons, datasets, claims, prompt sets, and lineage with explicit epistemic state (`ER-12`).
- Added autonomous-content evidence boundary (`verifyContentEvidenceBoundary`), evaluating proposed claims against verified evidence, enforcing that Citable strictly does not generate content or authorize publication without explicit downstream authority, and gating publication fail-closed (`ER-13`).
- Decoupled autonomous outreach and backlink acquisition capabilities (`B-080` through `B-089`) into a dedicated standalone product package (`products/outreach/` / `@nebulacomponents/citable-outreach`) consuming the shared evidence substrate with its own execution-authorization model, preventing state-changing outreach from being bundled into `@nebulacomponents/citable`.
Controlled site assets
These assets are controlled release-governance surfaces. Their links make the deployed bytes inspectable, but they do not establish that the current release reached every live surface.
- Release projection data
Byte-exact controlled resource-data projection served by this site.
- Machine-readable release summary
Byte-exact controlled llms.txt release asset served by this site.
- Controlled-surface governance notes
The receipt and finalization requirements for the controlled surfaces.
Verification boundary
Workflow verification remains unavailable because no fresh committed workflow receipt is projected here. Deployment verification remains unavailable because no fresh committed receipt proves the current live surfaces. A package release record or controlled asset link is not a substitute for either receipt.