Appearance
Luniq Orbit — internal dev docs
Internal only
These are the developer docs — architecture, module internals, every setting and route. They are never deployed publicly. The public user docs live in frontend/src/docs/ and ship with the app at /docs.
Orbit is an AI content agent: one workspace = one website, and the platform runs that site's entire web presence — content production, SEO, search + AI-search visibility, technical health, and first-party analytics — with a chat-driven AI operator at the core.
What the product does, in one pass
- Onboarding builds the foundation: company identity, audience (ideal client), languages/markets, brand voice (AI-extracted from the site), CMS connection, publishing collections, tracking pixel, GSC (the site scan runs in the background; key pages are scored, not picked).
- Site context keeps a two-tier catalog of every page on the site (all pages tracked free; ~20 key pages per locale get AI enrichment), refreshed weekly.
- Collections writes multi-locale articles (research-enriched, SERP-aware, brand-voiced, copy-edited, quality-scored) as reviewable drafts and publishes them to any of 7 CMSs through one adapter contract.
- Performance modules measure everything: GSC (rankings, indexing), Orbit Pixel (human visitors, AI crawlers, manual-first conversion goals), Backlinks, Health (technical audit with Google + AI verdicts), AI Visibility (brand mentions in ChatGPT + Google AI Overview).
- The Orbit agent ties it together in chat: 21 read tools + 8 action skills, page-aware scoping, editable memory, background skill-job chains with live outcomes, a daily cost cap — plus a scheduled autopilot (daily research + the Monday Signals overview email) running for every workspace.
- Lead Audit is a public lead magnet: teaser audit → email gate → deep audit + branded PDF.
The module map
| Module | id | Status | One-liner |
|---|---|---|---|
| Collections | 1a-blog-publisher | live, always-on | The content engine: write → review → publish |
| Pages | pages | live | Site-pages surface + weekly refresh cron |
| GSC | gsc | live | Search analytics + index status |
| Statistics | orbit-pixel | live | First-party pixel, leads, AI-crawler intel |
| Backlinks | backlinks | live | Authority profile (DataForSEO) |
| Health | health | live | Technical audit, Google + AI verdicts |
| AI Visibility | ai-visibility | live | Brand presence in AI answers |
| Lead Audit | lead-audit | live, public | Site-audit lead magnet |
| Web | web | live | Agent fetch_url + web_search |
| Orbit MCP | mcp | live | Agent tools over remote MCP for external AI clients |
| Agent autopilot | agent-autopilot | live | Daily research run + weekly Signals overview email |
| Social · Sales · Market | — | shells (501) | Reserved |
Start here
- Architecture — the 3 rings · how code is organized and the module contract
- The AI agent · the chat loop, tools vs skills, memory, scheduler
- Frontend surfaces · every page and what the user can do there
- All settings & options · the single reference for every option
- Keeping these docs updated · how the freshness gate works