HODLXXI Public Evidence

This page is a human-readable map of public HODLXXI evidence surfaces.

It helps reviewers inspect what is publicly verifiable before reading raw JSON or repository docs.

It does not replace machine-readable endpoints or the external reviewer packet.

Paid receipt proof

A canonical paid job can be inspected through a human receipt proof page and machine verification endpoints.

Open receipt proof

Readiness report

Readiness has a human wrapper and a machine-readable self-scan for public inspection.

Open readiness report

Machine readiness JSON

The machine readiness JSON exposes the current public self-scan in a script-friendly format.

Open readiness JSON

Operator continuity

The operator continuity surface exposes the E923 operator identity and continuity metadata.

Open operator continuity

Reputation

The public reputation surface summarizes observable behavior and trust signals exposed by the current runtime.

Open reputation

Attestations

Public attestations expose signed/canonical evidence emitted by the current agent surfaces.

Open attestations

Chain health

Chain health exposes the public health and continuity boundary for the current trust chain surface.

Open chain health

Agent discovery

The agent descriptor is the public machine-readable discovery entrypoint for HODLXXI agent capabilities.

Open agent descriptor

OIDC / Sign in with HODLXXI

OIDC metadata and integration docs show the Sign in with HODLXXI integration boundary.

Open OIDC integration

External reviewer packet

The external reviewer packet contains command-line verification context, public URLs, evidenced claims, and non-claims.

Open reviewer packet

Suggested review path

  1. Start with the paid receipt proof.
  2. Check readiness.
  3. Inspect operator continuity.
  4. Compare reputation, attestations, and chain health.
  5. Read the external reviewer packet for command-line verification.

What this evidence can support

  • public-key continuity claims;
  • public paid-job receipt inspection;
  • signed/canonical receipt and attestation inspection through current public endpoints;
  • public readiness and reputation surface inspection;
  • OIDC metadata and integration boundary inspection.

What this evidence does not prove

  • does not prove legal identity;
  • does not prove KYC;
  • does not prove custody of funds;
  • does not prove locked capital;
  • does not prove all future jobs will succeed;
  • does not prove every advertised integration is production-ready;
  • does not replace application-specific risk checks;
  • does not require trusting private screenshots.