MasteryMade · Domain Schema

Publishing Rules — Where Things Go

The routing table for every page, every agent, every session.
v1.1 · March 26, 2026 · Canonical: plans.asapai.net/domain-schema

FOR CLAUDE / FORGE / ANY AGENT: Before publishing via NowPage MCP, fetch this page and route accordingly. If content doesn't match any domain below, ask the user.

The rule

Each root domain = one audience. "Who needs to see this?" determines the domain.

Current domain assignments

DomainAudienceContent
plan.jasondmacdonald.comInternal teamMaster registry, 12 PRDs, architecture visuals, expert reconciliation docs, execution playbook (original)
plans.asapai.netInternal teamDomain schema (this page), execution playbook (copy), reusable templates
jasondmacdonald.comJason's public audienceDaily briefs, knowledge registry, articles, Builder's Code
[expert].asapai.netInternal (per-expert)Boarding packs, extraction workspaces, hubs
design.[expert].ioInternal (per-expert)Command centers, design systems (built from CLI)
[expert].ioExpert's audienceLanding pages, public tools, lead magnets
[expert].betaapp.ioExpert's usersLive MasteryOS product deployments
masteryos.aiMasteryOS customersCustomer docs, pricing, features
nowpage.aiDevelopersHC Protocol, NowPage product docs
labs.masterymade.comInternal + partnersContent templates, workbooks, case studies
*.asapai.net (other)NobodyScratch pad — prototypes, experiments, disposable

Decision flowchart

Is this a PRD, architecture spec, or reconciliation doc?
  → plan.jasondmacdonald.com

Is this a routing rule, template, or execution playbook?
  → plans.asapai.net

Is this a daily brief, article, or public thought leadership?
  → jasondmacdonald.com

Is this an expert's extraction workspace (boarding pack, etc)?
  → [expert].asapai.net

Is this something the expert's AUDIENCE sees?
  → [expert].io or betaapp.io

Is this a content template or workbook?
  → labs.masterymade.com

Is this a prototype or experiment?
  → [anything].asapai.net (scratch)

None of the above?
  → ASK THE USER

NowPage MCP security — domain restrictions

Before any partner or external user gets MCP access: Token scoping must be implemented.

Required restrictions

RestrictionPriority
Per-user domain allowlist — User A can only write to domains they ownHigh
System domains locked — plan.jasondmacdonald.com, plans.asapai.net, jasondmacdonald.com, nowpage.ai, masteryos.ai NEVER writable by external usersCritical
Slug namespace protection — /prd-*, /master-*, /domain-* reserved for adminMedium
Rate limiting — per-token publish limitMedium

Token scoping example

{
  "token": "align360-samuel-2026",
  "allowed_domains": ["align360.io","align360.asapai.net"],
  "denied_slug_prefixes": ["prd-","master-","domain-"],
  "rate_limit": "20/hour",
  "can_register_command_center": true,
  "can_send_email": false
}

Future migration

WhenFromTo
masterymade.com subdomains availableplan.jasondmacdonald.complans.masterymade.com
Same time[expert].asapai.net[expert].masterymade.com
PRD 12 ships(new)docs.masterymade.com

For Claude sessions

Agent instruction: Fetch https://plans.asapai.net/domain-schema before publishing. Route per the flowchart. Never publish to jasondmacdonald.com unless it's public personal brand content. Never publish to [expert].io unless it's user-facing in the expert's voice.
MASTERYMADE · Domain Schema v1.1 · March 26, 2026