Real-time tracking of all 8 estate plugins across fileos.cloud. Enforces Single Custody (PRT-0040), 100% Headless Execution (Rule 45), Zero Paid Actions via VPS review lanes, and complete client-side data privacy.
| Plugin ID | Primary Port | Dependencies Consumed | Shared Components Used | Places Used Across fileos.cloud | Holding Lane |
|---|
To eliminate commercial cloud CI/CD billing and guarantee $0 GitHub Action costs, all proposed updates to estate repositories are diverted into designated holding/ branches on GitHub.
holding/review-*vps_github_lane_daemon.py) detects update via in-memory git polling.main.OSF_USER_BACKUP_VAULT).DOC-USR-*) and records (USR-*) sync only to the user's personal private GitHub repository.YES. Both Cloudflare Forge and CF CLI represent high-leverage additions to our estate, and they should be integrated as two distinct, decoupled plugins rather than a single monolithic tool:
Upstream: https://github.com/cloudflare/forge
Role: Pluggable SDK & doc generation pipeline.
FileOS Fit: Runs on our VPS holding lane to ingest MRL schemas and OpenAPI specs, automatically compiling typed TypeScript / Python SDKs, CLIs, and documentation without paying for external SaaS.
Upstream: https://github.com/cloudflare/cf
Role: Agentic CLI for the entire Cloudflare API.
FileOS Fit: Replaces manual dashboard / Wrangler tasks. Enables our AI agents (CEO + JEV + Superpowers) to headlessly manage DNS records, Zero Trust access, and edge routing for fileos.cloud with structured JSON output.
Keep them separate: PLG-OSF-FORGE belongs to our Autonomous Code Generation & Schema Compilation tier, while PLG-OSF-CF belongs to our Cloud Edge Infrastructure & DNS Provider tier. Both have been registered in plugins_registry.json ready for activation.