# DamageBDD > Behaviour verification, ECAI knowledge retrieval and Nostr signing infrastructure. Use the current feature references for implementation details. Conceptual and historical articles may describe broader goals. Read each feature's validation limits and evidence date; do not infer that all components share the same release or verification status. ## Freshness Before using cached documentation, revalidate [the document inventory](https://damagebdd.com/docs/index.json). Compare content_revision, fetch changed documents, and verify the SHA-256 of their decoded HTTP response bytes against markdown_sha256 or html_sha256. Remove cached documents that are absent from the current inventory. Check docs/capabilities.json has the same content_revision before combining it with the inventory. On a hash or revision mismatch, refresh the inventory and retry; do not combine releases. Record the revision and retrieval time with your answer. If revalidation fails, say freshness could not be verified. These checks must be implemented by the consuming agent. generated_at is the build time. last_modified describes document inputs when known; evidence_date and verified_release retain their historical meaning. A new documentation revision does not establish new runtime verification. ## Start here - [Current Features: DamageBDD, ECAI, erm and Nosternity](https://damagebdd.com/articles/features_current.md): A source-reviewed entry point to practical workflows, implementation references and the evidence needed to evaluate the stack. - [User Manual: Get Started with Behavior Testing in Minutes!](https://damagebdd.com/manual.md): Quick start guide to DamageBDD — learn Gherkin syntax, authenticate with bearer tokens, execute feature files via curl and integrate behavior testing into CI/CD pipelines. - [Install DamageBDD](https://damagebdd.com/install.md): Beginner-friendly installation guide for DamageBDD on Linux and Android Termux using the verified production installer. - [DamageBDD Module Index](https://damagebdd.com/modules/index.md) - [DamageBDD Node Admin Guide](https://damagebdd.com/node_admins.md) - [Documentation index](https://damagebdd.com/docs/index.md): All exported topics. ## Features - [Blossom on DamageBDD: Share Files with a Verifiable Byte Identity](https://damagebdd.com/articles/blossom_media.md): An IPFS-backed Blossom implementation with signed upload authorization, bounded transfers and separate ownership claims for supporting files. - [Damage nsecbunker: Custody, Signing Policy and Live Verification](https://damagebdd.com/articles/damage_nsecbunker.md): The implemented DamageBDD NIP-46 bunker, its AWS custody evidence, current policy/status APIs and the exact scope of the release-build acceptance run. - [DamageBDD: Turn Acceptance Criteria into Evidence You Can Share](https://damagebdd.com/articles/damagebdd_evidence_workflows.md): Use readable scenarios, content-addressed reports, schedules and release identity to make service acceptance easier to reproduce and review. - [DamageBDD Nostr Integration: Identities, Events and Verification](https://damagebdd.com/articles/damagebdd_nostr.md): Source-backed Nostr capabilities in DamageBDD, the separation of event transport from signing policy, and the limits of current verification. - [ECAI: Give Engineering Knowledge a Source, a Structure and an Access Boundary](https://damagebdd.com/articles/ecai_engineering_memory.md): Private retrieval, typed code relations and durable indexing jobs provide concrete ways to evaluate ECAI on operational knowledge. - [ECAI Index NFTs: Give a Knowledge Release a Verifiable Identity](https://damagebdd.com/articles/ecai_index_nfts.md): What ECAI index artifacts and indexing-job NFTs represent, how IPFS and lineage fit together, and what remains before an automated paid indexing market. - [ECAI Indexing: Turn Source Collections into Managed Work](https://damagebdd.com/articles/ecai_indexing_workflows.md): A practical guide to ECAI's durable indexing queue, JSONL and IPFS inputs, disk indexes, ingestion journal and separate private retrieval path. - [ECAI Private Knowledge Retrieval and Controlled LLM Access](https://damagebdd.com/articles/ecai_private_knowledge.md): The current private-index implementation: encrypted segments, corpus permissions, bounded retrieval, model destinations and validation limits. - [ECAI Deterministic Relation Processing](https://damagebdd.com/articles/ecai_relation_processing.md): Typed relations, canonical identity, explicit composition rules, proof records and structural benchmarks in the ECAI repository. - [ECAI Repair Workflows: Make a Generated Patch Easier to Review](https://damagebdd.com/articles/ecai_reviewable_repairs.md): Connect incident context, source identity, candidate patches and isolated validation so reviewers can assess what changed and what was actually checked. - [ECAI Search: Find the Record and Check the Evidence](https://damagebdd.com/articles/ecai_search_evidence.md): How ECAI's field-aware lexical search, Wikimedia filters, snapshot identity and record membership proofs can support inspectable retrieval. - [ECAI and Wikipedia: Build a Corpus You Can Inspect and Reuse](https://damagebdd.com/articles/ecai_wikipedia_indexing.md): How ECAI selects Wikipedia articles with pageview data, builds a searchable snapshot and preserves the material behind a corpus release. - [erm: Bring Voice, Media and Operational Knowledge to Your Desktop](https://damagebdd.com/articles/erm_local_voice.md): A local Erlang workspace with typed voice actions, optional model assistance, native speech output and inspectable service health. - [Nosternity: Give Important Signed Events a Retention Policy](https://damagebdd.com/articles/nosternity.md): An append-only contract, event-store adapter and relay recovery path for selected signed Nostr records, with explicit pending-queue and validation limits. - [Nostr Reliability: Live Relay Delivery and NIP-46 Reply Correlation](https://damagebdd.com/articles/nostr_reliability.md): The subscribe-before-publish correction, stale-context protection, relay adapter behaviour and the evidence behind the live bunker tests. ## Machine-readable references - [Capabilities](https://damagebdd.com/docs/capabilities.json): Explicit status, release and evidence fields. - [Document inventory](https://damagebdd.com/docs/index.json): URLs, dates and content hashes.