Skip to content

Latest commit

 

History

History
81 lines (66 loc) · 4.24 KB

File metadata and controls

81 lines (66 loc) · 4.24 KB

Power House Documentation

This index is the authoritative map for Power House v0.3.13 documentation.

Start Here

Document Purpose
Repository README Installation, architecture, examples, and public links
Verification Guide Reproduce proof modes, conformance vectors, and rejection tests
Identity Layer Immutable identity API, CLI, .pha binding, verification, and replay
Memory Capsule v1 Portable .phm proof memory, replay, semantic binding, and challenge vectors
Truth Boundary What is core proof, what is semantic explanation, and what must not be overclaimed
Power House + slbit Observatory Independent semantic packets, non-core sidecar binding, CLI, and browser workflow
Power House Archive v1 Normative .pha core identity and optional EPA format
Rootprint v1 Normative branching, merging, navigation, and graph verification
Provenance Security Model Integrity boundary, assumptions, mutation behavior, and EPA isolation
SDKs Rust and Python interfaces and cross-language interoperability
JULIAN Protocol Transcript anchoring, quorum reconciliation, and network architecture
Stable Public Network Roadmap Production topology, completion evidence, and remaining decentralization work
Signed Validator Registry Identity-bound validator enrollment, health reconciliation, and dynamic monitoring discovery
Public Observer Registry Permissionless observer enrollment, identity health checks, and public peer telemetry

Proof Systems And Formats

Operations

Operational commands must be tested against the release identified at the top of each active guide. Secrets, access tokens, private keys, and unredacted production configuration must never be committed.

Benchmarks And Conformance

Timing reports are environment-specific measurements. Protocol complexity and verification scope are defined in the corresponding specifications.

Historical Material

The following documents are retained for traceability and are not the current release specification or deployment authority:

For current behavior, use the source code, conformance vectors, CI workflow, and active documents listed above.