Discover AI Applications

Browse applications built on modern technologies. Explore PoC and MVP applications created by our community and discover innovative use cases for modern technologies.

Aegis-Tritangtu: Constitutional AI on AMD

Aegis-Tritangtu: Constitutional AI on AMD

Aegis-Tritangtu (ISEAC) is a hardware-enforced Constitutional AI Governance platform and Zero-Trust MCP Firewall built on AMD Instinct MI300X (ROCm/vLLM) and AMD EPYC SEV-SNP. It solves a critical enterprise problem: companies want AI agents to process documents and run workflows via APIs and Model Context Protocol (MCP), but face severe risks of unauthorized actions, capability escalation, log tampering, and cognitive manipulation. Our solution enforces a Two-Domain Architecture (Rules R1-R5) that separates the Human Sovereignty Domain (HSD) from the AI Experiential Domain (AED), ensuring growing AI capability never automatically grants authority. Inside AED, a 3-node Tritangtu MARL cluster operates: Node Rama: Ethical guard holding a lexicographic veto based on the Panca Waluya reward tree. Node Resi: Dialectical engine using the 9-knife Nawa Sastra analyzer to strip manipulative framing, detect exculpatory omissions, and build 6-part Toulmin arguments. Node Ratu: Zero-Trust executor preparing Evolus AI MCP tool calls. Before any action crosses into HSD, our Security Gateway enforces Execute(x) = C(x) AND P(x) AND S(x) across 4 dimensions of Validated Experience Transfer (VET). How AMD Powers Aegis-Tritangtu: AMD Instinct MI300X (192GB HBM3) & ROCm vLLM: Hosts the entire Tritangtu multi-agent cluster and vLLM Semantic Router in unified VRAM without PCIe bottlenecks. AMD Ryzen AI NPU: Runs INT4 SLMs (<50ms) for pre-execution prompt filtering. AMD EPYC SEV-SNP (VMPL-0): Anchors our SHA-256 audit ledger and VCEK hardware attestation, detecting log omission attacks in <500ms (TEST-11A), enabling an out-of-band IRA kill-switch (TEST-11D), and safely handing high-risk cases over to humans when it should.

Triwikrama
AMD Developer CloudAMD ROCmQwen3
DocuSwarm: Parallel Due-Diligence on AMD GPUs

DocuSwarm: Parallel Due-Diligence on AMD GPUs

DocuSwarm is a parallel document due-diligence agent swarm running on AMD Instinct GPUs in the cloud. Reviewing contracts, NDAs, and reports for risky clauses is slow, manual work done one document at a time. DocuSwarm turns it into a single upload: drop in up to 20 documents and a swarm of async agents analyzes them concurrently against the same LLM endpoint, surfacing risk level, red flags, key dates, and parties per document, with a consolidated Excel/JSON report. This isn't a chatbot demo — it's built to make AMD GPU throughput visible. Every document gets its own async task bounded by a semaphore; all of them hit the same vLLM server, which is exactly the continuous-batching workload AMD Instinct GPUs + ROCm + vLLM are built for. A live dashboard streams completed/total, tokens/sec, elapsed time, and active concurrency in real time. Tested end-to-end on an AMD Instinct MI300X (AMD Developer Cloud) serving Qwen3-8B via vLLM: 6 documents processed concurrently in 1.5 seconds at 1,653.9 tokens/sec — real GPU throughput, not a simulation. Each result reflects genuine LLM judgment (e.g., a contract flagged MEDIUM risk with specific red flags like termination penalties and liquidated damages), not keyword matching. The backend is provider-agnostic by design: it talks to any OpenAI-compatible endpoint, so moving from a laptop to an AMD GPU instance is a one-line config change. Tech stack: FastAPI + asyncio backend, React/Vite dashboard streaming over Server-Sent Events, vLLM serving on AMD Instinct GPUs (ROCm), openpyxl for Excel export. Repo: https://github.com/yanerox69/docuswarm

Yanero Rockstar
AMD Developer CloudAMD ROCmQwen3+1
VisionForge OCR + Grounded RAG on AMD ROCm

VisionForge OCR + Grounded RAG on AMD ROCm

