What is a Memory Unit?

A Memory Unit is a deterministic JSON envelope linking domain payloads (RFQ, auction, forecast, etc.) with actors, timestamps, hashing and optional signatures (multi-signer ready).

Do you custody assets or run an exchange?

No. SemantiCord provides narrative, verification and transparency layers while keeping settlement or trading off‑platform.

How are hashes computed?

We produce canonical JSON by stable key sorting, removing the signatures array (if present) and blanking the hash field before computing SHA‑256.

Can I add my own schema?

Yes. Add a JSON Schema file plus a manifest entry and it is loaded client‑side for validation and generation.

What about private / sensitive data?

Use redaction or selective disclosure: store commitments or hashed pointers while exposing only necessary public narrative fields.

Verifiable market memory & narrative layer

Narratives for a Trustful Market

SemantiCord transforms the activity of GeoBid, OmniRFQ, and PredictAI into verifiable stories — activation campaigns, compliance‑ready trails, and market memory.

Explore Protocols

Semantic (meaning in logic) Cord (fabric of computation)

Work with Trusted Data

Capture signals, publish verifiable narratives — anchored artifacts you can trust and verify locally.

Who Uses SemantiCord

Verifiable narratives for teams that need to prove, not just claim.

📍 Marketplaces

Market Operators & Platforms

Local auction operators, RFQ platforms, and prediction markets building trust through verifiable recaps and tamper-proof settlement records.

Use: GeoBid, OmniRFQ, PredictAI

🔒 Compliance

Regulated Industries

Finance, healthcare, supply chain, and government teams needing cryptographically verifiable audit trails without blockchain complexity.

Schemas: attestation, settlement, transactionLog, consentRecord

🌍 Impact

ESG & Impact Reporting

Nonprofits, corporations, and carbon registries publishing verifiable impact claims with transparent methodologies and quality tracking.

Schemas: impactSnapshot, esgConsolidatedReport, impactUnitIssuance

💹 Data Markets

Data Marketplace Participants

Producers and consumers needing provenance tracking, quality reports, and verifiable pricing throughout the data lifecycle.

Flow: listing → bid → settlement → invoice → payment

🧠 AI/ML

Forecasting & Model Publishers

AI teams building credibility through immutable forecast-to-outcome track records, model cards, and evaluation transparency.

Schemas: predictAIForecast, forecastEvaluation, modelCard

⚙️ Developers

Integration Teams

Developers needing standardized schemas, finance automation scripts, and client-side verification without backend lock-in.

Tools: 53 schemas, billing scripts, Merkle utilities

Design Philosophy

SemantiCord is a trust layer, not a database or exchange. It's designed for verifiable narratives—from B2B marketplaces to consumer-facing transparency (ESG claims, forecast track records, impact reporting). Works off-chain first with optional blockchain anchoring. Not optimized for high-frequency trading or apps requiring sub-millisecond latency.

Explore Schemas View Proof Feed

What we power

Three products — one trust layer.

GeoBid

Local & Geofenced Auctions

Run proximity‑aware auctions for local food, energy, and services. SemantiCord creates the narrative and the public recap for every drop.

OmniRFQ

Compliance‑First RFQ

Explain RFQs, attach documents, and publish a clear, auditable trail — without acting as a custodian or exchange.

PredictAI

Signals → Market Memory

Turn forecasts into weekly, time‑stamped summaries that compound credibility and attract participants.

Protocols (outcome‑driven)

Operate playbooks, not packages — measured by filled auctions, cleared RFQs, and active readers.

1. Activation

Launch & Onboard

Drop pages for GeoBid with live context
RFQ pre‑qualification flows for OmniRFQ
Shareable assets for fast distribution

2. Trust Trail

Proof, not promises

Signed recaps + verifiable documents
On‑chain hashes for fairness & participation
ESG/CSRD‑aware metadata for audits

3. Market Memory

Compounding credibility

Weekly PredictAI signals + outcomes
SEO‑indexed summaries and data cards
Public archive for partners & press

Modular Primitives & Graph

Composable domain payload schemas referenced by MemoryUnit.metadata.schema. Each primitive can stand alone or link to others via identifier fields.

Core / Trust

memoryUnit: Envelope
attestation: Verifiable claim about a subject
participant: Actor / organization profile
provenance: Data source descriptor

Market & Flow

omniRFQ → settlement
geoBidAuction → bid* → settlement
agreement references RFQ / Auction IDs
documentManifest groups artifacts

*Bids may be embedded or separate payloads.

Signals & Impact

predictAIForecast → forecastEvaluation
impactSnapshot attaches environmental metrics
priceIndex aggregates forecasts / settlements

Relationship Graph

Identifiers create a lightweight graph without hard foreign-key enforcement; integrity comes from hashing + optional signatures.

Interactive Graph Text Graph View

Create & Verify (Client‑Side)

Generate Memory Units or simple Receipts and verify any artifact locally all on client side. Nothing is uploaded.

Memory Unit Generator

gap: 6px; margin-bottom: 4px; font-size: 12px; " >

Live Validate (auto schema: platform + event type)

Loaded Schemas (read-only)

Local P-256 Signature

Fill fields and generate…

Signatures

#	Algorithm	Address	Created	Status
No signatures

Simple Receipt

Enter text and create…

Verify JSON

Canonical View

Manual Hash (paste canonical JSON)

Proof feed

Live recaps with verifiable hashes. Filter by platform and drill into artifacts.

Schemas

Reference JSON Schemas (draft 2020-12 style) used for guidance & live validation. These are client-side only; no data leaves your browser.

MemoryUnit & Domain Payloads

Schemas loaded from /schemas. Add a JSON file + manifest entry to extend.

Notes

Deterministic hashing: Keys sorted (stable stringify). artifacts.jsonHash blanked & signatures excluded before computing.
Receipts: Canonical excludes the generated id so the same message + timestamp hash identically.
Validation: Client enforces basics; full JSON Schema validation.
Optional signatures: Multiple signatures can be attached (not included in hash) — EIP-191 / wallet support, WebCrypto P-256, or any others.
Anchors: Placeholder anchor/tx hashes are demo values (not on-chain).
Extensibility: New domain schemas can be added and they appear automatically.

Case studies