WARRANTthe team behind warrant.
a small team building attestation infrastructure for AI agents in regulated industries. solo founder today, hiring with discipline. four collective personas, one accountable founder, one public register.
the roster.
solo · 4 bylinesauthor bylines below are content-category labels, not separate people. vivek is accountable for every artefact.
| persona | scope | accountable as |
|---|---|---|
warrant compliance authors regulator-facing copy and citation policy |
article-level mapping for EU AI Act, SR 11-7, NYDFS Part 500, FCA Consumer Duty, RBI FREE-AI, SEBI Retail Algo, India DPDP, MAS AIRM/FEAT. | collective |
warrant engineering authors the evidence engine and the public verification surface |
FastAPI · Supabase · Render. each record is independently verifiable without contacting Warrant. a deterministic evidence engine, by design. | collective |
warrant editorial authors voice, microcopy, and the changelog |
court-document register. lowercase first person. no em-dashes. coverage we do not hold, we do not claim. | collective |
warrant research authors the regulator atlas and the threat model |
tracks new circulars, supervisory letters, and committee reports. the atlas at /regulators is the public artefact of this work. | collective |
vivek kumar solo founder · accountable for every persona |
previously CRED (lending stack), Vance (cross-border money), Partnr (B2B). spectra was the warrant ancestor at the Anthropic Hackathon 2025. | accountable founder |
what we will not do.
principles · 5a smaller, more useful list. things we have publicly committed not to do, with consequences if we fail.
engineering · a deterministic evidence engine
the evidence engine is deterministic by design. the same trace produces the same record. every record is a tamper-evident artefact mapped to a specific obligation, independently verifiable without contacting Warrant.
engineering · no SDK install for verification
verification is a public URL. every record is independently verifiable without contacting Warrant. anyone, anywhere, with any tool. warrant.build/verify. no auth, no key, no SDK.
audit · no compliance certification claims today
SOC 2 Type II, ISO 27001, GDPR DPA, HIPAA BAA are on the roadmap, post design-partner cohort. the /trust page lists what we don't yet hold and the timeline we have committed to.
brand · no "AI-powered" copy
the artefact is a court document. the language is the regulator's, not the marketer's.
brand · no anonymous brand
the founder is named. the bylines are named. the public register names the person accountable for every record. there is no "the warrant team" hiding from a refused filing.
architectural ancestry.
spectra → warranthow warrant emerged from spectra, the prototype vivek built at the anthropic hackathon 2025. the discipline carried over. the implementation simplified.
spectra was vivek's prototype. it emitted a structured artefact you could verify without contacting the author. court-document register. it worked. it also carried more ceremony than the warrant brief required.
warrant inherited the discipline and dropped the ceremony. the implementation collapsed into a deterministic evidence engine. the same trace produces the same record. the artefact it emits is tamper-evident and independently verifiable without contacting Warrant.
warrant collapsed that into a deterministic evidence engine. the same trace produces the same record, every time. the outcome: a tamper-evident record mapped to a specific EU AI Act obligation, independently verifiable without contacting Warrant.
operating principles.
5 · how we workthe discipline warrant operates by. each principle is checkable against the artefact, the repository, or the changelog.
01 · cite primary sources, not paraphrases
every blog post links the canonical regulator URL · EUR-Lex for EU AI Act, dfs.ny.gov for NYDFS Part 500, federalreserve.gov for SR 11-7, rbi.org.in for RBI FREE-AI, sebi.gov.in for SEBI Retail Algo. paraphrase is fine in the body; the citation row carries the verbatim text and the canonical link.
02 · verify before publish
the 200-trace eval suite runs on every commit. citation precision must stay ≥ 99% to merge. a regression in the suite blocks the merge regardless of how visible the change is. the eval is the gate, not a metric.
03 · refuse rather than soften
if a regulator citation cannot be substantiated by the trace, the map stage refuses. no record is issued. coverage we do not hold, we do not claim. the refusal is surfaced as a written reason in the receipt, not as a softened mapping.
04 · names over abstractions
warrant compliance, warrant engineering, warrant editorial, warrant research are content-category bylines. they are not anonymous teams. vivek is accountable for every artefact. the public register at /signing-officers names the person behind every record.
05 · no silent assumptions
the record surfaces, on every artefact, what was checked, what was missing, and what was refused. an inconclusive map step is recorded as inconclusive, not omitted. an action without sufficient context is flagged before the assess step decides anything about it.
what is coming next.
v0.4 → v1the roadmap below is what we have committed to in writing. nothing on it changes what a record is: a deterministic, tamper-evident artefact, independently verifiable without contacting Warrant.
the founder.
vivek kumari'm vivek. i built lending infrastructure at CRED, cross-border money rails at Vance, and a B2B operations product at Partnr.
Spectra was the architectural prototype: structured output you could verify without contacting the author, court-document register. warrant inherited the discipline. the implementation simplified into a deterministic evidence engine, with less ceremony.
x · @vivekonai
email · [email protected]