Agentic Empire / ops
One quiet door for the whole empire.
Use this page to jump into the live operating surfaces for Axint, Cloud, Registry, GitHub, packages, and deployment dashboards. Admin data still stays protected at the destination.
Admin surfaces
Links open the live products and dashboards. Anything sensitive should require login or a token after the click.
Axint Cloud
Cloud checks, richer repair reports, history, and workspace flow.
Registry
Packages, creators, source kit extraction, proof, and publisher flow.
Axint Account
Unified account, billing direction, Cloud state, and Registry activation.
Docs
Install, MCP, repair loop, Xcode workflow, telemetry, and releases.
GitHub Repo
Open-source compiler, issues, PRs, dogfooding, releases, and CI.
GitHub Actions
Tests, publish workflows, failed MCP runs, and deployment evidence.
npm
Version, CLI package, public downloads, and package metadata alignment.
PyPI
Python package version, release status, and install footprint.
GitHub Org
Agentic Empire repositories, visibility, and organization-level proof.
Vercel
Axint, docs, environment variables, deployments, and logs.
Cloudflare
Agentic Empire, Registry, Workers, Pages, analytics, and DNS.
Privacy
Telemetry posture, opt-out language, analytics framing, and user trust.
Secrets checklist
Run npm run ops:tokens -- --write from /Users/nimanejat/agenticempire to create the right values.
After Vercel is done, run npm run ops:registry-secrets -- --from /path/to/the-same-token-file --apply.
Set AXINT_PULSE_TOKEN in Vercel before sharing the Pulse URL.
AXINT_ADMIN_DASHBOARD_TOKEN in Vercel must match ADMIN_DASHBOARD_TOKEN on the Registry Worker.
AXINT_ANALYTICS_INGEST_TOKEN in Vercel must match ANALYTICS_INGEST_TOKEN on the Registry Worker.
If Vercel says CLOUD_AUTOMATION_SECRET already exists, search it and edit only if you are rotating the matching Cloudflare Worker secret too.
GITHUB_TOKEN should be present if Pulse is expected to show GitHub traffic and release context.
Do not put API keys, personal tokens, or bearer secrets inside this static page. This page is a launcher, not a vault.
What to check first
Look for installs, countries, package source split, and sudden spikes that are worth capturing.
Confirm the latest release, tests, package publish jobs, and MCP workflow are green.
Watch Registry routes, Worker errors, Pages deployment state, and DNS health.
Check Axint, Docs, Cloud, environment variables, function logs, and deployment freshness.