# §37 — Project Spine (locally ratified in OSCR-)

**Date:** 2026-06-29
**Status:** Locally binding via OSCR- (proposed upstream to FVW v8)
**Source:** Operator chat refinements (2026-06-26 to 2026-06-28)
**Tier:** Scrap (unratified upstream) → Local ratification (binding for Oscar)

---

## 37.1 — Every Oscar workspace contains zero or more projects.

A project is a typed instance of a domain (tree, media, social, charity, home, admin).

## 37.2 — Project types are constitutional.

Initial taxonomy: `tree` (arboriculture). Extensible to other types per §37.2 extension.

## 37.3 — Every project has the same universal artefact graph (per §38).

The graph is domain-agnostic. Domain-specific artefacts are layered on top.

## 37.4 — Projects are sovereign within Oscar.

Artefacts are private to a project. Cross-project movement requires explicit operator action.

## 37.5 — Project lifecycle is constitutional.

States: `draft → active → paused → archived → deleted`. Each transition auditable.

## 37.6 — Project is the universal scoping context.

Every artefact has a `project_id: string` foreign key. The Smart adapter's Layer 2 data queries scope to the current project.