title: RuView repository operating map

content: The Rust workspace and sensing server live under v2; contributor-facing architecture decisions live under docs/adr; the published operator harness lives under harness/ruview.

evidence: REPOSITORY


title: Evidence labels are mandatory

content: Accuracy and performance statements must distinguish MEASURED, CLAIMED, and SYNTHETIC evidence; pose PCK must be compared with the mean-pose baseline.

evidence: POLICY


title: The RuView harness is the contributor automation boundary

content: The RuView npm harness exposes fail-closed CLI and MCP tools while keeping its published runtime dependency-free; optional evolution tooling belongs in development and protected CI.

evidence: ADR


title: Self-learning requires gated promotion

content: Community memories and evolved policies are proposals until deterministic tests, security checks, frozen holdouts, and human review promote them. Raw transcripts and credentials are never shared.


title: Start repository exploration with source-cited guidance

content: The read-only ruview_guidance tool maps capability maturity to repository paths, validation commands, and explicit limitations; local citations are checked when a RuView checkout is available.