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

Highlights

  • Pro

Organizations

@projnanda

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 Internet of AI Agents

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


The Vision

The industry is scaling the Internet of Agents. But the mainstream narrative assumes reliable cloud connectivity, abundant compute, and low-stakes consumer tasks. The autonomous economy at the extreme edge — aerospace, defense, maritime, physical infrastructure — needs more: cryptographic model governance, offline-capable identity, structural compliance, verifiable capability restriction, signed agency receipts under bounded delegated authority, and operator surfaces that turn signed evidence into something a human can triage in real time. These libraries are the building blocks.

Each ships a small, versioned Protocol surface and a public conformance suite. Any backend — including proprietary ones — plugs in behind the same Protocol and proves compliance against the same public tests. Compliance is mechanical, not declarative: a runtime ships a signed sm-conformance badge, re-verifiable offline by anyone holding the runtime's did:key — no service on the path, no vendor lock-in.


Stellar Minds map

 +-----------------------------------------------------------+
| OPERATOR SURFACES (TS / React) |
| attest-viewer · decision-inspector · attest-auditor |
+--------------------------- ↑ -----------------------------+
| signed evidence (receipts / AAE envelopes)
+-----------------------------------------------------------+
| AGENCY & ACCOUNTABILITY arp · aae · dat · parc |
| did it happen? · was it allowed? · is it trusted? |
+-----------------------------------------------------------+
| BEHAVIORAL TRUST locp → airlock → enclave |
+-----------------------------------------------------------+
| MODEL TRUST provenance · card · integrity · gov|
+-----------------------------------------------------------+
| ACCOUNTABLE DISCOVERY resolver → divergence |
| is the registry itself telling the truth? |
+-----------------------------------------------------------+
| FEDERATION bridge · org-server · org-agent · federation|
+-----------------------------------------------------------+
conformance binds every tier — signed, offline-checkable badges

Substrate tiers are Python-first (they run where agents run); Operator Surfaces are TS / React (they run where humans look).


The libraries

🧾 Agency & Accountability — what an agent owes the human it represents · receipts · verdicts · authority · reputation (4)

The layer above MCP (tool integration) and A2A (transport) that those standards deliberately leave open: what does an agent owe the human it acts for? Four primitives, one signing path (Ed25519 over JCS), each answering one part of a trust question — and composable end-to-end.

LibraryWhat it doesInstall
sm-arpAgency Receipt Protocol — per-action, Ed25519-signed, JCS-canonical, hash-chained receipts. Did it happen?pip install sm-arp
sm-aaeAttested Action Envelope — a signed, hash-chained record of a pre-action authorization verdict (authorized / denied / conditional); refusals are first-class, provable later. What was permitted, and what was refused?pip install sm-aae
sm-datDelegated Authority Token — the principal-signed grant bounding what an agent may do, for how long, under what limits; three-valued, recomputable verdicts. Was it authorized?pip install git+https://github.com/Sharathvc23/sm-dat.git
sm-parcPortable Agent Reputation Credential — a recomputable reputation VC consumed at chapter admission; reputation that travels, collusion that can't. Is it trusted?pip install sm-parc
🧠 Model Trust — what is this model? · identity · cards · integrity · governance (4)
LibraryWhat it doesInstall
sm-model-provenanceZero-dep model identity dataclass (id, provider, version, tier); maps into AgentFactspip install git+https://github.com/Sharathvc23/sm-model-provenance.git
sm-model-cardUnified model-card schema; 4-state lifecycle with transition guardspip install git+https://github.com/Sharathvc23/sm-model-card.git
sm-model-integrity-layerOffline SHA-256 weight hashing, HMAC attestation, lineage; blocks base-swap attackspip install git+https://github.com/Sharathvc23/sm-model-integrity-layer.git
sm-model-governance3-plane ML governance; Ed25519 sigs, M-of-N quorum, drift auto-revocationpip install git+https://github.com/Sharathvc23/sm-model-governance.git
🛡️ Behavioral Trust — what may this agent do, right now? · compliance · capability · staging (3)
LibraryWhat it doesInstall
sm-locpOpen Compliance Protocol — defeasible-logic engine + W3C VC issuance; mints AAEspip install git+https://github.com/Sharathvc23/sm-locp.git
sm-airlockAllowlist-gated plugin sandbox; deny-by-default, sliding-window rate limits, signed manifestspip install git+https://github.com/Sharathvc23/sm-airlock.git
sm-enclaveSpeculative-execution sandbox; stages effects, commits the winner, irreversibility gatepip install git+https://github.com/Sharathvc23/sm-enclave.git
👁️ Operator Surfaces — how does a human see what the agents are doing? (TS / React, 3)
LibraryWhat it does
sm-attest-viewerRenders AAE streams as forensic, filterable, reverse-chronological timelines
sm-decision-inspectorHITL workbench for decision envelopes; M-of-N quorum chip, gesture-safe approve / deny
sm-attest-auditorBidirectional audit drill; RFC 6962 merkle inclusion verified in-browser via Web Crypto
🌐 Federation & NANDA Protocol — how agents find, join, and trust each other (4)
LibraryWhat it doesInstall
sm-bridgeNANDA-compatible registry endpoints + Quilt delta sync; drop-in FastAPI routerpip install git+https://github.com/Sharathvc23/sm-bridge.git
sm-org-serverMinimal, backend-agnostic server implementing the Chapter Protocol wire (~550 lines)pip install sm-org-server
sm-org-agentThe agent client signing surface — did:key identity, canonical strings, Ed25519 headerspip install sm-org-agent
sm-federationCross-server federation descriptor + envelope specpip install git+https://github.com/Sharathvc23/sm-federation.git
🔎 Accountable Discovery — is the registry itself telling the truth? · corroboration · divergence (2)

