Resources

Reference material for evaluation and verification.

Public resources show structure and boundaries. Controlled documents are available to qualified reviewers under appropriate confidentiality terms.

All
Briefs
Specs
TRD
Samples
Policies
Legal
FAQ
Browse library Sample artifacts Glossary FAQ

Library

Documents commonly requested during evaluation and institutional review.

Brief PDF · Controlled
Executive brief

Framing, boundaries, governance posture, roadmap state, and disclosure model.

Request access V2026.02.19
Brief PDF · Controlled
IP / technical brief

Mechanics chain, canonicalization, sealing, disclosure tiers, verification procedure.

Request access V2026.02.19
Brief PDF · Controlled
Operational brief

Integration patterns, chain-of-custody workflow posture, review board orientation.

Request access V2026.02.19
Brief PDF · Controlled
Minimal disclosure brief

What CEYO is and is not, non-interference affirmations, operator responsibility boundaries.

Request access V2026.02.19
TRD PDF · Controlled
Technical requirements (Phase 1)

Build-ready requirements for Stages 1–3: intercept, canonicalize, seal, fail-open.

Request access V2026.02.19
Spec PDF · Controlled
Verification specification

Canonicalize, recompute hash, validate signature, confirm policy alignment. PASS/FAIL states.

Request access V2026.02.19
Spec PDF · Controlled
Capture policy & masking schema

Inclusion/exclusion rules, masking behavior, disclosure tiers, and policy versioning.

Request access V2026.02.19
Policy HTML · Public
Responsible use policy

Human rights and lawful use boundaries, operator obligations, prohibited deployments.

Open Public
Policy HTML · Public
Vulnerability disclosure

Reporting channel, safe harbor, scope, and coordinated disclosure expectations.

Open Public
Legal HTML · Public
Privacy

Public site collection, contact submissions, and boundary statements for deployment posture.

Open Public
Legal HTML · Public
Terms

Informational purpose, IP, disclaimers, limitation of liability, governing law.

Open Public
Samples JSON · Public
Sample artifacts & verification reports

Public examples showing artifact structure and verification outcomes (PASS/FAIL).

Open Public
FAQ HTML · Public
Frequently asked questions

Common questions from non-technical and institutional reviewers.

Open Public

Sample artifacts & verification reports

Public examples with redacted fields.

Public artifact sample
Artifact
Disclosure tier: public
{
  "artifact_id": "a1b2c3d4e5f6g7h8i9j0",
  "timestamp": "2026-03-08T14:30:00Z",
  "policy_id": "p_pub_v1",
  "policy_version": "1.2",
  "disclosure_tier": "public",
  "input_hash": "<REDACTED>",
  "output": {
    "decision": "Approve",
    "confidence": 0.95,
    "factors": ["<REDACTED>", "<REDACTED>", "<REDACTED>"]
  },
  "model_id": "<REDACTED>",
  "model_version": "<REDACTED>",
  "environment": "<REDACTED>",
  "hashing_algorithm": "SHA-256",
  "signature_algorithm": "ECDSA",
  "signature": "<REDACTED>"
}
Purpose: demonstrate structure without exposing proprietary or sensitive fields.
Verification report (PASS)
Verify
Overall: PASS
{
  "artifact_id": "a1b2c3d4e5f6g7h8i9j0",
  "verification_timestamp": "2026-03-08T15:00:00Z",
  "policy_id": "p_pub_v1",
  "policy_version": "1.2",
  "disclosure_tier": "public",
  "hashing_algorithm": "SHA-256",
  "signature_algorithm": "ECDSA",
  "verification_steps": [
    { "step": "Canonicalization", "standard": "RFC 8785", "result": "PASS" },
    { "step": "Hash Recomputation", "computed_hash": "e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855", "result": "PASS" },
    { "step": "Signature Verification", "result": "PASS" },
    { "step": "Policy Alignment", "result": "PASS" }
  ],
  "overall_result": "PASS - Artifact integrity confirmed"
}
Interpretation: integrity and provenance checks succeeded under declared policy scope.
Verification report (FAIL)
Verify
Overall: FAIL
{
  "artifact_id": "z9y8x7w6v5u4t3s2r1q0",
  "verification_timestamp": "2026-03-08T16:30:00Z",
  "policy_id": "p_pub_v1",
  "policy_version": "1.2",
  "disclosure_tier": "public",
  "hashing_algorithm": "SHA-256",
  "signature_algorithm": "ECDSA",
  "verification_steps": [
    { "step": "Canonicalization", "standard": "RFC 8785", "result": "PASS" },
    { "step": "Hash Recomputation", "computed_hash": "f6e0b1e2d3c4a5b6c7d8e9f0a1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d6e7f8a9b0", "result": "FAIL - Hash mismatch" },
    { "step": "Signature Verification", "result": "NOT ATTEMPTED" },
    { "step": "Policy Alignment", "result": "NOT ATTEMPTED" }
  ],
  "overall_result": "FAIL - Artifact integrity compromised"
}
Interpretation: hash mismatch indicates alteration or mismatch; signature checks are not meaningful after hash failure.
Verification steps Request walkthrough

Glossary

Key terms used throughout CEYO.

Artifact

A structured record generated at inference time under policy scope, intended for later verification.

Policy scope

Explicit inclusion/exclusion/masking rules defined before artifact generation.

Canonicalization

Deterministic serialization (RFC 8785) so equivalent structures yield identical bytes for hashing.

Sealing

Hashing and signatures applied to canonical bytes to enable tamper detection and provenance checks.

FAQ

Common questions for evaluators, operators, and institutional reviewers.

Integrity and provenance under declared policy scope: canonicalize → recompute hash → validate signature → confirm policy alignment. Verification does not confirm correctness, fairness, legality, or compliance conclusions.
No by default. Capture scope is policy-defined and can exclude proprietary internals. Disclosure tiers support verification without default exposure of weights or trade-secret implementation.
CEYO supports fail-open posture by default: inference continues, the failure is logged or flagged, and the artifact is marked unsealed for later review.
Operators retain signing keys in their own HSM, KMS, or TEE environments. CEYO is non-custodial and does not possess, transmit, or store private signing keys.
No. CEYO supports integrity and provenance arguments. Admissibility and regulatory sufficiency are determined by the relevant authority, forum, and institutional procedures.
Request walkthrough Verification steps