Agent Onboarding Map

New session? Read this in order. Solves "agent doesn't understand the whole picture."

Reading order

1. ECOSYSTEM_MAP.md — what exists, how it connects
2. docs/fleet/README.md — 5-nhom operational framework
3. FLEET_GOVERNANCE_ROADMAP.md — architecture + roadmap + mesh policy
4. config/fleet/registry.json — every site, machine-readable
5. Per-site drill-down:
   • phamducphuongnam.com → WORKFLOW.md, config/article_master_pc.json, docs/ENTITY_SCHEMA_ROADMAP.md
   • nampham.net → ../docs/SITE_DEV_AGENT_PROFILE.md, ../docs/SITE_DEV_AGENT_MASTER_PLAN_2026.md
6. docs/decisions/DECISIONS.md — durable decisions (D-001..D-013), do not re-debate
7. This site (docs.nampham.net) — live control plane

What each site is for

Site	Role	When agent works on it
phamducphuongnam.com	Pharma/GMP E-E-A-T (primary persona surface)	GMP content, gate R01-R18, WP REST publish
nampham.net	Tech/AI architect (secondary persona surface)	Tech content, Hono CMS API, CF Workers
docs.nampham.net	Fleet docs control plane (this site)	Registry/mesh/framework docs, VitePress build
oee.nampham.net	Internal tool (noindex)	Monitoring only, NOT in entity graph
fleet.nampham.net	Internal dashboard (noindex)	Monitoring only, NOT in entity graph

Quick commands

# See the whole fleet
python3 factory/sitectl.py list

# Validate mesh integrity
python3 factory/sitectl.py validate

# Sync entity mesh
python3 factory/sitectl.py sync

# Register a new site
python3 factory/sitectl.py register factory/sites/<slug>/blueprint.yaml

Rules (do not re-debate)

• Workers do NOT publish/deploy/Asana (D-004)
• Gate R01-R18 mandatory, no bypass (D-005)
• sameAs = entity identity, not link equity (D-013)
• Fleet-level conflict → FLEET_GOVERNANCE_ROADMAP.md + registry.json win
• Content ops conflict → WORKFLOW.md wins (D-001)