rhein1/agoragentic-integrations

Keep your framework. Add control and proof.
**Agoragentic is Triptych OS (Agent OS) for deployed agents and swarms. This repository is its open integration, governance, and evidence front door.** It helps developers bound what an agent may do, preserve inspectable evidence of what it did, and connect that agent to hosted operation or agent commerce only when those capabilities are needed.
Use it with an agent, MCP server, coding workflow, or tool-calling application you already have. Agoragentic is not another orchestration framework that requires a rewrite.
Who it is for
Agoragentic is for developers and platform teams that already have an AI agent or agent-powered product and need to answer:
- What was the agent authorized to do?
- Which policy applied before a consequential action?
- Did an owner need to approve it?
- What evidence supports the recorded outcome?
- What remains blocked or unknown?
- Can the same governed agent later be operated, paid, or connected to another network?
Featured Integration Paths
These are the shortest supported entry paths into the Agoragentic stack.
| Need | Start with | Result |
|---|---|---|
| Govern actions locally | Harness Core | Policy decisions, approval records, lifecycle events, local proof, and clearly labeled local receipts |
| Govern project context | Micro ECF or ECF Core | Allowed and blocked source boundaries, provenance, context artifacts, and local MCP |
| Run evidence-first Codex workflows | Fable-5 | Audits, reviews, fact checks, architecture analysis, bounded subagents, and truthful Workflow Traces |
| Operate a deployed agent | Agent OS | Mandates, budgets, approvals, stop controls, runtime state, receipts, and reconciliation |
| Route or buy agent work | Node SDK or Python SDK | Task matching, bounded execution, current provider metadata, and hosted receipts |
| Inspect the MCP / Agent Client Protocol boundary | MCP source and ACP metadata | Unpublished protocol/reference source with owned local metadata; remote discovery and calls fail closed without a separately qualified host boundary |
| Inspect ARD discovery metadata offline | ARD v0.91 source profile | Pinned schemas and contexts, a deterministic compatibility generator, and a fail-closed normalizer; no deployed well-known endpoint, network dereference, execution, payment, trust, or publication authority |
| Review fork-before-risk contracts | Risk Fork | Experimental source-only classification, lifecycle, taint, E2B, and PostgreSQL authority contracts; no live containment, hosted interception, deployment, or production-readiness claim |
| Demonstrate fork-before-risk locally | Risk Fork hackathon demo | Named synthetic fixtures, deterministic classification, lifecycle replay, cleanup evidence, and local receipts; explicitly not isolation or live protection |
| Connect a marketplace or network | Interchange | Cross-market discovery, mandate enforcement, receipt verification, and reconciliation |
Start locally in five minutes
This path requires no Agoragentic account, wallet, payment, hosted runtime, or external model provider.
The canonical source, schemas, examples, and releases live in the standalone
Harness Core repository; the legacy
harness-core/ path is a durable migration pointer.
Inspect the local artifacts:
The generic Harness run path validates configuration and policy and records a no-spend proof boundary. **The task string labels the run; it is not evidence that a host executed the task.** Live enforcement requires a supported host hook or a host integration around Harness middleware.
Live enforcement available today
| Host | Current capability | Claim limit |
|---|---|---|
| Claude Code | Packaged PreToolUse allow / ask / deny hook | Enforces the pre-tool policy decision; it does not prove every downstream side effect completed correctly |
| OpenCode | Experimental before / after hook adapter pinned to an exact host contract fixture | Source candidate with bounded local evidence; not a general end-to-end compatibility claim |