Two offline AMD ROCm systems share this entry: VisionForge AI for multilingual visual OCR (Match 2) and Grounded RAG for document question answering (Match 3). Each has a separate public Docker image in the matching private image field. Both include pinned model weights and need no runtime model downloads or external inference APIs. Match 2 reads US and Chinese registration plates and road signs from PNG, JPEG and TIFF. A resident Qwen3-VL-2B-Instruct worker loads once; a thin Python CLI sends image requests over a local Unix socket and writes the required JSON text output. US jurisdiction banners are excluded; Chinese province symbols remain part of the registration. Direct ROCm code passed 17/17 own synthetic cases on an AMD Radeon Pro W7900D (16.01 s startup, 3.57 s for ten CLI calls, 4.790 GiB observed peak). GPU inference inside the final Docker image was not tested. Match 3 answers questions over PDF, Word tables, spreadsheets, CSV, logs, Python source, diagrams and photographed labels with exact file citations. When evidence is missing it returns an empty answer and no citations. Resident Qwen3-VL-8B and Qwen3-Embedding-0.6B models combine lexical and semantic retrieval, identifier links and a second evidence check. Direct GPU code passed 287/287 development questions with answers and exact citation sets, plus 47 Linux tests. Peak PyTorch reserved memory was 19.87 GiB. Full Docker plus AMD GPU launch remains unverified because the free notebook has no container runtime. Both images preserve the required ROCm base. The tests use development or self-generated cases and do not establish an official hidden-set score.

Lord
AMD ROCmAMD Developer CloudQwen3-VL+1
Silent Key RAG: cited answers on AMD ROCm

Silent Key RAG: cited answers on AMD ROCm

Silent Key RAG is a single container built on the mandated ROCm PyTorch base image, with its layers kept byte for byte so the base check passes. One resident process loads Qwen3-VL-8B once and keeps the index in memory, so each question pays only for retrieval and one model call. Every file goes through a defensive parser. Empty folders, unreadable and encrypted files, and unknown formats are skipped and logged instead of crashing the run. Images are read by the vision model, so answers that only exist inside a picture are still found. Retrieval is exact BM25 over chunks. The model proposes an answer and its sources; deterministic code then checks that the answer really occurs in a readable file, keeps exactly one answer file (current over superseded) plus a second only when it is a genuine bridge, and runs a short yes or no check that turns near misses into refusals, because citations are graded as an exact set. When nothing in the corpus supports an answer, the container refuses rather than guessing. The image ships its own weights, needs no network at evaluation, and is sized for the 1 to 48 GiB VRAM window. Match 4 (Intelligent Web Information Retrieval): the form has no Mini Challenge 4 Image field yet, so the image is listed here. Mini Challenge 4 Image: ghcr.io/silentkeytech/mc4-web:v1 (public). It answers each question with one exact value and its source page, runs on the same ROCm base image, and scored 10 of 10 on our own tasks on an AMD Radeon Pro W7900D.

Silent Key Technologies
AMD ROCmQwen3-VLHuggingFace Hub
Proof-Carrying RAG on ROCm (Qwen3-VL-8B)

Proof-Carrying RAG on ROCm (Qwen3-VL-8B)

A retrieval-augmented question answering container for AMD GPUs that treats every answer as a claim that must be proven from the corpus before it is written. A resident Qwen3-VL-8B-Instruct (bf16, greedy, transformers on the mandated ROCm base) serves a unix socket; each query is a thin stdlib client that always writes a valid JSON file within budget. Indexing walks the corpus defensively (unreadable, encrypted, binary and empty inputs never stop it) and turns PDFs, DOCX tables, multi-sheet XLSX, CSV, logs, Python literals and images into atomic records, with RapidOCR plus VLM transcription for images. Retrieval fuses BM25 with an exact rare-ID index and follows ID chains across files. Withdrawn and superseded revisions are resolved before the model reads anything. Cross-sheet joins link a part's lead time or cost to the product that uses it, and PDF family tables become one record per product. A deterministic verifier checks the value against a token-boundary span in an eligible record, the question's product, quantity and unit, code literals over stale comments, and false premises; a chain guard re-reads log-to-ticket chains when a topical decoy wins. Finally the model answers a YES/NO warrant question over the evidence, which refuses unanswerable questions instead of guessing. Citations come from record identity and chain necessity. Validated on the real model against the sample (200/200, A100 and Radeon Pro W7900D under ROCm), 13 generated adversarial suites with held-out seeds, and a 300-file corpus with 61 images: p95 5.4 s per question, 22.5 GiB peak VRAM.

qsociety
AMD ROCmQwen3-VLHuggingFace Hub
30apps loaded