Public/Private Boundaries

Protean is designed around a strict operating principle: private science, public proof.

The runtime can produce rich internal scientific work product, but the public surface exposes only reviewed, redacted, verification-safe artifacts.

Private By Default

The following never publish automatically:

• raw sequences
• private salts
• selected batches
• private manifests
• source traces
• scoring weights
• embeddings
• failure logs
• internal papers
• unfiled invention material
• unreleased assay data
• provider packets
• local runtime paths

Public After Review

Public surfaces may expose:

• public object IDs
• salted commitments
• artifact hashes
• redacted lineage summaries
• disclosure state
• lifecycle state
• reviewed public papers
• reviewed collection manifests
• provenance verification records

Future Network-Aligned Participation Structures

Future network-alignment research must operate only on public-safe projections: reviewed collection manifests, object IDs, commitments, artifact hashes, redacted lineage, lifecycle state, disclosure state, and provenance verification records.

It must not expose raw sequences, salts, selected batches, source traces, scoring internals, embeddings, internal lineage notes, unfiled IP, unreleased assay data, provider packets, or local paths. Any future mechanism would be separate from $PRTN, separately documented, and review-gated before use.

Candidate Papers

Candidate assessment Markdown, PDFs, full manifests, and top-ten indexes are private work product by default. They may contain sequences, score internals, local paths, and IP-sensitive context.

Public research routes must serve reviewed public exports, not raw local paper batches.

Guardrail

private runtime
-> redaction guard
-> founder/scientific review
-> counsel review when candidate-specific
-> public export
-> optional provenance anchoring