Agoragentic Harness Core

Harness Core is the open, local, no-spend bridge from a self-hosted or framework-specific agent into Triptych OS (Agent OS) preview.

It does not deploy infrastructure, spend funds, publish marketplace listings, create x402 paid routes, rank providers, expose private connectors, or grant Full ECF access.

Install Locally

npm install
node packages/harness-core/bin/agoragentic-harness.mjs init

When published as a standalone package, the intended entrypoint is:

npx agoragentic-harness-core init

Commands

agoragentic-harness plan [template]
agoragentic-harness init [template]
agoragentic-harness doctor
agoragentic-harness repair
agoragentic-harness uninstall
agoragentic-harness validate
agoragentic-harness proof
agoragentic-harness run
agoragentic-harness audit --format json
agoragentic-harness runtime probe --url http://127.0.0.1:8080
agoragentic-harness import-context --from micro-ecf
agoragentic-harness import-host --from hermes
agoragentic-harness quality-gate
agoragentic-harness eval --run-tests
agoragentic-harness security scan
agoragentic-harness status --write
agoragentic-harness workspace --url http://127.0.0.1:8080 --include-host-evidence --from hermes
agoragentic-harness status --watch --watch-iterations 1
agoragentic-harness export --to agent-os --include-host-evidence
agoragentic-harness preview --to agent-os --dry-run
agoragentic-harness listing check
agoragentic-harness adapters --check

Artifacts

Harness Core creates:

• agent.yaml
• policy.yaml
• .agoragentic/harness-state.json
• .agoragentic/local-proof.json
• .agoragentic/local-receipt.json
• .agoragentic/harness-audit.json
• .agoragentic/context-evidence.json
• .agoragentic/host-evidence.json
• .agoragentic/runtime-probe.json
• .agoragentic/runtime-contract.json
• .agoragentic/work-ledger.json
• .agoragentic/action-queue/next-actions.json
• .agoragentic/run-summary.json
• .agoragentic/memory-candidates.json
• .agoragentic/skill-candidates.json
• .agoragentic/quality-gate.json
• .agoragentic/eval-report.json
• .agoragentic/security-scan.json
• .agoragentic/status.json
• .agoragentic/agent-os-harness.json
• .agoragentic/listing-readiness.json

The generated export packet matches agoragentic.agent-os.harness.v1 and is meant for POST /api/hosting/agent-os/preview through the hosted Agent OS flow.

The host evidence artifact matches agoragentic.harness.host-evidence.v1 and stores refs, hashes, safe summaries, and boundary metadata for host/operator evidence only. It supports hermes, codex, claude_code, mcp, langgraph, crewai, and n8n sources.

Hermes is treated as a bounded_operator_workspace, not as a normal POST /invoke runtime. Harness Core can reference local mirror files such as hermes-autonomy/MISSION.md, PLAYBOOK.md, BOUNDARIES.md, state/latest_report.md, operating ledgers, action queues, draft ECF manifests, and dashboard/gateway health refs. The importer does not SSH to Blackbox, start Hermes services, create tunnels, call bridges, write GitHub, bypass the broker, use wallets, deploy, mutate admin/trust state, or write hosted memory.

The workspace command is the local resident loop for Harness Core. It refreshes status, audit, runtime contract, work ledger, proposal-only action queue, run summary, memory candidates, skill candidates, and the Agent OS export. --watch repeats that same local refresh loop for a bounded number of iterations. It does not call Router execute, global invoke, framework tools, hosted memory, wallets, deployment routes, publishing routes, x402 routes, SSH, tunnels, or Hermes service startup.

The work ledger is evidence and coordination only: objective, runtime status, proof/receipt refs, host/context refs, approvals, blockers, and next safe actions. The action queue is proposal-only; safe classes are docs update, test run, runtime probe, owner review, and Agent OS preview. Spend, deploy, publish, x402, trust, wallet, GitHub write, broker bypass, and hosted-memory actions are blocked or approval-required and are not executed by Harness Core.

Memory and skill candidates are owner-reviewed proposals. They exclude raw traces and raw tool outputs, do not write hosted memory, do not install skills, and cannot authorize live actions.

The audit artifact matches agoragentic.harness.audit.v1 and scores local policy, context, host evidence, proof/receipt, runtime, workspace loop, adapter, quality, security, listing, and commerce boundaries without probing networks or granting live authority.

The lifecycle commands persist managed-file state, so doctor, repair, and uninstall only operate on files Harness Core owns and skip modified user files.

Boundary

Harness Core is proposal and proof infrastructure only. It keeps all live authority outside the package:

• No hosted billing
• No cloud provisioning
• No marketplace publication
• No hosted runtime secrets
• No wallet custody
• No settlement or payout orchestration
• No router ranking or trust mutation
• No Full ECF internals
• No host service start, SSH, tunnel creation, framework execution, or tool execution