ECAI: Knowledge Retrieval, Relations and Reviewable AI
Index source collections, retrieve records with provenance, control model access and inspect typed relations and candidate repairs.
Open your ECAI dashboard
Sign in with your DamageBDD account to access your hosted workspace, indexing and verification tools.
Keep the source behind the answer
ECAI (Elliptic Curve AI) is the knowledge and relation-processing part of the DamageBDD platform. The documented implementation combines managed indexing, retrieval, source identities, private-corpus access controls, typed relations and interfaces to language models.
Its practical role is to make records and proposed actions easier to inspect: which source supports an answer, which corpus release was searched, which relationship was computed and which evidence accompanies a candidate repair. The capability matrix records the evidence for each path.
Choose an implementation workflow
| Need | Reference |
|---|---|
| Build a searchable collection | Managed indexing and Wikipedia collections |
| Find and inspect the supporting record | Search evidence and engineering memory |
| Restrict which records reach a model | Private retrieval and controlled LLM access |
| Inspect structural code relationships | Typed relation processing |
| Review an incident-driven repair proposal | Repair workflows |
| Publish a versioned knowledge artifact | Index artifacts and NFT boundaries |
| Reuse media and track revisions | Video Fastpath pilot and its local-test scope |
For a customer evaluation, begin with private knowledge and incident review. Indexing jobs, knowledge releases, model inference and settlement are separate services; inclusion in this table does not establish one end-to-end production deployment.
Determinism, integrity and meaning
| Property | What it can establish | What it cannot establish alone |
|---|---|---|
| Deterministic encoding | The same specified input and algorithm produce the same identity | Equivalent wording has identical meaning |
| Hash or curve-point binding | A checkable relationship to supplied bytes under the chosen construction | Recovery of arbitrary text by reversing a hash |
| Signature or record proof | Authenticity/integrity relative to a trusted key or root | Truth of the source statement |
| Typed relation rules | A result follows from the encoded relations and implemented rules | General reasoning accuracy on an unseen domain |
| Retrieval with provenance | Which retained record was returned | Correct ranking, completeness or a hallucination-free generated answer |
Search needs stored records and an index or lookup mechanism. Group operations on points do not create missing source data or assign semantic meaning by themselves. The LLM bridge deliberately uses models where configured; its answers and proposed repairs still require evaluation.
Cryptography has a defined scope
Ordinary elliptic-curve cryptography is not a post-quantum security guarantee. A hybrid-cryptography interface in private storage requires its own real-backend and deployment validation. Describe the algorithm, parameters and evidence for the particular boundary rather than assigning a security property to “ECAI” as a whole.
For hash-to-curve constructions, consult RFC 9380. Adding a compressed-point prefix to a hash does not ensure a valid curve point. The encoding and proof guide explains the limits of the earlier educational examples.
Research and implementation
The ambition is structured, inspectable computation over knowledge. Broader claims about geometric reasoning need explicit semantics and experiments. The conceptual introduction separates this direction from the implementation; the research index labels earlier drafts.
The EKEF v0.3 draft is not a release-wide wire-format contract. The Red Lines and Guardrails policy states design commitments; each enforcement mechanism needs implementation evidence.
Follow the work
Read the implementation repository, platform vision and implementation articles. The author's Nostr profile contains discussion and research commentary; it is not a release acceptance log.
Live ECAI updates
Follow ECAI discussions as they arrive from public Nostr relays. These posts are commentary, not verified release evidence. Scroll down the page to load older posts; use the manual control if a relay cannot provide more results.