Rate posture
Free99
$0 /mo
Setup: $0 for gated 0S access. Provider usage still needs real configured keys and allowed platform accounts.
Skye Content Forge expansion
Free99 content repurposing, still behind the gate.
Skye Content Forge is mounted inside the 0S as a live/local AI content command app for approved source scanning, original content generation, draft archives, Markdown export, SkyeVault/R2 upload, scheduler ticks, GitHub backup/restore, Netlify/Cloudflare deploy hooks, and official social publishing boundaries. Free99 means no charge. It does not mean public anonymous access.
Gate posture
No anonymous bypass
App boot requires a 0S, FS27, SkyGate, or local admin gate session. API calls reject ungated requests when the server is running.
Runtime posture
Local/live server
The command center runs from skye-content-repurposer-local/server.js, writes JSON state, exports Markdown, and exposes scheduler/backup/deploy routes behind tokens.
What this adds to the 0S
Running Gated App
Source scanner, article extraction, generation controls, draft archive, export panel, publisher queue, runtime status, backup, and restore controls from the live local server.
Static App Shell
Review the browser shell inside the 0S folder. End-to-end API actions require the running server at localhost:4399.
Publishing Architecture
Local static site output, GitHub commits, Netlify/Cloudflare hooks, CLI deploy options, and official social API boundaries.
Always-On Deployment
Docker, systemd, PM2, GitHub Actions, Netlify scheduled function, and Cloudflare cron worker templates.
Copyright Boundary
Approved source scanning is for topic discovery and transformed original content, not copying articles or implying source endorsement.
Proof Receipt
Review the gate-session script, API 401 proof, smoke test, pricing update, and local-runtime boundary.
Operator boundary
The app is ready as a local/live operator tool. Root 0S env import, OpenAI generation, and SkyeVault/R2 Markdown export are verified in the running environment. The legacy Google Drive route remains optional, but the primary cloud storage lane now uses the live Cloudflare R2 vault bucket. GitHub backup, Netlify/Cloudflare deploy, Facebook, Instagram, and LinkedIn publishing still require their provider permissions, account approvals, and platform rules before live claims.