← Home

Systems World Tree

World Tree

Canonical structural map for agent routing, build gating, model routing, and verification discipline. Read-only by design. Clean systems scale.

Status: ACTIVE — canonical routing and governance visible

Canonical routing

The Systems World Tree (0ALekBrUCZ433Uk9PVA) is the canonical structural map for agent discovery, inheritance, and routing.

Canonical create-on / index Drive ID: 0ALekBrUCZ433Uk9PVA

New agents should be pointed at the Systems World Tree root 0ALekBrUCZ433Uk9PVA, not the internal-only core J.A.R.V.I.S. folder, and Slack-facing agents remain gated until the proper tokens are supplied.

Build gating

Agent creation stays phased: discovery → build package → user approval → external token handoff if needed → Hermes/profile implementation → identity test → final activation.

Slack-facing agents remain gated until dedicated tokens and identity approvals are supplied.

Model routing

Model routing now follows the standing governance rule: Tier 0 free/local first, then Tier 1 cheap API, Tier 2 standard API, and Tier 3 premium only for high-risk technical work.

  • Tier 0 — free / local first
  • Tier 1 — cheap API for routine work
  • Tier 2 — standard API for harder technical work
  • Tier 3 — premium only for app builds, architecture, and high-risk systems work

Verification discipline

HVCP says work is not done until it is verified, validated, tested, and delivered in a usable state. Do not assume success; verify it.

HVCP keeps the command center honest: execute, validate, fix, retest, then deliver.

Safety posture

Read-only local snapshot only — no credential changes, no deployments, no Slack/Telegram mutations, and no production edits from this surface.

No credentials, no production edits, no public deployment, and no Telegram re-enable from this page.

Source notes

  • Systems World Tree is the canonical structural map for new agents.
  • Canonical create-on / index Drive ID is 0ALekBrUCZ433Uk9PVA.
  • Injection scan workflow exists and requires reading every relevant folder before action.
  • Model tier routing is active: start free/local first, then escalate only when required.
  • HVCP requires verification before delivery, not optimism before evidence.
  • CLEAR bridge brief was not readable in the local source copy.