Status: built versus planned
The roadmap describes intent. This page describes state, and errs toward saying less.
Source: the Skighnet project's internal status document, dated 2026-11-14. It was compiled from merged changes and facts supplied by the owner. It was not checked against live systems, and no traffic, revenue or uptime figures are claimed. This page is edited by hand and can go stale.
| Capability | Status |
|---|---|
| Operations dashboard and backend on AWS ECS (stopped nightly at 03:00 ET by design) | Deployed (owner-supplied) |
| Read-only MCP server with bearer and OAuth 2.1 auth | Deployed; verified by a scripted flow only, not yet by a real AI-client connector |
| Mail hosting for part of the network on MXroute | Deployed (owner-supplied) |
| Cloudflare traffic analytics; approval-gated DNS editing; job and audit store; mail client | Merged, deploy pending |
| Domain registry reconciliation, health scoring, site manifests, news-wire claim ledger, DOLF envelope validation | Offline only (code and tests, no live wiring) |
| Architecture documents; Covenant of Care v0.1 (proposed) | Docs only |
| Revenue ingestion by domain and date | Planned |
| Bounded AI agent permissions and approvals | Planned |
| Immutable deployment records and rollback | Planned |
| Governed content publishing; autonomous cross-site coordination | Planned |
| Galatea enforcement of approvals; independent production veto | Planned / not established |
| IntelliPulse to Galatea to Skighnet pipeline running end to end | Unverified |
In short: the control plane and tooling are partly live; the reasoning layer's enforcement and the automated, cross-site loop are not.