FeedOracle Action Gate Phase 1 — Dry-Run

Agent-control layer placed between autonomous AI agents and real systems. Every agent action passes through 9 independent safety layers, requires operator approval for anything outside the sandbox, and produces a cryptographically signed, hash-chained receipt that any third party can verify without our cooperation.

Verify any FeedOracle receipt yourself in 3 commands

# 1. Download the verifier (multi-key aware)
curl -O https://feedoracle.io/.well-known/verify-academic-receipt.py

# 2. Install the dependency
pip install cryptography

# 3. Verify any receipt — script picks the correct public key from the manifest
python3 verify-academic-receipt.py path/to/receipt.json

Exit codes: 0=valid · 1=sha256 mismatch · 2=signature/pin invalid · 3=fetch error. For audit-grade pinning use --expect-fingerprint SHA256:... from the key manifest.

What is documented here

Audit Briefing
Single-document overview for external auditors — architecture, receipt schema, compliance anchors, transparent open-items list, verification instructions.
Agent Integration Guide
For developers building agents that go through the gate. Proposal schema, error semantics, retry guidance, end-to-end examples.
Architecture & Receipt Schema
The 9 layers, signing infrastructure, hash-chain semantics, schema versions 0.1 / 0.2 / 0.3.
Phase Status Documents
Build log entries for every phase. Each curation walkthrough has its own status doc with chain-id, receipt-id, test results, and rollback evidence where applicable.

Current state (2026-05-10)

Audit chains	59 (all VALID)
Receipts	105 (all sha256 valid)
ECDSA-signed	47 (key v1: 46, key v2: 1+)
Chain integrity issues	0
Curation walkthroughs completed	6 (different change-types)
Auto-rollback events in production	3 (all recovered to clean state)
Active signing key	academic_l1_v2 (since 2026-05-10)
Kill-switch state	OFF (default — phase 1 is dry-run)

Trust model

Public keys are self-published at /.well-known/ on this domain. Trust is anchored in (a) the TLS certificate of feedoracle.io, and (b) out-of-band fingerprint pinning recorded in the manifest's rotation history. There is no CA chain. For long-term verification (audits years later), record the fingerprint of each key version once and pin it — the URLs may move, the fingerprints do not.

Contact: support@feedoracle.io