Discovery is only as honest as the registry answering. A registry can lie by omission (hide an agent), tampering (a false endpoint), or equivocation (different answers to different clients) — and no signature on a single record proves what a registry chose not to serve. The defense is corroboration: ask several sources the same question and make any disagreement loud. Together these two are the reference implementation of the IETF Internet-DraftMulti-Source Corroboration for AI Agent Discovery (draft-chandra-agent-registry-corroboration).

LibraryWhat it doesInstall
sm-resolverThe corroboration kernelResolver[T], the View contract, a vantage-aware diff, the Corroborator. Zero runtime dependencies. What did each source claim?pip install sm-resolver
sm-divergenceCheating-registry detection — omission / endpoint / DID divergence across registries + a signed Corroboration Record. Do they agree?pip install sm-divergence
✅ Conformance — the shared substrate that makes "compliant" checkable

sm-conformance is orthogonal to the trust tiers — not one of them, but the substrate that lets any of them prove it is honestly implemented. A runtime runs a tier's vectors-driven suite, then ships a small JSON badge signed by its own Ed25519 key, recording which suite it passed (pinned by a suite_digest over the vector corpus) and the pass/fail counts. Any party re-verifies the badge offline against the runtime's did:key — no service, no proprietary library on the path. It ships a trust ladder — self-signed badge and lab counter-signature — with --require-countersigned admission gates, so a registry can demand a trusted lab's attestation rather than accept a runtime's self-claim.

pip install sm-conformance


Design Principles

PrincipleHow
Zero dependencies (Python tier)Core 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-basedExtension points use @runtime_checkable protocols (Python) or typed event arrays (TS) — no forced inheritance, no lock-in
Conformance-drivenEvery versioned Protocol ships a public test suite; backends prove compliance by passing the same tests as the reference implementation
Fail-fast validationInvalid data is rejected at construction time, not discovered downstream
ComposableEach library answers one question; stack them for full governance or use any one standalone
Offline-firstEvery operation works without network access; federation is additive, not required
Quick start — five tiers in ~25 lines
# Identityfromsm_model_provenanceimportModelProvenanceprovenance=ModelProvenance(model_id="my-model", provider_id="local", model_version="1.0")
# Metadatafromsm_model_cardimportModelCardcard=ModelCard(model_id="my-model", model_type="lora_adapter", status="shadow")
# Integrityfromsm_integrityimportcheck_governance, STANDARD_POLICIESreport=check_governance(provenance, policies=STANDARD_POLICIES)
# Governancefromsm_governanceimportGovernanceCoordinatorcoord=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 AAEsfromsm_locpimportRegulatoryTheoryBuilder, Literaltheory= (
RegulatoryTheoryBuilder("WAREHOUSE")
.defeasible("D1", ["operator_certified"], "permitted", priority=5)
.fact("operator_certified")
.build()
)
result=theory.query(Literal.parse("permitted"))
# Federationfromsm_bridgeimportSmBridge, SimpleAgentbridge=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

PackageVersionTestsDependencies
sm-bridge0.3.140FastAPI, Pydantic
sm-model-provenance0.2.043None
sm-model-card0.2.043None
sm-model-integrity-layer0.2.0153None
sm-model-governance0.2.097None
sm-locp0.2.0102cryptography
sm-enclave0.2.086None
sm-airlock0.2.078None
sm-attest-viewer0.2.369React 19, Radix UI
sm-decision-inspector0.1.145React 19, Radix UI
sm-attest-auditor0.1.135React 19, Radix UI
sm-arp0.3.0170cryptography, base58, jcs
sm-aae0.1.035cryptography
sm-dat0.1.042sm-arp, cryptography, jcs
sm-parc0.2.156cryptography, base58, jcs
sm-org-server0.1.075FastAPI, sm-arp
sm-org-agent0.1.034cryptography, sm-arp
sm-federation0.1.028None
sm-resolver0.2.031None
sm-divergence0.8.0114httpx (+ Ed25519 extra)
sm-conformance0.3.296cryptography, base58
Total1,472

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

Pinned Loading

  1. sm-decision-inspectorsm-decision-inspectorPublic

    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

  2. nandatownnandatownPublic

    Forked from projnanda/nandatown

    Python 1

  3. sm-model-cardsm-model-cardPublic

    Unified model card schema for NANDA-compatible agent registries — covers LoRA adapters, edge ONNX, federated, and heuristic models with built-in validation and lifecycle tracking

    Python 1

  4. city-of-agentscity-of-agentsPublic

    Forked from rameshraskar/city-of-agents

    Control plane for the City of Agents — FastAPI service registry and NEST network onboarding.

    Python