# Net schemas

JSON shapes for the Net pillar. Validation tooling TBD; these are the v2
source of truth until code lands.

| File | Describes |
|------|-----------|
| [subscription.json](./subscription.json) | Fleet-level part subscription |
| [observation.json](./observation.json) | Single fleet contribution |
| [intro-markers.json](./intro-markers.json) | `intro-markers` part payload |
| [edition-manifest.json](./edition-manifest.json) | Edition torrent manifest |

## Identity keys

Observations reference **content**, not paths:

```json
"contentKey": "content:sha256:abc…def"
```

Alternative for episodic content:

```json
"contentKey": "show:dan-da-dan:s02e04:fingerprint:…"
```

Path-based keys are forbidden in Net editions (fingerprinting risk). All obs/edition payloads strictly validated (additionalProperties:false in schemas); untrusted sources (torrents/obs) treated hostile per pillars/net.md security subsec + plan App C (PathGuard + mandatory auth for runtime, generic errs only, contentKey + provenance). See plan.md + correlation/cross-cutting for infra (governor net/*, mcp bridge/net, Phase 7 daemon).