Explore the newsroom Showing 1–4 of 10 stories Newest first
The event belongs to the asset assigned when it happened. Sensor s1: Assigned to machine A before 14:00. Reassignment: Assigned to machine B from 14:00. Observation: Event time 13:58; arrival time 14:03. Historical context: Resolve the observation to machine A. Synthetic example: sensor s1 moves from machine A to B at 14:00. A delayed observation occurred at 13:58, so its asset context is A even though it arrives at 14:03. The ingestion adapter must preserve event time, units and assignment history. INDUSTRIAL DATA / ASSET CONTEXT ORIGINCHAINDB SENSOR s1 Assigned to machine A Before 14:00 Assigned to machine B From 14:00 14:00 Event 13:58 Arrives 14:03 Resolve the delayed event to A Event time and arrival time answer different questions CONCEPTUAL ILLUSTRATION Industrial interoperability 11 Oct 2026
OPC Foundation and Avnu’s September collaboration focuses on testable industrial interoperability. Above the network, teams still need to connect observations to assets, revisions and maintenance evidence.
Read the story ↗ Compare runs only after recording what changed. Questions: Retain representative queries and labels. Corpus: Pin the source revision used in the run. Configuration: Record model and retrieval settings. Evidence trace: Inspect candidates, permission decisions and supported output. Illustrative reproducible experiment. Hold questions and corpus revision stable when comparing retrieval configurations, then inspect ranking, access, freshness and unsupported-answer failures separately. No benchmark result is claimed. ENTERPRISE AI / EVALUATION ORIGINCHAINDB PINNED INPUTS Questions + labels Version q1 Corpus revision Version c1 Configuration A Record settings Configuration B Record the change Review Access Freshness Support Version the experiment, then review failures by stage CONCEPTUAL ILLUSTRATION Enterprise AI evaluation 10 Oct 2026
NIST’s September ARIA planning manual reinforces a broader view of evaluation. Application teams can start by making retrieval inputs, source revisions and failure cases inspectable.
Read the story ↗ Discovery finds a candidate; confirmation checks the current fact. Search candidate: A description is relevant to the request. Source changed: The product becomes unavailable. Current-record check: Read availability before confirmation. Decision: Do not offer stale availability from an earlier snippet. Illustrative stale-availability test. Candidate retrieval is not the authoritative inventory check. The application re-reads the current product record before presenting a commitment or next action. RETAIL / AGENT COMMERCE ORIGINCHAINDB DISCOVERY Relevant candidate Product p1: weekend bag Candidate ID p1 No stock commitment CONFIRMATION Current record p1 Availability: unavailable Do not offer p1 Show its updated state Source changed between the two steps Relevance and availability have different jobs CONCEPTUAL ILLUSTRATION Commerce and product data 9 Oct 2026
A September W3C–GS1 workshop puts machine-consumable commerce in focus. Here is a practical data design retailers can test without confusing discovery with a purchase decision.
Read the story ↗ A relevant document still has to pass the access boundary. Requesting principal: Know whose resources the agent may access. Permission gate: Evaluate resource and action scope. Allowed evidence: Only permitted current source text can proceed. Blocked evidence: Exclude its title, snippet and citation too. Illustrative application boundary. Retrieval relevance cannot grant permission. An agent may receive only allowed evidence, and a read permission does not authorize a deployment change. SOFTWARE AGENTS / AUTHORIZATION ORIGINCHAINDB Team A request Read documentation ACCESS Resource + action Team A source Allowed evidence Team B source Blocked before output Read authority does not grant write authority Permission applies before evidence reaches the model CONCEPTUAL ILLUSTRATION AI identity and access 8 Oct 2026
NCCoE’s September update puts agent identity and authorization into a practical software-development context.
Read the story ↗ Industry reading listRecent headlines from official sources · checked 11 Oct 2026 + PostgreSQL · 9 Oct 2026
PostgreSQL · 7 Oct 2026
PostgreSQL · 7 Oct 2026
PostgreSQL · 5 Oct 2026
Model Context Protocol · 22 Aug 2026
Model Context Protocol · 28 Jul 2026
External publications, separate from OriginChainDB announcements and partnerships.
