Skip to content

Founder decision: visibility flipped back to public after the 2026-07-26 privatization — deliberate or accidental revert? #20

Description

@AnobleSCM

Surfaced by the 2026-08-03 overnight sweep (recorded in AnobleSCM/mcp-zero-trust-proxy#1's public-repo census). The 2026-07-26 privatization receipt (knowledge-stack: docs/research/receipts/2026-07-26-public-repo-privatization.md) records this repo being made PRIVATE that day. Live state today: PUBLIC, pushed-to today, active PRs. One-word founder answer needed in conversation: (a) deliberate — then the standing rule needs a third written exception naming this repo, or (b) accidental — then re-privatize (Vercel/consumer check first). No recommendation pre-cooked: the receipt and live state genuinely conflict.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    ready-for-humanNeeds Andrew / human decision (herdr-lead#640 triage)

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions