惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

H
Hackread – Cybersecurity News, Data Breaches, AI and More
U
Unit 42
Vercel News
Vercel News
Martin Fowler
Martin Fowler
云风的 BLOG
云风的 BLOG
爱范儿
爱范儿
MongoDB | Blog
MongoDB | Blog
J
Java Code Geeks
F
Fortinet All Blogs
MyScale Blog
MyScale Blog
C
Check Point Blog
N
Netflix TechBlog - Medium
Microsoft Azure Blog
Microsoft Azure Blog
aimingoo的专栏
aimingoo的专栏
博客园_首页
WordPress大学
WordPress大学
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
IT之家
IT之家
Last Week in AI
Last Week in AI
罗磊的独立博客
大猫的无限游戏
大猫的无限游戏
Jina AI
Jina AI
V
Visual Studio Blog
小众软件
小众软件

Hacker News - Newest: "AI"

AI can't read an investor deck AI as an attorney? Student uses ChatGPT, Gemini to sue UW over alleged racial discrimination Hacking MCP Servers in AI Systems – The Rug Pull: Tool Changes After Approval GitHub - MeepCastana/KubeezCut: Free Web based video editor Can AI judge journalism? A Thiel-backed startup says yes, even if it risks chilling whistleblowers Coming soon: 10 Things That Matter in AI Right Now DARPA built an AI to fact-check enemy weapons claims What explains heterogeneity in AI adoption? When AI Meets Muscle: Context-Aware Electrical Stimulation Promises a New Way to Guide Human Movements - Department of Computer Science AI Changed How We Build. It Did Not Change What Matters. Linux rules on using AI-generated code - Copilot is OK, but humans must take 'full responsibility for the… Meta spins up AI version of Mark Zuckerberg to engage with employees Code Mode: Let Your AI Write Programs, Not Just Call Tools | TanStack Blog GitHub - Delavalom/graft: Go framework for building AI agents. Type-safe tools, multi-provider (OpenAI, Anthropic, Gemini, Bedrock), zero vendor SDKs. India's TCS tops estimates, says new AI models did not dent services demand Gen Z's fading AI hype Strong feeling: we are in a folded AI reality GitHub - machinarii/total-recall-catalog: A reference catalog of latest knowledge retrieval, memory & RAG systems GitHub - mensfeld/code-on-incus: Give each AI agent its own isolated machine with root, Docker, and systemd. Active defense detects and stops threats automatically.. Quantization, LoRA, and the 8% Problem: Benchmarking Local LLMs for Production AI Iran war: We spoke to the man making Lego-style AI videos that experts say are powerful propaganda Powell, Bessent discussed Anthropic's Mythos AI cyber threat with major U.S. banks GitHub - immartian/bellamem: Persistent belief-graph memory for AI agents. Retrieves decisive context by importance — not recency, not RAG, not /compact. recursive-mode: The Repo-Native Operating System for AI Engineering After the attack on Sam Altman's home, will AI CEO's go on the offensive? The biggest advance in AI since the LLM Opus 4.6 vs GPT 5.4 One Prompt Unity World Generation Test “AI polls” are fake polls Client Challenge Can AI be a 'child of God'? Inside Anthropic's meeting with Christian leaders
GitHub - arian-gogani/nobulex: The accountability primiti...
arian_ · 2026-04-25 · via Hacker News - Newest: "AI"

CI OpenSSF Best Practices

AI agents can't prove they followed their own rules. Nobulex fixes that.

$ npx tsx examples/demo.ts

Agent A declares covenant: permit read, forbid transfer > 500
Agent A executes 5 actions...
  ✓ read /data/users — allowed
  ✓ transfer $300 — allowed
  ✓ read /data/orders — allowed
  ✗ transfer $600 — BLOCKED by covenant
  ✓ read /data/config — allowed

Agent B verifies Agent A...
  ✓ Step 1: Covenant signature valid
  ✓ Step 2: Proof signature valid
  ✓ Step 3: Log integrity verified (5 entries, chain intact)
  ✓ Step 4: Compliance check passed (0 violations)
  ✓ Step 5: History length sufficient (5 ≥ 1)
  ✓ Step 6: Covenant matches requirements
  ✓ Step 7: Audience binding confirmed
  ✓ Step 8: Task class verified

Result: Agent B trusts Agent A ✅

Agent C presents tampered proof...
  ✓ Step 1: Covenant signature valid
  ✓ Step 2: Proof signature valid
  ✗ Step 3: FAILED — hash chain broken at entry 2

Result: Agent B refuses Agent C ❌

Three primitives. That's the whole protocol:

  1. Declare — write rules: permit, forbid, require
  2. Enforce — check every action before it runs
  3. Prove — tamper-evident hash chain anyone can verify

Tests License TypeScript

Try it live · Policy Designer · Quickstart · Compare · Receipt Schema · Pricing · IETF Draft

What is Proof-of-Behavior?

You can't audit a neural network. But you can audit actions against stated commitments.

verify(covenant, actionLog) → { compliant: boolean, violations: Violation[] }

This is always decidable, always deterministic, always efficient. No ML, no heuristics — mathematical proof.

Proof-of-behavior means every autonomous agent action is:

  • Declared — behavioral rules defined before deployment in a formal language
  • Enforced — violations blocked at runtime, before execution
  • Proven — every action hash-chained into a tamper-evident audit trail that third parties can independently verify

Quick Start

npm install @nobulex/sdk
import { createDID, parseSource, EnforcementMiddleware, verify } from '@nobulex/core';

// 1. Create an agent identity
const agent = await createDID();

// 2. Write behavioral rules
const spec = parseSource(`
  covenant SafeTrader {
    permit read;
    permit transfer (amount <= 500);
    forbid transfer (amount > 500);
    forbid delete;
  }
`);

// 3. Enforce at runtime
const mw = new EnforcementMiddleware({ agentDid: agent.did, spec });

// $300 transfer — allowed
await mw.execute(
  { action: 'transfer', params: { amount: 300 } },
  async () => ({ success: true }),
);

// $600 transfer — BLOCKED before execution
await mw.execute(
  { action: 'transfer', params: { amount: 600 } },
  async () => ({ success: true }),  // never runs
);

// 4. Prove compliance
const result = verify(spec, mw.getLog());
console.log(result.compliant);    // true
console.log(result.violations);   // []

Cross-Agent Verification Handshake

Before two agents transact, they verify each other's proof-of-behavior. No proof, no transaction.

import { generateProof, verifyCounterparty } from '@nobulex/sdk';

// Agent A generates its proof-of-behavior
const proof = await generateProof({
  identity: agentA,
  covenant: spec,
  actionLog: middleware.getLog(),
});

// Agent B verifies Agent A before transacting
const result = await verifyCounterparty(proof);

if (!result.trusted) {
  console.log('Refusing transaction:', result.reason);
  return; // No proof, no transaction
}

// Safe to transact — Agent A is verified
await executeTransaction(proof.agentDid, amount);

The handshake checks eight things in order: covenant signature, proof signature, log integrity, compliance, minimum history, required covenant, audience binding, and task class scoping. If any check fails, the transaction is refused.

Why Proof-of-Behavior Matters

What exists today What's missing
Guardrails filter prompts and outputs No proof the agent followed rules at the action layer
Monitoring watches what agents do after the fact No enforcement before execution
Identity verifies who the agent is No verification of what the agent did
Governance platforms provide dashboards and policies No cryptographic evidence a third party can independently verify

Proof-of-behavior fills the gap: declare → enforce → prove.

The Covenant DSL

covenant SafeTrader {
  permit read;
  permit transfer (amount <= 500);
  forbid transfer (amount > 500);
  forbid delete;
  require counterparty.compliance_score >= 0.8;
}

Forbid wins. If any forbid matches, the action is immediately blocked regardless of permits. Default deny for unmatched actions. Conditions support >, <, >=, <=, ==, != on numeric, string, and boolean fields.

Three keywords. No configuration files. No YAML. No JSON schemas. Just rules.

Architecture

┌─────────────────────────────────────────────────────────────┐
│                      Integrations                           │
│            mcp-server  ·  a2a  ·  langchain                 │
├─────────────────────────────────────────────────────────────┤
│                       User API                              │
│                         sdk                                 │
├─────────────────────────────────────────────────────────────┤
│                   Proof-of-Behavior                         │
│                                                             │
│  identity · covenant-lang · action-log · enforcement        │
│  middleware · verification · crypto · merkle · proofs       │
│                                                             │
│                         core                                │
└─────────────────────────────────────────────────────────────┘

Packages

Package What It Does
@nobulex/core Everything — identity (DIDs), covenant DSL, hash-chained action logs, enforcement middleware, verification, cryptographic proofs
@nobulex/sdk User-facing API — NobulexClient, CovenantAgent, cross-agent handshake
@nobulex/mcp-server MCP compliance server for Claude Desktop, Cursor, VS Code
@nobulex/a2a A2A Agent Card behavioral attestation extension
@nobulex/langchain LangChain callback integration
@nobulex/claude-agent-sdk Claude Agent SDK compliance hooks — PreToolUse/PostToolUse gating, tamper-evident tool-call logs

Integrations

  • npmnpm install @nobulex/sdk
  • MCPnpx @nobulex/mcp-server (works with Claude Desktop, Cursor, VS Code)
  • A2A — Agent Card behavioral attestation extension
  • LangChain — drop-in compliance callbacks

Conceptual Comparison

Bitcoin Ethereum Nobulex
What it verifies Monetary transfers Contract execution Agent behavior
Mechanism Proof of Work Proof of Stake Proof of Behavior
What's proven Transaction validity State transitions Behavioral compliance
Guarantee Trustless money Trustless contracts Trustless agents

Live Demo

npx tsx examples/demo.ts

Creates two agents, defines behavioral rules, enforces at runtime, blocks a forbidden transfer, generates a proof-of-behavior, runs the 8-step handshake, and then shows the same handshake rejecting a third agent whose log was tampered with — all in one script.

npx tsx examples/langchain-agent.ts   # covenant enforcement around a mocked LangChain agent
npx tsx benchmarks/bench.ts           # protocol performance on your hardware

Security Audit

We've conducted an internal security review. Here's what we tested and what we found:

Verified secure:

  • Hash chain integrity: modifying any entry breaks the chain (property-tested with fast-check across random chains of varying length).
  • Signature forgery: invalid signatures are rejected 100% of the time.
  • Replay attack prevention: audience-bound proofs fail when replayed to a different verifier (property-tested).
  • Covenant enforcement: forbidden actions are blocked before execution, never after — the handler never runs.

Known limitations:

  • No key revocation mechanism yet — compromised keys remain trusted until removed out-of-band.
  • No rate limiting on handshake verification — potential DoS vector under adversarial load.
  • Single-threaded chain verification — chains above ~100K entries take visible time (see benchmarks).
  • Clock skew tolerance is 0 — agents with desynchronized clocks may fail timestamp checks.

Not in scope:

  • Model-level safety (prompt injection, jailbreaking) — use guardrails for that.
  • Network transport security — use TLS.
  • Key storage — use your platform's HSM or key vault.

See docs/threat-model.md for the full threat model.

Development

git clone https://github.com/arian-gogani/nobulex.git
cd nobulex
npm install
npx vitest run             # full test suite (incl. fast-check property tests)
npx tsx examples/demo.ts   # see the protocol run end-to-end
npx tsx benchmarks/bench.ts

Standards

Ecosystem

Projects building on or composing with Nobulex:

Partner Layer Integration
Dominion Observatory Pre-call trust scores Feeds trust_score into covenant require
SidClaw HITL approval Signed state-transition receipts
Aira Authorization + audit Multi-party signing with RFC 3161
Signet Signing layer Bilateral co-signing, policy attestation
AgentMint Runtime enforcement Ed25519 plan signing, scope matching
APS Receipt schema Co-designed outcome_hash format

Documentation

Links

License

MIT — use it for anything.