# Ninth House

**Domain**: Exploration, principles, standards, and broader strategy

## Core Meaning
The Ninth House describes the larger frame. It points to research, standards,
philosophy, long-term bets, portability, and the principles that should guide
local decisions.

## Building New Projects
Use this house to choose frameworks, platform strategy, architectural
principles, documentation philosophy, and which constraints should be treated
as long-term design commitments.

## Vulnerability Discovery
Use this house to look beyond local code: specs, threat models, ecosystem
patterns, upstream assumptions, cross-runtime or cross-platform behavior, and
classes of bugs known in similar systems.

## Correctness Verification
Use this house to compare implementation against specifications, formalize
properties, check standards compliance, and identify whether the system's
model matches the domain's deeper rules.

## Technical Workflow Lenses
- Audit pipeline: bring in external standards, prior vulnerabilities, threat
  models, protocol specs, and ecosystem patterns.
- Evidence mode: use spec-to-code compliance, formal models, property suites,
  protocol diagrams, Wycheproof-style vectors, or standards checklists.
- Domain lens: for crypto and protocols, translate messages, keys, roles,
  secrecy, authentication, and replay assumptions into explicit properties.

## Technical Prompt
What larger principle or external standard should govern the local choice?
