Skip to content
View Sharathvc23's full-sized avatar
💭
Jitterbugging
💭
Jitterbugging

Highlights

  • Pro

Block or report Sharathvc23

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
Sharathvc23/README.md

The Enterprise Internet of AI Agents

Open-source primitives for decentralized, cryptographically governed AI agent networks. Built on Project NANDA standards.


The Vision

The industry is scaling the Internet of Agents — AI agents that discover, communicate, and collaborate across the web. But the mainstream narrative assumes reliable cloud connectivity, abundant compute, and low-stakes consumer tasks.

Critical segments of the autonomous economy — aerospace, defense, maritime logistics, physical infrastructure — operate at the extreme edge. Connectivity is intermittent. Trust must be continuously verified. The penalty for an AI hallucination or unauthorized action can be severe.

To scale AI agents in the enterprise, we need more than discovery. We need cryptographic model governance, offline-capable identity, structural regulatory compliance, verifiable capability restriction, and operator-facing surfaces that turn signed evidence into something a human can triage in real time.

These libraries are the building blocks.


How the libraries fit together

Each library ships a small, versioned Protocol surface and a public conformance test suite. Any third-party backend — including proprietary ones — plugs in behind the same Protocol and proves compliance against the same public tests. The open substrate is the standard; what you build above it is yours. No vendor lock-in, no forked forks.


Trust tiers

Operator Surfaces answer "how does a human see what the agents are doing?" — forensic, filterable timelines of signed agent action evidence. Behavioral Trust answers "what is this agent allowed to do, right now?" — regulation, capability, staging. Model Trust answers "what is this model?" — identity, metadata, integrity, approval. Federation sits beneath all three — how agents find each other on the network.

  +-----------------------------------------------------------+
  |                    OPERATOR SURFACES                      |
  |                       (TS / React)                        |
  |                                                           |
  |  sm-attest-viewer        chronological forensic timeline  |
  |  sm-decision-inspector   HITL workbench, M-of-N quorum    |
  |  sm-attest-auditor       bidirectional audit drill        |
  +--------------------------- ↑ -----------------------------+
                               |  W3C VC streams (AAE wire envelope)
                               |
  +-----------------------------------------------------------+
  |                      BEHAVIORAL TRUST                     |
  |                                                           |
  |    sm-locp     →     sm-airlock    →     sm-enclave       |
  |  (compliance)     (capabilities)      (speculative exec)  |
  |  *emits AAEs*                                             |
  +-----------------------------------------------------------+
                              |
  +-----------------------------------------------------------+
  |                         MODEL TRUST                       |
  |   sm-model-provenance · sm-model-card ·                   |
  |   sm-model-integrity-layer · sm-model-governance          |
  +-----------------------------------------------------------+
                              |
  +-----------------------------------------------------------+
  |                         FEDERATION                        |
  |                                                           |
  |   sm-bridge  —  registry endpoints, Quilt delta sync      |
  +-----------------------------------------------------------+

Substrate tiers (Behavioral / Model / Federation) are Python-first because they run where agents run. The Operator Surfaces tier is TypeScript / React because it runs where humans look — browsers, dashboards, embedded panels.


Model Trust Tier

1. Base Identity — sm-model-provenance

Agents need a standardized way to broadcast who they are and what model powers them, without heavy dependencies in constrained edge environments.

A zero-dependency Python dataclass capturing core model identity (model ID, provider, version, governance tier). Omit-when-empty serialization keeps payloads compact. Maps into the JSON shapes required by NANDA AgentFacts and decision envelopes.

pip install git+https://github.com/Sharathvc23/sm-model-provenance.git


2. Metadata & Lifecycle — sm-model-card

Enterprise environments require structured documentation of an AI's capabilities, training metrics, and deployment lifecycle.

A unified model card schema for federated registries. Covers LoRA adapters, edge ONNX, federated learning, and heuristic models under a single validated dataclass. Four-state lifecycle (shadow → ready → deprecated → archived) with transition guards.

pip install git+https://github.com/Sharathvc23/sm-model-card.git


3. Cryptographic Verification — sm-model-integrity-layer

In a decentralized network, systems must mathematically verify an agent hasn't been compromised in transit or loaded with unauthorized model weights.

An additive integrity gate. Offline SHA-256 weight hashing, HMAC-SHA256 attestation, model lineage tracking, and 6 built-in governance policies. Prevents base-swapping attacks. Zero runtime dependencies.

pip install git+https://github.com/Sharathvc23/sm-model-integrity-layer.git


4. Approval & Drift — sm-model-governance

AI cannot autonomously execute high-stakes actions without a legally defensible audit trail and verifiable oversight.

Three-plane ML governance (Training → Approval → Serving). Ed25519 cryptographic signatures, M-of-N multi-party quorum, time-bounded approvals, and autonomous drift detection with auto-revocation. Designed for aerospace and defense compliance frameworks.

pip install git+https://github.com/Sharathvc23/sm-model-governance.git


Behavioral Trust Tier

5. Regulatory Compliance — sm-locp

An approved model can still do the wrong thing. Regulatory compliance is about what the agent does in the world, not what the model is.

The Open Compliance Protocol (OCP) — a defeasible-logic engine, machine-readable regulations (MRR) format, and W3C Verifiable Credential issuance layer. Agents observe their operational state, check it against regulatory theories, and produce cryptographic proofs of compliance that any third party can verify without re-running the evaluation. The VC issuance layer is what mints Attested Action Envelopes (AAEs) — the per-action evidence primitive consumed by sm-attest-viewer.

Persistence Protocol v1 is frozen. Ship your own corpus, your own backend — the engine is indifferent as long as your implementation passes the public conformance suite.

pip install git+https://github.com/Sharathvc23/sm-locp.git


6. Capability Restriction — sm-airlock

A plugin system without an isolation boundary is an attack surface. Plugins must reach the host agent to be useful, but unrestricted access leaks state, bypasses tenant isolation, and floods the host with unbounded calls.

Allowlist-gated plugin sandbox for autonomous agents. The Airlock proxy denies every attribute access by default and permits only what the caller explicitly declares via AllowlistSpec. Per-method sliding-window rate limits, Ed25519-signed plugin manifests for supply-chain integrity, and a violation-callback hook for audit integration. Zero runtime dependencies.

pip install git+https://github.com/Sharathvc23/sm-airlock.git

7. Decision Staging — sm-enclave

AI agents that touch real-world state need to evaluate their options before committing. Otherwise a wrong decision fires hardware that cannot be undone.

Speculative execution sandbox. Stages side effects produced during speculative branch execution in isolated enclaves, commits the winner atomically, discards the losers. Irreversibility gate blocks hardware-touching commands from firing in speculative branches unless explicitly allowed. Pluggable committers per effect type. Zero runtime dependencies.

pip install git+https://github.com/Sharathvc23/sm-enclave.git


Operator Surfaces Tier

8. Attestation Renderer — sm-attest-viewer

Compliance evidence and operator triage are useless if there's no way to see the signed envelopes flowing past in real time. Operators need a different artefact than a chat log.

Reference renderer for Attested Action Envelopes (AAEs) — the per-action evidence primitive minted by sm-locp. A React / TypeScript component library that displays AAE streams as forensic, filterable, reverse-chronological timelines. As of v0.2, the renderer surfaces the four AAE envelope kinds (action, decision, belief, checkpoint) with kind-specific visual distinctions while remaining backward-compatible with v0.1 producers.


9. HITL Workbench — sm-decision-inspector

A chronological timeline shows that decisions exist. It cannot ergonomically serve the multi-party gesture surface where operators actually authorize or deny — that demands a different primitive.

Reference workbench for the type: "decision" envelope variant. Surfaces the proposed action, the M-of-N countersignature roster, the live quorum chip, and the operator approve / deny controls as a forensic, gesture-safe HITL surface. Locks the gesture surface once quorum is reached so an operator never accidentally double-signs.


10. Bidirectional Audit Drill — sm-attest-auditor

Forward envelope chains alone do not solve forensic audit, because an auditor often arrives after an incident — starting from a known checkpoint commitment and needing to prove a specific envelope was covered by it in O(log N) sibling-path verification.

Reference renderer for bidirectional audit over AAE envelope chains. Walks forward chains via predecessor_hash (cycle-safe, gap-tolerant) and verifies reverse merkle inclusion proofs from checkpoint envelopes per RFC 6962 SHA-256 — runs the cryptographic verification in-browser via Web Crypto, with no proprietary library on the audit path.


Federation

0. Transport & Federation — sm-bridge

Exposing enterprise agents to a federated network should not require rewriting an entire database or implementing complex sync protocols from scratch.

A reference implementation for NANDA-compatible registry endpoints and Quilt-style delta synchronization. Drop-in FastAPI router, DID/handle parsing, thread-safe delta store, and a protocol-based converter for integrating with any internal data model.

pip install git+https://github.com/Sharathvc23/sm-bridge.git


