feat: self-anneal the public founder control loop

[HitsuyoAkuWeb3]

Closes #15

Business Change

Turn the strange-attractor audit and the accepted owner decisions into a founder-readable, privacy-safe control and activation loop.

Approved Position

• Category: Founder control system for AI-assisted work.
• Headline: Make AI work official.
• Promise: Turn AI-assisted work into owned, reviewable business assets.
• Mechanism: AI Office.
• Accessibility benefit: plain-English GitHub.
• Deeper doctrine: 9-Figure Ease.

What Changed

• Rebuilt the founder front door and deterministic proof loop.
• Added scoped Apache-2.0 and CC BY 4.0 licensing with joint copyright and explicit exclusions.
• Named separate security, conduct, and audit aliases with primary and backup owners, access limits, response targets, minimum-data rules, and an inbound-delivery gate.
• Bounded the First Official Asset Challenge to a 10-12 founder beta with private assets by default and evidence gates before any full public campaign.
• Replaced the parent GitBuilt Discussion form with Announcements.
• Created private GitMoneyOS/gitbuilt-proof-sprint staging, transferred the GitBuilt form, and established security, consent, metrics, brand, and claim gates.
• Prepared Discussions, Pages, social preview, and selected GitHub-owned Actions changes for post-merge execution.

Proof

• Public Framework Contract passed on commit 1cab2f1.
• All repository YAML parses.
• Relative Markdown links resolve.
• Third-party Actions are pinned to full commit SHAs.
• Bounded credential-pattern scan passes.
• Private Vulnerability Reporting, Dependabot security updates, secret scanning, and push protection are API-verified enabled.
• GitBuilt staging repository is private and its transferred Discussion form is inspectable by owners.

Remaining Gates

• The hitsuyoaku.tech aliases are approved names but are not represented as operational until inbound delivery and reply tests pass.
• Discussions, Pages, repository description/homepage, social preview upload, and the GitHub-owned Actions allowlist execute after merge and require live receipts.
• The Challenge is not open for public enrollment.
• GitBuilt visibility and launch remain blocked by all five launch gates.
• No release is approved by this packet.

Review And Merge Boundary

Hitsuyo Aku supplied the accepted decision packet. Red Pillar and the owners team should review the encoded implementation and public claim boundary. This PR must not merge automatically; a human owner decides merge after review.

After Merge

Execute the staged settings runbook, dispatch-test the SHA-pinned workflows under the selected GitHub-owned Actions policy, verify Pages and links, record the Healing Dashboard receipt, and separately decide whether a first release is warranted.

AI Assistance

OpenAI Codex prepared the bounded branch, deterministic checks, and review packet. Human owners retain public truth, settings, merge, release, and final acceptance.