Butterfly Effect Club v1 scaffold

Status

The admin console UI is under construction. v1 scaffolding shipped 2026-05-22 — it provides the repo layout, sheet schema, the dry-run sync script, and the GitHub Pages bind. The dashboard, auth gate, and roster table land in Phase 6 of the implementation sequence (see PROPOSAL.md §11).

How admin access works (planned)

The admin console boots from config.json — no hardcoded sheet IDs in the page. From there:

1. If no key in localStorage, generate one via the embedded create_signature.html flow
2. Public key is broadcast to Edgar via [REGISTER KEY EVENT] → lands on Main Ledger → Contributors Digital Signatures
3. Page calls the GAS proxy attached to the Cohort Roster sheet → resolves your registered email + checks whether it's on the sheet's editor list
4. If yes → admin dashboard (attestation queue). If no → public mode.

Trust circle = sheet editor list. To grant or revoke admin access, share or unshare the Cohort Roster. No static admin file to maintain.

Where to look

• Repo: TrueSightDAO/butterfly-effect-club — proposal, schema, scripts
• Program landing page on truesight.me — partner co-branded surface (this is the public credential URL family)
• Participant records — written to lineage-credentials by the GAS handler downstream of Edgar
• SCHEMA.md — ERA Cohort Roster schema + back-fill column glossary

For operators

Local dry-run runbook in scripts/README.md. Service account is butterfly-effect-club@get-data-io.iam.gserviceaccount.com; the Cohort Roster sheet at 1pApVCRqsDw9... already grants it editor access.