P06: implement Custom Domains authority model

[Techshrr]

GoJet V10 / P06 — Custom Domains

Refs #1
Refs #18

Status

READY FOR REVIEW — P06 EXIT CONDITIONS SATISFIED

P06 implements and closes the current-repository Custom Domains authority model defined by the approved GoJet V10 specification pack.

• final signed implementation SHA: 4079d1ee7c4876cab3e6bccccc3e4ac62cf97f23
• base integration SHA: ed82747f9f7ddb7696534cdda110f2f7f594b46a
• frozen test plan: artifacts/v10/P06/test-plan.json
• test range: P06-T001..P06-T024
• technical review: artifacts/v10/P06/review.md — SIGNED / APPROVED
• P0 defects: 0
• P1 defects: 0
• DECISION REQUIRED: 0

Frozen authority boundary

• support ticket = request only; never active entitlement
• active structured Business plan or recorded manual_approval are the entitlement sources
• highest currently valid domain_limit wins; security suspension/revocation overrides
• domain_limit is enforced atomically server-side
• Entitlement / Ownership / Ingress DNS / HTTPS / Domain Risk remain independent authority axes
• normal downgrade denies new mutations immediately and grants existing valid routing exactly seven calendar days of grace when no alternate valid source exists
• abuse/fraud/security suspension and ownership loss fail closed immediately with zero grace
• create/verify/activate/restore/rotate/link assignment/redirect are server-authoritative checkpoints
• custom-host redirect fails closed and never falls back to an official GoJet host
• official/custom hosts share identical normalized destination-risk target/fingerprint/selection policy; custom-domain authority is an additional gate only

Delivered implementation

• migrations/000002_custom_domains.sql: entitlement sources/requests, atomic usage, independent domain trust axes, append-only revalidation and audit authority
• internal/domains/*: entitlement resolution, hostname/IDNA authority, ownership TXT, ingress CNAME, HTTPS/TLS, domain risk, periodic revalidation, downgrade grace, security suspension, permission/mutation authority, Link assignment and runtime routing authority
• internal/links/*: same-transaction custom-domain Link create/update guard, custom-host redirect authority and destination-risk parity
• services/platformapi / services/redirectengine: shared production MySQL domain authority wiring
• Workspace Domains UI: entitlement states, custom-domain list, seven-step create flow, domain detail surfaces, assigned resources and revalidation state
• browser evidence covers mobile layout, keyboard tabs, accessible control naming, non-color-only status and persistent non-ready authority states

Final exact-head closure evidence

P06 Closure run: 32519298309 / run #9 — SUCCESS
Artifact ID: 9460016077
Artifact name: gojet-v10-p06-closure-4079d1ee7c4876cab3e6bccccc3e4ac62cf97f23
Artifact digest: sha256:21e2fe5898a047e166aac520870070e8072f00885a3c89aaf86736f6ac22a2c8
P06-T024 JSON digest: sha256:09782b88da32926d2f38c3b9c0511f87f24fed7cb185358ba2fdf18eb3ace27f

Closure artifact was independently inspected after CI:

• P06-T024: PASS, errors=[], exact signed SHA
• P06-T001..T023: 23/23 PASS, each bound to exact signed SHA with errors=[]
• regression manifest: 12/12 required workflows completed/success; missing=[], pending=[], failed=[]
• evidence-index: 23/23 input SHA-256 values match artifact files
• closure-result SHA-256 matches the actual P06-T024 file
• signed review and defect/decision ledger are present in the same exact-head artifact

Final same-head workflow matrix

• P00 Bootstrap and G0 Traceability — run 32519298146 — SUCCESS
• P01 Engineering Foundation — run 32519298143 — SUCCESS
• P02 Brand Foundation — run 32519298111 — SUCCESS
• P03 Design System — run 32519298126 — SUCCESS
• P04 Product Shells — run 32519298361 — SUCCESS
• P05 Links Domain Contract — run 32519298213 — SUCCESS
• P05 Real Integration — run 32519298161 — SUCCESS
• P05 Workspace Browser — run 32519298133 — SUCCESS
• P05 Closure — run 32519298187 — SUCCESS
• P06 Custom Domains — run 32519298259 — SUCCESS
• P06 Real Integration — run 32519298137 — SUCCESS
• P06 Workspace Domains Browser — run 32519298243 — SUCCESS
• P06 Closure — run 32519298309 — SUCCESS

P06 evidence coverage

• T001–T007: entitlement/request/manual approval, atomic capacity, tenant isolation and persistence authority
• T008: canonical hostname / IDNA / platform-host exclusion
• T009: hashed one-time ownership secret and rotation
• T010–T012: real authoritative TXT, CNAME and TLS observations
• T013–T014: fail-closed Domain Risk and periodic independent revalidation
• T015: exact 168-hour normal downgrade grace with immediate mutation denial
• T016: zero-grace abuse/fraud/security/ownership-loss suspension and no self-reactivation
• T017: Workspace manage permission precedes authoritative traffic/mutation and every trust axis is independently enforced
• T018: crafted Link create/update cannot bypass custom-domain assignment authority; denied writes do not mutate Links
• T019: custom-host redirect requires current routing entitlement/grace + all trust axes + destination-risk allow, fails closed without destination exposure and never falls back
• T020: official/custom normalized reachable-target fingerprint and destination-risk ordering parity
• T021: Workspace entitlement states and denied deep-link wizard behavior
• T022: seven-step wizard/detail/assigned-resource/revalidation flow with one-time secret isolation
• T023: mobile/accessibility/persistent-problem browser evidence
• T024: same-exact-head P00–P06 regression matrix plus internally consistent evidence index

Node ownership boundary

P14 later owns full request UX/mail; P17 later owns administrator entitlement queue/UI; P13 owns the full billing product; P16 owns the full provider/admin risk product. P06 establishes the authority model those nodes consume and does not depend on their unexecuted deliverables.

Merge boundary

P06 is now eligible for review: the signed revision itself passed the full affected exact-head matrix and T001–T024 closure. This PR has not been merged by this closure process; merge remains a separate repository/release action.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.