# Seventh House

**Domain**: Partnership, contracts, users, and external counterparts

## Core Meaning
The Seventh House describes the other side of the relationship. It points to
users, peers, APIs, vendors, collaborators, adversaries, and any contract that
requires two parties to agree.

## Building New Projects
Use this house to shape user workflows, integration contracts, partner APIs,
permissions, handoffs, and the obligations the system accepts on behalf of
others.

## Vulnerability Discovery
Use this house to examine trust between parties: authentication,
authorization, delegation, OAuth flows, webhooks, multi-tenant boundaries, and
third-party integrations.

## Correctness Verification
Use this house to verify contracts, compatibility, permissions, cross-service
state, idempotency, and behavior at integration boundaries.

## Technical Workflow Lenses
- Audit pipeline: inspect authentication, authorization, delegation, webhooks,
  OAuth flows, vendors, and multi-tenant boundaries.
- Evidence mode: use integration tests, contract tests, permission matrices,
  captured traffic, and cross-service traces.
- Human context: clarify obligations between teams, users, APIs, reviewers, and
  external counterparties.

## Technical Prompt
Who is on the other side of this interface, and what agreement could fail under
pressure?
