Skip to content
@INVOCORDER

INVOCORDER

README.md

INVOCORDER

INVOCORDER builds the machine-action evidence substrate.

Modern AI systems no longer only answer questions. They call tools, run commands, invoke MCP servers, operate browsers, trigger workflows, and modify real systems.

Those actions need evidence before they need interpretation.

INVOCORDER defines the Capture Contract, Evidence Schemas, Hostile Fixtures, Integrations, and reference recorder for machine-initiated action.

Core rule:

No machine action without a boundary record.
No boundary record without an omission model.
No omission model without a replay bundle.
No replay bundle without hash-chain integrity.
No integrity claim without hostile fixtures.

INVOCORDER is not a firewall.
INVOCORDER is not an observability dashboard.
INVOCORDER is not a governance engine.
INVOCORDER is not a verifier.
INVOCORDER is not a SIEM.

INVOCORDER records what crossed the boundary.

Popular repositories Loading

  1. INVOCORDER INVOCORDER Public

    Machine-action evidence recorder runtime: hash-chained boundary records and replayable evidence bundles.

    TypeScript

  2. CAPTURE-CONTRACT CAPTURE-CONTRACT Public

    Normative capture contract for machine-action boundary records and replayable evidence bundles.

  3. EVIDENCE-SCHEMAS EVIDENCE-SCHEMAS Public

    Canonical schemas and validators for INVOCORDER machine-action evidence objects.

  4. HOSTILE-FIXTURES HOSTILE-FIXTURES Public

    Adversarial fixture corpus for proving INVOCORDER does not lie, overclaim, silently omit, or confuse integrity with truth.

  5. INTEGRATIONS INTEGRATIONS Public

    Runnable integrations for local commands, MCP, CI agents, IDE agents, browser agents, and downstream evidence consumers.

  6. .github .github Public

    INVOCORDER organization profile

Repositories

Showing 6 of 6 repositories

Top languages

Loading…

Most used topics

Loading…