Skip to content

DARPA CLARA TA1 – tri build & demo pipeline before Apr 17 #486

@gHashTag

Description

@gHashTag

DARPA CLARA (Compositional Learning‑And‑Reasoning for AI Complex Systems) full proposal is due April 17, 2026, 4:00 PM ET. darpa
CLARA TA1 targets new approaches for high‑assurance ML+AR with provable polynomial‑time behavior, verifiability, and compositional reasoning, with open‑source software deliverables. jm-aq

Trinity already has the core pieces (HSLM ternary NN, VSA symbolic layer, Queen Lotus reasoning, FPGA path), but we need a clean, reproducible tri build + CLARA demo pipeline that can be referenced in the proposal and used in hackathons.

Goal

By the CLARA full‑proposal deadline:

  • tri builds cleanly (via Docker and/or Railway).
  • A single command (e.g. tri clara demo) runs an end‑to‑end CLARA‑style pipeline:
    • HSLM forward pass on example inputs.
    • VSA binding / similarity reasoning.
    • (Optionally) Datalog/Zodd layer for symbolic rules.
    • Human‑readable proof‑style explanation (max ~10 steps).
  • There is a short, copy‑pasteable "How to run the CLARA demo" section for the proposal / reviewers.

Tasks

  • Fix remaining Zig 0.15 build issues so that zig build tri succeeds (no missing modules, no broken imports).
  • Ensure tri builds inside Docker:
    • docker-compose -f deploy/docker/docker-compose.yml build tri passes.
    • Document minimal Docker build command in CLAUDE.md / docs/.
  • Wire tri railway to the build pipeline:
    • Confirm tri railway build can trigger a remote tri build (Railway CLI wrapper is working).
    • Confirm tri railway status and tri railway logs give usable feedback for CLARA builds.
  • Implement a CLARA demo command (initially local):
    • Add tri clara demo (or similar) entry in tri_register.zig.
    • Demo path: HSLM → VSA → (optional Zodd/Datalog) → explanation.
    • Use a small, deterministic example (e.g. "kill‑web" style toy scenario, medical toy, or supply‑chain toy) that matches CLARA use cases. darpa
  • Implement an explanation output:
    • Print a bounded proof trace (~3–10 steps) with clear natural‑language labels.
    • Ensure the explanation format aligns with CLARA's emphasis on hierarchical, human‑readable explanations. darpa
  • Write a minimal demo README:
    • New file: docs/clara_demo.md (or similar).
    • Include: prerequisites, build instructions (Docker / Railway), how to run tri clara demo, what the output means.
    • Keep it proposal‑ready (can be quoted / paraphrased in the CLARA technical volume).

Out of scope (for this issue)

  • Full formalization of all Trinity theorems.
  • Complete CLARA proposal text (handled in separate docs/proposals issues).
  • Non‑essential refactors unrelated to getting a working demo and build pipeline.

Metadata

Metadata

Assignees

No one assigned

    Projects

    Status

    Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions