JSPM

@verifiedstate/haystack

0.1.0
    • ESM via JSPM
    • ES Module Entrypoint
    • Export Map
    • Keywords
    • License
    • Repository URL
    • TypeScript Types
    • README
    • Created
    • Published
    • Downloads 5
    • Score
      100M100P100Q41386F
    • License MIT

    VerifiedState integration for Haystack — cryptographic receipts for every agent assertion

    Package Exports

    • @verifiedstate/haystack
    • @verifiedstate/haystack/dist/index.js

    This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@verifiedstate/haystack) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

    Readme

    @verifiedstate/haystack

    Haystack Finds the Facts. It Doesn't Sign Them.

    VerifiedState integration for Haystack. Adds cryptographic verification receipts to every assertion your Haystack agent makes.

    Install

    npm install @verifiedstate/haystack

    Quick Start

    import { VerifiedStateHaystack } from '@verifiedstate/haystack';
    
    const memory = new VerifiedStateHaystack({
      apiKey: 'vs_live_...',
      namespaceId: 'your-namespace-uuid',
    });
    
    // Store and verify a fact from your Haystack agent
    const { artifact, assertions, receipts } = await memory.storeAndVerify(
      'Customer prefers dark mode and uses PostgreSQL'
    );
    
    console.log(receipts[0].status);           // "verified"
    console.log(receipts[0].final_confidence); // 0.94
    
    // Query verified memory
    const results = await memory.query('What database does the customer use?');
    console.log(results.answerable);     // true
    console.log(results.channels_used);  // ["sparse", "dense"]

    Why

    Every fact your Haystack agent stores should come with proof — a signed receipt showing what the claim is, what evidence supports it, and whether it's been challenged or superseded.

    Without verification receipts, you have the agent's output. You don't have the reasoning.

    API

    store(content, sourceId?)

    Store content from your Haystack agent.

    extract(artifactId)

    Extract structured assertions.

    verify(assertionId)

    Verify an assertion, produce a signed receipt.

    storeAndVerify(content, sourceId?)

    All-in-one: store, extract, verify.

    query(queryText, limit?)

    Six-channel retrieval with abstention.

    health()

    Namespace health metrics.

    License

    MIT