settled-reach/docs/sprints/sprint-6/copy.md

title, description, type, status, sprint, team

title	description	type	status	sprint	team
Sprint 6 — Copy Briefing	Smuggler item specs — manifest copy, access token, comm log	sprint	archived	6	copy

Sprint 6: Touch — Copy Tasks

Goal: Movement stances, fog rebuild, multi-verb interactions, and smuggler inventory

Branch: copy Agents: Mellanie (narrative), Paula (systems), Gestalt (content architecture)

New Tickets

#	Title	Blocked by
#441	Define 3 smuggler item specs — manifest copy, access token, comm log	—

Use db/connectors/ticket show <id> for full details.

Key Decisions

• decisions/scope.md — D-065 (Smuggler inventory — knowledge-primary with physical evidence)
• decisions/content.md — D-034 (THE FRIEND — production-level NPC pattern)

Notes

#441: Define 3 smuggler item specs

• What exists: Knowledge graph tracks what player knows (KG infrastructure from Sprint 3-4). Physical inventory is new for Sprint 6.
• Needs: Author YAML item specs for 3 smuggler inventory items (per D-065):
  1. Manifest copy — Proves cargo discrepancy. Leverage proof (smuggler's word doesn't carry institutional weight).
  2. Corridor access token — Proves ring membership. Physical proof of social network position.
  3. Personal comm log — Bridge between KG knowledge and provable leverage. Recorded conversations.
• D-065 context: Knowledge is the primary "inventory" for all characters (you SAW the manifest, not you HAVE it). Smuggler additionally gets minimal physical inventory (3 items in v0.1) because the smuggler's word doesn't carry institutional weight — they need tangible proof for leverage. Detective's word IS evidence (institutional authority), so detective is mostly KG-only (2 slots reserved for future use).
• Content requirements per item:
  • Name: Short display name (e.g., "Manifest Copy", "Access Token")
  • Description: 1-2 sentence item description in character voice (smuggler perspective)
  • Flavor text: Optional 1-line contextual note (e.g., "Kael's handwriting on the margins")
  • Knowledge link: Which FactId(s) this item proves or corroborates (e.g., manifest copy proves CargoDiscrepancySova17)
  • Contraband flag: Boolean — is this item detectable by security scans? (future #425)
• File location: content/campaigns/main/systems/van-maanens-star/sova/sova-transit/items/smuggler-inventory.yaml or similar
• Cross-reference: Sprint 5 deliverables (#297 Kael FRIEND pack, #298 Sera FRIEND pack) provide context for smuggler's social network and cargo operations. Items should reference established content.
• Integration: Server #424 implements CarriedBy component + Take/Place verbs. Client #438 renders inventory UI. Copy team defines the content (what the items are, why they matter).

Dependency Chain

#441 (Smuggler item specs) → standalone

Server #424 (CarriedBy implementation) reads item specs
Client #438 (Inventory UI) displays items

PR Workflow

When ready to submit, create a PR with tea CLI. All flags are required to avoid TTY prompts (see CLAUDE.md "Gitea access" section):

tea pr create \
  --repo jpmschweitzer/settled-reach \
  --login schweitz \
  --title "feat(content): smuggler inventory item specs" \
  --description "Sprint 6 copy deliverables per D-065 — manifest copy, access token, comm log" \
  --base main \
  --head copy

Notes for Copy Team

Sprint 6 is light for copy — only 1 ticket (#441). This is intentional: Sprint 5 was heavy content authoring (FRIEND packs ~150-200 lines), Sprint 6 focuses on systems and UI (server/client carry the load).

Item specs are small but thematically important. These items differentiate the smuggler's gameplay loop from the detective's. The smuggler needs physical proof because their word doesn't carry authority. Each item should feel like a risk to carry and a weapon to wield.

Voice and perspective:

• Items are viewed through the smuggler's eyes. Descriptions should reflect the smuggler's relationship to the object (e.g., "Kael slipped me this token three weeks ago. Access to the maintenance corridors. Hope it still works.").
• Item descriptions are diegetic — the character is looking at the item in their inventory. Not neutral game text.

Knowledge integration:

• Each item should tie to at least one FactId from the knowledge graph. For example, the manifest copy might prove CargoDiscrepancySova17 (a fact the smuggler knows) and unlock leverage in confrontation with Kael or Sera.
• Paula and Gestalt: cross-check item specs against existing KG FactIds in content/global/knowledge/ to ensure consistency.

Contraband implications:

• All 3 items are contraband (security would flag them). This is thematically consistent with the smuggler archetype. Detective doesn't carry contraband by default (institutional authority protects them).
• Contraband detection is deferred to future sprint (#425), but flag items now so the data is ready.

Sprint 6 copy work is small, high-quality, thematically load-bearing. Treat these 3 items as miniature character studies — what the smuggler carries defines who they are.