121 lines
6.6 KiB
Markdown
121 lines
6.6 KiB
Markdown
# Session 0001.0 — Transcript
|
|
|
|
> App: wiggleverse-www
|
|
> Start: 2026-06-05T08-24 (PST)
|
|
> Type: coding
|
|
> Status: **FINALIZED**
|
|
> Mode: autonomous (default)
|
|
> Outcome: Code of Conduct page added (TL;DR + full), content finalized, deployed
|
|
> to pre-prod; operator chose to HOLD off the apex. Apex untouched.
|
|
> PRs: #1 (CoC page) merged · #2 (deploy SKIP_DOMAINS guard) merged.
|
|
|
|
## Launch prompt
|
|
|
|
> Add a Code of Conduct page (TLDR + full) to wiggleverse-www, finish any
|
|
> content polish, then decide whether to launch on wiggleverse.org — per
|
|
> wiggleverse-org/corp/ROADMAP.md Phase 1 and the site's phase1-marketing-site
|
|
> memory. Site is in pre-prod (pages.dev, SEO off) — don't re-point the apex
|
|
> until explicitly told it's ready.
|
|
|
|
## Plan
|
|
|
|
Phase 1 marketing site is built & in pre-prod. This session closes the one open
|
|
content item — the Code of Conduct page that replaces the pulled Transparency
|
|
surface — then polishes and decides on launch.
|
|
|
|
1. **Build `/code-of-conduct/`** — a full page (not a stub), grounded in the OHM
|
|
principles on The Model page. Mirror OHM's "two registers, one definition":
|
|
**TLDR = human register** (warm, plain, kid-readable), **full = machine
|
|
register** (precise, structural). Cover: who it applies to, the commitments,
|
|
expected/unacceptable behavior, special duty of care to minors, reporting,
|
|
enforcement, scope.
|
|
2. **Wire it in** — add a "Code of Conduct" link to the footer "The org" column
|
|
on every page; add to `sitemap.xml`. (Footer placement, not nav — it's a
|
|
governance doc; see Deferred decisions.)
|
|
3. **Content polish** — sweep the existing pages for small fixes.
|
|
4. **Verify** — serve locally, check all pages/links render.
|
|
5. **Push** — branch → PR → merge to `main` (per push-before-PR-review). Run the
|
|
pre-prod deploy (`infra/deploy-site.sh`) so pages.dev reflects the new page.
|
|
6. **Decide on launch** — recommend, but **do not** re-point the apex (gated on
|
|
explicit operator go-ahead). Record the recommendation.
|
|
|
|
## Pre-state
|
|
|
|
- Phase 1 site built & in pre-prod (corp/0002, 2026-06-04): six… actually five
|
|
pages (Home, The Model, Building, Learn, Give) on `wiggleverse-www.pages.dev`,
|
|
SEO off, apex un-pointed. Transparency surface had been pulled, slated for
|
|
rework as a Code of Conduct — the one open content item.
|
|
- Clean baseline: `main` == `origin/main`, no in-flight sessions (0001 was the
|
|
first numeric session under `wiggleverse-www/`).
|
|
|
|
## Session arc
|
|
|
|
1. **Init.** Classified as a coding session; ran `wgl-session-coding-init`,
|
|
claimed session 0001 (dry-run showed nothing in flight). Read repo memory
|
|
(`phase1-marketing-site`), corp `ROADMAP.md` Phase 1, the design spec §10, and
|
|
the existing page pattern (header/footer hand-repeated, design-system classes).
|
|
2. **Built `/code-of-conduct/index.html`** — a full page grounded in the eight OHM
|
|
principles from The Model page, structured as OHM's two registers: a warm,
|
|
kid-readable **TL;DR (human register)** and a precise **full text (machine
|
|
register)** covering scope, commitments, expected/unacceptable behavior, a
|
|
special duty of care to minors, reporting, enforcement, and changes.
|
|
3. **Wired it in** — footer "The org" link on all six pages (perl insert),
|
|
`sitemap.xml` entry, lastmod bumped to 2026-06-05.
|
|
4. **Polish** — fixed stale `transparency/` references in `CLAUDE.md` and
|
|
`README.md` (page was removed in corp/0002); confirmed the only remaining
|
|
`transparency` mentions are the intentional OHM *principle* on The Model + CoC.
|
|
5. **Verified** — served locally; all six pages + 404 return 200; CoC renders with
|
|
TL;DR + full + reporting email.
|
|
6. **Landed** — branch `add-code-of-conduct` → PR #1 → merged to `main`.
|
|
7. **Deploy safety** — discovered `deploy-site.sh` unconditionally re-attaches the
|
|
apex/www domains (= launch). Added a `SKIP_DOMAINS` guard (branch
|
|
`deploy-skip-domains-guard` → PR #2 → merged) so pre-prod refreshes never touch
|
|
the apex.
|
|
8. **Pre-prod deploy** — ran `SKIP_DOMAINS=1 ./infra/deploy-site.sh` with the
|
|
Cloudflare token from Keychain (`wgl-cloudflare-token-wiggleverse.org`, bytes
|
|
never printed). CoC live at `wiggleverse-www.pages.dev/code-of-conduct/` (200,
|
|
`X-Robots-Tag: noindex` intact); apex confirmed HTTP 000 (not launched).
|
|
9. **Launch decision** — presented readiness assessment + asked. **Operator chose
|
|
"Hold in pre-prod."** No apex change.
|
|
|
|
## Cut state
|
|
|
|
- `main` clean and == `origin/main`; zero open PRs; both branches deleted.
|
|
- Site content-complete in pre-prod; apex deliberately un-pointed (operator hold).
|
|
- Memory updated: `phase1-marketing-site.md` + `MEMORY.md`.
|
|
|
|
## 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._
|
|
|
|
- **CoC link placement — footer only, not the top nav.** The pulled Transparency
|
|
surface had both nav + footer links. I placed Code of Conduct in the footer
|
|
"The org" column on every page but left the top nav at its four items + CTA.
|
|
Rationale: a CoC is a governance/policy doc (footer is the web convention), and
|
|
the nav is already full. Easy to add to the nav if the operator prefers parity
|
|
with the old Transparency treatment.
|
|
- **CoC content authored from OHM principles.** No pre-written CoC text existed;
|
|
I drafted it grounded in the eight OHM principles on The Model page and mirrored
|
|
OHM's two-register structure (TL;DR = human register, full = machine register).
|
|
Reporting address used: `conduct@wiggleverse.org` (assumed; confirm it exists /
|
|
is monitored before launch). "Informed by the spirit of the Contributor
|
|
Covenant" is attributed without copying its text.
|
|
- **Deployed to pre-prod via new `SKIP_DOMAINS=1` path, not the bare script.**
|
|
`deploy-site.sh` unconditionally re-attaches the apex/www domains (= launch);
|
|
added a `SKIP_DOMAINS` guard (PR #2) and used it so the refresh never touched
|
|
the apex. Confirmed apex still HTTP 000.
|
|
- **Launch left for explicit operator go-ahead** per the standing gate — not
|
|
executed autonomously (operator previously pulled the site as "not ready"). At
|
|
closeout the operator confirmed: **hold in pre-prod.**
|
|
|
|
## Next session
|
|
|
|
The site is content-complete; the only open item is the launch decision, which the
|
|
operator is holding. When they say go:
|
|
|
|
```
|
|
/goal Launch wiggleverse-www on the apex: confirm conduct@wiggleverse.org is a real monitored inbox, revert the SEO block (robots.txt + X-Robots-Tag in _headers), then run infra/deploy-site.sh WITHOUT SKIP_DOMAINS to attach the apex/www custom domains + proxied CNAMEs. Per wiggleverse-org/corp/ROADMAP.md Phase 1 and the phase1-marketing-site memory.
|
|
```
|