Source-ownership reference

Edit the owning source, then run its synchronization or build step. Do not edit materialized copies and expect the change to persist.

Concern	Owning source	Derived or delivery surface
Shared ecosystem instructions	_context/	Root CLAUDE.md, AGENTS.md, CURSOR.md
Shared agent definitions	_agents/*/AGENT.md	Editor-specific agent directories
Spine-authored procedures	.claude/skills/*/SKILL.md	Codex and Cursor skill copies
Shared MCP recipe	.mcp.json	Editor-specific MCP configuration
Documentation platform roster and pins	docs-sites.toml	Per-site configuration and CI callers
Shared site identity	docs-brand/	Four byte-identical files below each docs root
Ecosystem map	docs-ecosystem/index.md in HSSMSpine	Canonical public page under HSSM while Spine's source repository remains private
Package behavior and public API	Owning package repository	Other sites link to its rendered docs
Network generation and promotion policy	LAN_pipeline_minimal	Validated artifacts in delivery stores
Personal task state	_local/	Session context only; never a tracked source

Spine owns a statement only when it is genuinely cross-repository. Package install commands, API guarantees, model availability, and troubleshooting belong with the package that implements and tests them. The dependency explanation shows where downstream verification is needed without transferring ownership.