# Session 0011.0 — Transcript

> App: makers-collective-demo
> Start: 2026-07-07T17-48 (PST) · End: 2026-07-07T20-09 (PST)
> Type: brainstorming (stage 2 continued as tech-design — operator-directed, one claim per session)
> Posture: careful
> Claude-Session: 779f8138-703a-4d08-9d47-22e76fc24ac7
> Checkout: /Users/benstull/git/wiggleverse.org/wiggleverse/makers-collective-demo--wt-modules (worktree, branch session-0011; removed at finalize after merge)
> Anchor: none — demo repo runs unanchored by design (no Gitea issues for this repo)
> Status: FINALIZED — merged to main at b1ba15b, demo published and verified, spec submitted (status: proposed)

## Launch prompt

```
Let's explore how modules will really work and what the schema will be. We need to create something that scales, is secure, has a moderation/approval system and is simple to author. Where should we start?
```

## Plan

Brainstorm how Hearth **modules** really work — authoring model, scalability,
security, moderation/approval — into the spec's business + product lenses,
then (stage 2, operator-directed mid-session: "Let's do the tech design for
this now to dig deep and come up with a working prototype") author the
engineering lens and land a working prototype of the Studio module surfaces
per the spec↔prototype lockstep. Concurrent SESSION-0010 was live in the main
checkout throughout; this session ran isolated in worktree
`makers-collective-demo--wt-modules` on branch `session-0011`.

## Pre-state

- `main` at 60dc906 (spec v0.6.0, Channel + two-feed contract). Spec's module
  ground: D4/INV-6 (data not code), INV-7 (version pinning), D26–D29 (filter
  lifecycle + Studio), D30–D31 (kinds; author-declared filter capability).
  Open: Q4 (engine perf), Q14 (filter registry bar), Q15 (module/filter
  overlap), plus no contracts for authoring, capability, approval, views,
  writes, or storage.
- SESSION-0010 live and concurrently merging (taglines v0.6.1, The Tube
  v0.6.2) — the claim's shared-checkout guard forced this session into its own
  worktree before claiming.

## Arc

1. **Gate + claim.** Operator chose Brainstorming at the type question.
   Claim refused the shared checkout (SESSION-0010 live) → worktree
   `--wt-modules`, branch `session-0011`, claimed **0011** stamped
   brainstorming/careful.
2. **Stage 1 — brainstorming (spec v0.7.0, D35–D40).** Framing confirmed
   (authoring model first), then five checkpoints: **D35** conversation-first
   authoring over an always-inspectable, hand-editable manifest; **D36**
   expressiveness ceiling = composition + bounded spreadsheet-grade
   expressions (no trigger chains; notifications parameterized by the same
   expressions); **D37** test loop = sandbox preview + steward-only trial
   install, member-facing enable a separate step; **D38** capability = D31
   generalized and typed (defines / reads-by-name / offers; own-types-only
   writes; installs narrow; consent sheet renders the declaration verbatim) →
   **INV-12**; **D39** registry gate tiered by capability (static validation
   always; self-publish own-data; human review for sensitive reads; modules
   aren't speech — delist/kill with notice + appeal). **D40** (registry
   signals) was adopted provisionally while the operator was AFK and later
   REVERSED by the operator at the stage-2 checkpoint: public install counts
   for artifacts; INV-11 stays people-scoped. Landed as PUC-25/26/27 +
   PUC-11 amendment, §5 Studio surfaces, §6 coherence touches, Q17/Q18.
3. **Stage 2 — tech-design (spec v0.8.0, D41–D46, §6.11).** Operator
   checkpoints: **D41** YAML + platform-published versioned JSON Schema;
   **D42** restricted CEL profile; **D43** compile-on-pin (resolves Q4).
   §6.11 authored: schema outline + worked example, CEL profile, static
   validation **V1–V8**, consent-sheet-as-pure-function, execution model,
   registry lifecycle states + sensitive-capability policy; Q17 resolved,
   Q18 narrowed to review operations.
4. **Working prototype (lockstep).** The Studio Modules tab gained the
   **manifest workbench**: editable YAML manifests (Seed Swap + Market
   Finder), live V1–V8 validation (subset parser + validator implemented
   in-page), consent sheet generated live with per-read narrowing switches,
   tier-routed publish + trial-install states, sandbox preview. Verified by
   an extracted-core node test harness (grew to 28 tests, all green;
   scratchpad-only, not committed).
5. **Operator design probes, each folded in live:**
   - *"How is the view defined?"* → **D44** renderer catalog + slot mapping
     (closed catalog v1: table/cards/list/calendar/gallery/board; slots map
     declared fields; platform owns a11y/theming once; V8). Prototype:
     renderer-driven preview — flip `cards` ↔ `table` in the YAML and the
     same objects re-render.
   - *"Where can I find the yaml schema?"* → it existed only as a name;
     authored **`specs/module-manifest.schema.json`**
     (`urn:hearth:module-manifest:v1`, draft 2020-12), verified with
     PyYAML + jsonschema (both manifests valid; negative controls fail).
   - *"How do members add a seed listing / where stored?"* → **D45** derived
     forms + bounded field annotations (label/help/choices/required/default —
     enums become data); prototype gained a working create path (derived
     form renders a select from `choices`; created listings land in the view
     or visibly filter out). Storage half answered by §6.2/§6.3.
   - *"What's the schema of the postgres store?"* → **D46** one JSONB-spine
     `objects` table + defines-validated writes + pin-time partial expression
     indexes; companion tables (manifests/installs/vouches/reviews). No
     prototype change (no UX surface).
   - *"Do we need an API key for an LLM?"* → No: public static page (a key
     would be world-readable; §6.3 hard secrets rule), and the working loop
     is deliberately deterministic; a live composer would be a server-side
     proxy behind the §6.2 AI boundary — future work, not this artifact.
6. **Ship (operator: "commit, merge, publish. And finalize").** Reconciled
   with 0010's v0.6.1/v0.6.2 (merge origin/main into session-0011; two spec
   conflicts resolved — version header → v0.8.0 keeping all change-log rows;
   §5 keeps both sessions' paragraphs; prototype auto-merged; suite green
   post-merge). Merged to `main` via a detached temp worktree (main checkout
   occupied by 0010) at **b1ba15b**; published via `publish-demo.sh` — origin
   sha256 match, HTTP 200 — https://hearth-demo.wiggleverse.org verified.

