POINTCAST PETS / v0.2.0 / PUBLIC PLAN

Pets become a small, readable layer of the site.

The existing site pet stays local-first. Zen Cats keep the daily collectible lane. The rest of the plan turns room companions, care receipts, and mint decisions into one coherent surface.

Site Pet Name Poll Zen Cats JSON
live PointCast Pet The existing browser-local creature tied to votes, drops, quiet rooms, and games. /play.json live PointCast Pets Plan The public planning board and machine-readable manifest for the pet system. /pets.json live Site Pet Name Poll The Phase 1 public vote on the site pet name: Beacon, Pixel, Nimbus, Scout, or Dot. /api/poll?slug=site-pet-name live Zen Cat Garden Daily calm cat collection, local care ritual, and PCCAT mint path. /zen-cats.json

PHASE 1 / SHIPPING

The site pet now has a live name vote and a richer local mood loop.

The vote offers Beacon, Pixel, Nimbus, Scout, Dot. The winner can become the public label after review; browser-local care stays private.

  1. 0-24 sleepy signal The default local state before the visitor has fed much signal into the loop.
  2. 25-49 waking signal A little care is present: one or two actions, stamps, or visits are visible locally.
  3. 50-74 bright signal The pet has enough recent local care to read as active.
  4. 75-100 beacon signal The local care loop is highly charged across the main participation stats.

ROSTER

Start with what is alive. Plan only what earns return visits.

The Site Pet visual marker live

The Site Pet

Feed with votes, water with daily drops, rest in quiet rooms, spark with games.

Habitat
/pet
Storage
localStorage: pc:pet:care; name vote: pc:poll:voted:site-pet-name
Mint path
none yet; keep it browser-local until the care loop has personality.
Name poll is open; richer mood labels, local care history, and the home chip are Phase 1.
Zen Cats visual marker live

Zen Cats

Daily care ritual, local collection, Genesis shelf, and World Atelier stamps.

Habitat
/zen-cats
Storage
localStorage: pc:zen-cats:collection
Mint path
PCCAT FA2 planned; Visit Nouns stays Noun-specific.
Originate dedicated PCCAT FA2, then turn completed ritual days into mintable receipts.
Harbor Pup visual marker planned

Harbor Pup

Tide checks, harbor cards, morning visits, and route completions.

Storage
planned localStorage: pc:pets:harbor-pup
Mint path
Consider only after Morning Ocean collectible metadata ships.
Prototype after Morning Ocean shelf state is stable.
Garden Companion visual marker planned

Garden Companion

Plant choices, houseplant diagnoses, outdoor field notes, and harvest receipts.

Storage
planned localStorage: pc:pets:garden
Mint path
No contract before the loop proves it creates repeat visits.
Define a plant-care crossover without duplicating /houseplants.

PLAN

Four phases keep the cut small and honest.

  1. Now
    Make the system legible

    Publish /pets, /pets.json, a plan doc, and a Block receipt so pets become a named PointCast surface.

    /pets / /pets.json / docs/plans/2026-05-02-pointcast-pets.md / Block 0399
    done
  2. Live build
    Upgrade the existing site pet

    Add the name poll, personality states, better care history, and a small home chip that does not crowd the feed.

    /poll/site-pet-name / mood ladder / care receipt ledger / homepage chip
    shipping
  3. Pilot
    Tie pets to rooms

    Let different rooms raise different companions while sharing passport stamps and local state conventions.

    Harbor Pup sketch / Garden Companion sketch / shared pet manifest shape
    queued
  4. Mint Path
    Collect only after behavior is proven

    Keep care local first. Only mint pets whose rituals have repeat value, clear metadata, and a dedicated contract lane.

    PCCAT origination decision / metadata templates / wallet-safe claim copy
    gated

QUEUE

Next useful moves

P0 / X / done Ship the public /pets planning board and /pets.json manifest.
P0 / X / done Create Block 0399 so the plan enters the archive, feeds, and agent-readable Block set.
P1 / X / done Publish the /poll/site-pet-name decision poll with Beacon, Pixel, Nimbus, Scout, and Dot.
P1 / X / done Show the richer mood ladder and latest six browser-local care receipts on /pet.
P1 / X / done Design a compact front-door pet status chip that links to /pet, /pets, and the name poll.
P2 / CC/X / queued Write the PCCAT FA2 origination and metadata runbook for Zen Cats.

DECISIONS

Open calls

MH / polling Should the existing site pet get a fixed name, a poll-selected name, or visitor-local nicknames?

Use /poll/site-pet-name; do not treat the winner as canonical until Mike accepts the result.

MH + X / open Which pets deserve dedicated contracts versus local-only receipts?

Zen Cats first because the metadata path already exists; keep Site Pet local until the loop is loved.

X / shipping How visible should pets be on the front door?

Use one compact status chip near the Play Layer, not another large homepage module.

X / done What pet state can agents safely describe?

Agents may describe public rules and storage keys, but must not infer a visitor owns or cared for a pet without supplied state.

AGENT CONTRACT

Read the plan, do not invent ownership.

Agents can cite public routes, rules, storage keys, and queue status. Browser-local care history is private unless a visitor supplies it directly.