Open Source

Standards and tools Synapti publishes

Most of the work ships as open source first. A tool gets productized only when hosting it for others is the right move. The reasoning: standards beat closed verdicts, audits beat assertions, and a working community of practice beats a brochure. Every project here is published under an open licence and maintained in the open. Everything below lives at github.com/synaptiai.

Standards

Open specifications. Anyone can implement, contest, or extend.

  • UIM Protocol

    Spec stable 39

    Standardized way for AI agents to discover and execute intents against web services. Defines a unified vocabulary for intents, metadata, and execution methods, plus an ODRL-based policy layer for permissions and rate limits. The missing layer between agents and APIs.

    github.com/synaptiai/uim-protocol
  • Agent Capability Standard

    Active 4

    An open specification for composable AI agent capabilities. 36 atomic capabilities across 9 cognitive layers, a type-safe workflow DSL, and grounded world modeling with trust-aware conflict resolution. Built on the Grounded Agency philosophy: agent reliability becomes structural, not optional.

    github.com/synaptiai/agent-capability-standard
  • Influence Tactics Protocol

    Active 1

    Open standard for detecting and scoring manipulation in online content. 20-category framework across 5 composite factors. The substrate Decipon runs on. Anyone can implement, contest findings, or extend the framework.

    github.com/synaptiai/influence-tactics-protocol
  • Multi-Agent Constitutional Architecture

    RFC

    A four-layer governance architecture for multi-agent AI systems. Authority boundaries, escalation, and constitutional review applied to ensembles where naive agent autonomy produces drift, conflict, or runaway behavior.

    github.com/synaptiai/multi-agent-constitutional-architecture

Tools

Production code. Plugins, kits, and engines you can install today.

  • Synapti Marketplace

    Active 6

    Curated collection of Claude Code plugins for AI-augmented development plus advanced analytical and research tasks. Each plugin ships specialized agents, skills, and commands for a specific domain. The umbrella distribution channel for the Claude Code work published here.

    github.com/synaptiai/synapti-marketplace
  • Prompt Decorators

    Active 43

    A standardized framework for enhancing how LLMs process and respond to prompts through composable decorators. Ships an open standard, a Python reference implementation, and an MCP server that brings decorator behavior into Claude Desktop and other MCP-aware clients.

    github.com/synaptiai/prompt-decorators
  • BDSK

    Active

    Behavior-Driven Specification Kit. Specification-first governance for AI-assisted code generation. Eight-phase validator, lifecycle skills, and scope enforcement. Test-before-code, uncertainty documentation, multi-pass verification.

    github.com/synaptiai/bdsk
  • Lucid

    Active

    Open-source epistemic audit for Claude conversation history. Applies eight published AI-safety research frameworks (Spiral-Bench, Sharma sycophancy, SycEval, BeliefShift, ITP, MedTrust-RAG) and produces citation-validated HTML reports. For users who want to know whether their assistant is drifting toward sycophancy.

    github.com/synaptiai/lucid
  • SIARE

    Experimental 1

    Self-Improving Agentic RAG Engine. Evolves multi-agent RAG pipelines using quality-diversity optimization (Map-Elites) and topology search. Lets the pipeline find its own better shape rather than requiring humans to enumerate candidate architectures.

    github.com/synaptiai/siare
  • flow-harness

    Active

    Provider-neutral coding-agent harness built on deterministic workflow graphs, durable evidence, and fail-closed sandboxed execution. For anyone running coding agents, that means a run either produces a verifiable record of what happened or it does not run at all, and swapping the underlying model provider does not change how the workflow behaves.

    github.com/synaptiai/flow-harness

Licensing

Standards and protocols sit under permissive licenses so adoption is not gated on negotiation. Tools and code sit under licenses that match how they get used: MIT for libraries you embed, Apache for tooling that touches your CI, CC BY-SA for written methodology like the playbooks. The license is in each repo, and it is not a formality.

See the long-form open methodology →