# docs

## Purpose

Public reference material and design history.

## Ownership

Website assets, architecture, features, integrations, launch material, protocol specs and superpowers design records.

## Local Contracts

Current source and protocol docs determine shipped behavior. Plans and historical specs are context, not evidence that a feature shipped. Never conflate activation configuration, fresh recall proof, or public-directory approval.

## Work Guidance

Update the closest protocol or integration document when its contract changes. Keep public links and version claims verifiable.

## Verification

Check relative links and referenced CLI help; package validator covers distribution claims affected by packaging changes.

## Child DOX Index

None. This document owns the full subtree.