Design Principles

Principle How
Zero dependencies (Python tier) All core Python libraries use only the standard library. Crypto and database backends are optional extras.
Substrate-neutral (TS tier) The renderer accepts events as a prop. It never opens connections, polls endpoints, or makes network calls.
Protocol-based Extension points use @runtime_checkable protocols (Python) or typed event arrays (TS) — no forced inheritance, no vendor lock-in.
Conformance-driven Every versioned Protocol ships with a public test suite. Backends prove compliance by passing the same tests as the reference implementation.
Fail-fast validation Invalid data is rejected at construction time, not discovered downstream.
Composable Each library answers one question. Stack them for full governance or use any one standalone.
Offline-first Every operation works without network access. Federation is additive, not required.

Quick Start

# Identity
from sm_model_provenance import ModelProvenance
provenance = ModelProvenance(model_id="my-model", provider_id="local", model_version="1.0")

# Metadata
from sm_model_card import ModelCard
card = ModelCard(model_id="my-model", model_type="lora_adapter", status="shadow")

# Integrity
from sm_integrity import check_governance, STANDARD_POLICIES
report = check_governance(provenance, policies=STANDARD_POLICIES)

# Governance
from sm_governance import GovernanceCoordinator
coord = GovernanceCoordinator()
output = coord.complete_training("my-model", "sha256:abc", {"loss": 0.28})
approval = coord.submit_for_governance(output, approved_by="governance-lead")

# Regulatory compliance — produces AAEs
from sm_locp import (
    RegulatoryTheoryBuilder, Literal, VCGenerator, ComplianceCredentialSubject,
)
theory = (
    RegulatoryTheoryBuilder("WAREHOUSE")
    .defeasible("D1", ["operator_certified"], "permitted", priority=5)
    .fact("operator_certified")
    .build()
)
result = theory.query(Literal.parse("permitted"))

# Federation
from sm_bridge import SmBridge, SimpleAgent
bridge = SmBridge(registry_id="my-registry", provider_name="My Org", provider_url="https://example.com")
bridge.register_agent(SimpleAgent(id="my-agent", name="My Agent", description="An AI assistant"))

Test Coverage

Package Version Tests Dependencies
sm-bridge 0.3.1 40 FastAPI, Pydantic
sm-model-provenance 0.2.0 43 None
sm-model-card 0.2.0 43 None
sm-model-integrity-layer 0.2.0 153 None
sm-model-governance 0.2.0 97 None
sm-locp 0.2.0 102 cryptography
sm-enclave 0.2.0 86 None
sm-airlock 0.2.0 78 None
sm-attest-viewer 0.2.3 69 React 19, Radix UI, lucide-react
sm-decision-inspector 0.1.1 45 React 19, Radix UI, lucide-react
sm-attest-auditor 0.1.1 35 React 19, Radix UI, lucide-react
Total 791

Sharath Chandra — Personal research contributions aligned with Project NANDA standards. Stellarminds.ai

Pinned Loading

  1. sm-model-provenance sm-model-provenance Public

    A single dataclass that serializes model-related metadata into the JSON shapes expected by NANDA AgentFacts, AgentCard, and decision-envelope outputs. Zero runtime dependencies

    Python 1

  2. sm-model-integrity-layer sm-model-integrity-layer Public

    A single dataclass that serializes model-related metadata into the JSON shapes expected by NANDA AgentFacts, AgentCard, and decision-envelope outputs. Zero runtime dependencies.

    Python 1

  3. sm-locp sm-locp Public

    Stellarminds Open Compliance Protocol — defeasible logic engine, machine-readable regulations, and W3C Verifiable Credentials for autonomous compliance

    Python

  4. sm-attest-viewer sm-attest-viewer Public

    Reference renderer for the Attested Action Envelope (AAE) — TypeScript/React viewer for VC-compliant signed agent action streams. Implements the Attestation pillar of Project NANDA's four-pillar ar…

    TypeScript 2

  5. sm-attest-auditor sm-attest-auditor Public

    Bidirectional audit drill for AAE envelope chains — forward chain-walk via predecessor_hash, reverse RFC 6962 merkle inclusion verification. Companion to sm-attest-viewer + sm-decision-inspector. N…

    TypeScript 1

  6. sm-decision-inspector sm-decision-inspector Public

    Human-in-the-loop workbench for AAE decision envelopes — approve/deny gestures, M-of-N countersignature quorum, signer roster. Companion to sm-attest-viewer. NANDA Attestation pillar.

    TypeScript 1