## Cut state

- `main` = b1ba15b: spec **v0.8.0** (D35–D46, INV-12, V1–V8, §6.11.1–.10,
  PUC-25/26/27, Q4+Q17 resolved, Q18 narrowed, `status: proposed`) +
  `specs/module-manifest.schema.json` + prototype with the working workbench.
  Demo live and verified.
- Session worktree removed, branch `session-0011` deleted locally (merged;
  remote branch retained). Canonical clone's local `main` left stale at
  a8b1cd7 deliberately — it is SESSION-0010's checkout; theirs to fast-forward.
- Spec submitted via submit-spec.sh (`--status proposed`, careful default —
  no-op: content already on main). Test harness lives only in the session
  scratchpad by design.

## Deferred decisions

_Autonomous-mode low-confidence calls the driver made and would have
liked operator input on. Appended as the session runs; surfaced at
finalize. Empty if none._

- ~~**Registry trust signals (proposed D40)**~~ — RESOLVED by operator at the
  stage-2 checkpoint: **reversed** the provisional call — install counts are
  public on registry listings (counts for artifacts, not people; INV-11 stays
  people-scoped). D40 amended in the spec.
- **Demo scope for the working prototype (stage 2)** — operator AFK at the
  checkpoint; adopted the **full working loop** per the launch instruction
  "dig deep and come up with a working prototype": editable YAML manifest
  inspector with live validation, live consent-sheet generation, sandbox
  preview, tier-routed publish. Implicitly ratified by the operator's
  merge-and-publish instruction at review; flag stands for the record.

## Operator plate

- Review the shipped spec at leisure (it merged on your instruction with the
  whole-document pass compressed): https://git.wiggleverse.org/wiggleverse/makers-collective-demo/src/branch/main/specs/hearth-platform-v1.md
- Q18 (module review operations), Q14 (filter bar — now informed by D39),
  Q15 (module/filter overlap — now judgeable against §6.11), Q12/Q13, Q16
  remain the flagged tech-design queue.

## Next-session prompt

```
/goal Complete the Hearth SPEC's remaining engineering lens (tech-design session) for the still-flagged v0.2–v0.6 work — the module system itself is DONE (session 0011, §6.11, D35–D46): biz/* featuring contracts + CatalogFeature lifecycle, BusinessMembership admission/attendance lifecycle (Q12/Q13), the filter manifest shape + disposition contract + profile-scope rendering pipeline + filter registry bar (Q14, informed by D39; module/filter overlap Q15 can now be judged against §6.11), the two-feed contract's Explore recommender (Q16), and module review operations (Q18) — per the §6 version notes in specs/hearth-platform-v1.md
```