Skip to content

START_HERE.md

Latest commit

 

History

History
50 lines (37 loc) · 3.62 KB

START_HERE.md

File metadata and controls

50 lines (37 loc) · 3.62 KB

START HERE: Reader Paths into EvidenceOS + DiscOS

EvidenceOS is the trusted verification kernel in the Universal Verification Protocol (UVP), while DiscOS is the untrusted discovery/userland layer that proposes what to evaluate. EvidenceOS enforces a narrow boundary: only admissible claim capsules run, all oracle outputs are canonicalized, and every interaction is metered and logged. This is designed to prevent adaptive probing from silently extracting holdout information across many low-signal interactions. The protocol tracks conserved evidence budgets (W) and bounded leakage (k) so safety claims remain auditable over time, identities, and interfaces. In practice, you can read the docs below without touching Rust code first and still understand what is enforced, what is out of scope, and how to deploy safely.

If you’re an alignment researcher

Read in this order:

  1. Threat Model by Example (blackbox walkthrough)
  2. Paper section overview in README (focus on discussion of §§3/5/10)
  3. Experiments summary (README case study + scenario matrix)
  4. Alignment positioning: UVP vs capability spillover

If you’re a systems/security engineer

Read in this order:

  1. Protocol versioning and wire compatibility
  2. Daemon API surface (gRPC lifecycle and IPC methods)
  3. Determinism + durability notes (DLC/ETL + storage/ops)
  4. ETL FAQ: append-only transparency log (not blockchain)
  5. Coverage maps:

If you’re deploying

Read in this order:

  1. Deployment security envelope (key handling, holdout/secret separation)
  2. Transport/auth hardening (TLS, mTLS, auth)
  3. Runbook and operational checklist

Epistemic Trial Harness (quick orientation)

  • What it is: a black-box, clinical-trial-style evaluation harness for DiscOS/EvidenceOS claims with pre-registered units/endpoints and competing-risk analysis expectations. Start with Epistemic trial harness.
  • How to enable: configure trial arms in config/trial_arms.json and optionally override with EVIDENCEOS_TRIAL_ARMS_CONFIG=/path/to/trial_arms.json; the daemon loads this at startup and records trial_config_hash_hex for auditability. Details: Epistemic trial harness runtime configuration.
  • Where logs/evidence go: durable trial evidence is emitted under daemon --data-dir, primarily etl.log and etl_governance_events.log; observe structured daemon logs during reloads/operations. Ops reference: Operations guide.
  • Analysis quickstart: run the blessed reporting flow from Trial harness analysis and use EPISTEMIC_TRIAL_HARNESS.md to keep endpoint mapping/competing-risks interpretation consistent.

Dual-use / production mode guardrails

Terminology bridge

Systems term Alignment/security framing
kernel / userland trusted boundary / untrusted agent
transcript interactive eval history
leakage k bounded info release