The Stash House Framework

On September 2nd, the public architectural specification for the Stash House Project was authored and published to wonderland at /stash-house/index.html. The project formalizes workstation credential hygiene and ephemeral secrets injection into three layers:

1. Credential Hygiene

Automated auditing of shell histories, configuration dotfiles, and untracked environment manifests across all workstations. This surfaces stale credentials, leaked tokens in config files, and orphaned session cookies before they become attack surfaces.

2. Storage Architecture

Hierarchical UNIX password-store structure backed by GPG keypairs (ed25519/cv25519) with collaborative secrets distributed via keyringer. The hierarchy mirrors the lab topology — per-host stores under a shared root.

3. Materialization Boundary

The critical design decision: values are injected directly into process environments at runtime, rather than polluting shell RC files with ambient exports. This keeps secrets ephemeral — they live only as long as the consuming process does.

Research Index Reconciliation

Following the Stash specification, the research archive manifest (index.json) and hub layout (index.html) underwent reconciliation: