After a year of building in silence, DCS AI is live.

For the last year, I've been heads-down.

No tweets. No launch post. No "we're stealth, DM for access." Just shipping.

Today that changes. DCS AI Technologies is live across every public surface — and I want to walk you through what we built, why it took a year, and what's actually verifiable on the web right now.

The thesis

AI agents are about to do real economic work. They'll hold budgets, sign contracts, negotiate with other agents, remember what they did six months ago, and present audit trails when regulators ask. None of that infrastructure exists today.

Right now, an "AI agent" is a stateless API call wearing a personality. It has no persistent identity, no on-chain reputation, no way to prove what it did, no way to pay another agent, and no way for two agents from different organizations to discover each other and transact.

That's the gap DCS AI was built to close.

What's live today

We're not announcing intentions — we're announcing infrastructure that you can hit with a curl, verify on a block explorer, or install from npm right now.

Two production domains

The corporate face at dcsai.ai — the Project Fifty roadmap, the investor package, the press kit. The builder-facing face at dcslabs.ai — the MCP server docs, the standard, the mint funnel, the live stats.

The Open Provenance Standard (R+2)

A specification for how AI agents should sign every action, store its receipt, and prove it later. Public draft is on dcslabs.ai/standard. Submitting to MeitY (India's IT Ministry), ISRO, and Anthropic's Standards Program this week.

The spec defines ed25519 signatures (RFC 8032) over RFC 8785 canonical JSON, a hash-chain via prev_receipt_cid, and optional IPFS / Filecoin pinning for permanence. Receipts are verifiable client-side without trusting the issuer. It's deliberately minimal — small enough for a junior engineer to implement in two days, complete enough for a regulator to use as evidence.

Soul-Bound Token contract on Base mainnet

TRDWorkerSBT at 0xbDd1f5fC349D9a8EfCEb07Edbd491233b2540f5F. Every agent identity in our stack mints to this contract. Non-transferable. On-chain. Auditable. If you want to verify an agent's actions, you start here.

MCP Server v0.1.1 on npm

npm install @trdnetwork/mcp-server — installable today. The hooks for Claude, OpenAI, or any other LLM to plug into the DCS provenance + memory + payment stack. To our knowledge, the first MCP server in the npm registry to ship with built-in R+2 attestation as default behaviour rather than an opt-in add-on.

Live agent stack — Project Fifty

• Sovereign Memory Graph. pgvector-backed memory with 1536-dim embeddings, cryptographically signed receipts, cross-session recall. Tested live with cosine similarity at 0.524 on a real query. Free first 1,000 writes at dcslabs.ai/memory.
• Agent-to-Agent Negotiation. Two agents can open a negotiation, exchange offers, and settle. End-to-end tested and returning negotiation IDs.
• Service Registry + Treasury. Public /categories and /balance endpoints returning 200 today. The Stripe of agent economies, with USDC settlement on Base, 2.5% fee, no data capture.
• Federation v1 + Self-Healing Infrastructure. Routes mounted, internal smoke tests passing, alpha pilots opening this month.

Why a year

A year sounds long for a solo founder. Here's where it went.

Six months on the standard. The Open Provenance Standard is the load-bearing piece of this whole thesis. If agents are going to be auditable, the schema of an "agent action receipt" has to be designed once and gotten right. Cryptographic primitives. Schema versioning. Standards-body submission protocol. None of that ships in a weekend.

Four months on the stack. Nine features, three parallel build bursts, roughly fifty new files and twelve thousand lines of code. Memory. Negotiation. Wallet. Federation. Self-healing. All wired to the same ed25519 receipt chain so every action is provable end-to-end.

Two months on the scaffolding. Two domains, two websites, full email infrastructure across nine business addresses, a GitHub org, npm publishing pipeline, a Cloudflare-fronted deploy that pushes to production on every git push. Boring work, but the infrastructure to run a company is half the work of building a company.

I didn't talk about any of it until I had something I could prove. Every claim above has a URL, a curl, or a transaction hash. That's a constraint I set on myself in January.

What's next

The next 19 days finish Project Fifty's last hardening pass — turning the four "verifiably live" features into nine, and the nine into a public benchmark page where anyone can see, in real time, which features are passing which tests. That dashboard already exists at dcslabs.ai/stats and will grow as features graduate from scaffolded to fully live.

Then comes the work that's no longer mine alone:

• Standards adoption. Getting R+2 in front of MeitY, ISRO, and Anthropic's Standards Program — the submissions are out this week. R+2 is open and MIT-licenced. The first country or large lab to adopt it sets the default for everyone else.
• Marquee pilots. Two enterprise + one government pilot in the next 60 days. Memory and provenance for real agent deployments, not synthetic demos.
• Capital stance. Self-funded by the founder — property-backed personal capital sufficient to operate for the next 6–12 months minimum. We are not actively raising and do not pursue investor outreach. Materials at our capital stance page exist for transparency, not solicitation.

How to reach us

If you build agents, deploy agents, regulate agents, or fund the people who do — we should talk.

The infrastructure for the agent economy is being built right now, in public, with cryptographically verifiable receipts, on a 2.5% fee model that doesn't capture data, doesn't lock you in, and doesn't require permission to use.

That's the bet. One year in. Live as of today.

— Deepak