Docs: ArbolSystem.md and FeedSystem.md describe a deployed system, but v5.0.0 ships no implementation

[brycemagera]

Summary

The PAI/DOCUMENTATION/Arbol/ArbolSystem.md and PAI/DOCUMENTATION/Feed/FeedSystem.md docs in v5.0.0 describe a fully deployed Cloudflare Workers platform (Arbol) with a live Feed System running on top of it — including specific deployed flow names, deployed worker names, schema details, and a _FEED private skill — but no implementation ships with the release. A user trying to follow the docs to "implement Feed and Arbol" hits a near-total gap.

What the docs claim exists

ArbolSystem.md references these paths/artifacts:

• ~/.claude/PAI/ARBOL/{Actions,Pipelines,Flows}/
• ~/.claude/PAI/USER/ARBOL/ (Workers source repo)
• lib/runner.v2.ts, lib/pipeline-runner.ts
• shared/auth.ts, shared/anthropic.ts, shared/action-worker.ts
• deploy.sh, flow-index.json
• Example deployed workers: arbol-a-label-and-rate, arbol-a-write-twitter-post, arbol-a-extract-transcript, etc.
• arbol run CLI

FeedSystem.md goes further and lists specifically deployed flows: _F_FEEDS_POLLER, _F_FEEDS_PROCESSOR, _F_FEEDS_LR_SURFACE, _F_YT_LABEL_EMAIL, _F_YT_LR_SURFACE — described in past tense ("Deployed as …"). It also references a _FEED/SKILL.md, a /feed slash command, a D1 schema with 4+ tables, R2 storage, Cloudflare Queues, and a self-hosted proxy.

What v5.0.0 actually ships

Item	v5.0.0 release
PAI/DOCUMENTATION/Arbol/ArbolSystem.md	Present
PAI/DOCUMENTATION/Feed/FeedSystem.md	Present (referenced in v5.0.0 ARCHITECTURE_SUMMARY)
PAI/ARBOL/	Missing
PAI/USER/ARBOL/	Missing
Any A_*, P_*, F_* implementation	None
lib/runner.v2.ts, shared/*.ts	None
deploy.sh, flow-index.json, any wrangler config	None
_FEED skill	None
/feed slash command	None
PAI/USER/{ACTIONS,PIPELINES,FLOWS}/	Empty README scaffolds only

(v4.0.x at least shipped ACTIONS/PIPELINES/FLOWS scaffold dirs; v5.0.0 dropped those from PAI/ but kept the docs that reference them.)

Additional issues this creates

1. PAI/USER/FEED.md ships as a "Needs content" placeholder — not the rich intelligence-routing doc its name suggests, and easy to confuse with the Feed System.
2. The default settings.json description includes "/feed manages intelligence sources, polling, and AI processing." and "The Arbol CLI (pai.ts) runs actions and pipelines from the terminal." — but no /feed command exists, and PAI/TOOLS/pai.ts is the Claude Code launcher, not an Arbol CLI.
3. ARCHITECTURE_SUMMARY.md lists Arbol and Feed as subsystems with doc paths, reinforcing the impression that they're shipped.

Requested clarification

Could you confirm which of these is intended?

• A. Arbol + Feed are private infrastructure you run, and the public docs are reference material that intentionally won't ship code. → Suggest a > Not included in public release. Private infrastructure reference. callout at the top of each file.
• B. They're planned for a future release and the v5.0.0 docs landed early. → Suggest a "Status: Planned / Not yet released" banner.
• C. The implementation exists in another repo / branch / Pack that users are expected to install separately. → Suggest a ## Installation section pointing to it.

Either way, removing the past-tense "Deployed as ..." phrasing from FeedSystem.md (lines 204-208) would prevent users from assuming the system is live in the public release.

Environment

• PAI release: v5.0.0
• Investigated via fork at brycemagera/Personal_AI_Infrastructure_fork

[dmoore44]

I'll second it. I was reading through the docs and was going to look in to setting up Arbol, but there's no implementation - just references.

[BCtopics]

I third this!

[danielmiessler]

To answer directly: it's your option A — Arbol and Feed are private cloud infrastructure the docs describe as reference architecture, and no implementation is intended to ship publicly. You're right that the docs should say so up front; a callout banner at the top of both files is the fix and it's queued for the release pipeline. Thanks for the thorough ships-vs-claims table.