Know What Your Company Is Running.

Five compute from evidence: App, Build, Production, Integrations and Costs. The other six — Product, Customers, Data, AI, Commercial and Customer Contact — are deliberately unconnected and return unknown. Each dimension carries its own state, explanation, evidence and a real-evidence flag.

Repository metadata, latest commit, latest Actions workflow, and recent project deployments. A snapshot taken when the page is read, with no webhook, no polling and no stored deployment history.

Purpose, capability, billing type, plan, cost, renewal date, criticality, proof-of-concept status and where the record came from.

Attention items come from computed health factors that have real evidence behind them, so each one can name what raised it.

Explicit human decisions with their rationale and date. Separate from, and narrower than, comprehensive change auditing.

A curated relationship grouping with a category fallback and health attention, not a discovered dependency graph.

Simple, Standard and Technical wording, all derived from persisted service and decision records.

Independent Better Auth identity, PostgreSQL, workspaces, and owner, admin, member and viewer roles. No VoyantIQ service is required at runtime.

All on accounts the buyer owns. The application brings its schema and migrations; it does not bring somewhere to run them.

Until one exists there is no repository evidence, and the dimensions that depend on it report unknown rather than healthy.

The same applies to deployment evidence.

Entered by hand. No connected provider billing API populates them.

There is no email provider, no password reset and no email verification. A buyer running this as a paid service needs to build that before customers depend on it.

There is no member invitation flow, no company switcher and no per-client branding or export.

Nothing in the delivered application depends on a data licence VoyantIQ holds. The GitHub and hosting accounts it connects to are commercial relationships the buyer has or opens themselves.

The LGPL sharp and libvips exception is an open item in the transfer pack, with a first-transfer review requirement still outstanding. It is named here rather than left in a document nobody opens.

This repository makes no model call. The explanation levels are derived from stored facts, not generated, and nothing here runs a company on its own.

No billing API populates costs, and there is no cost history table. Costs are manual.

The cost-signal rules exist and are tested, but no application or interface path calls them and nothing supplies the prior snapshots they compare against. It must not be demonstrated as a working alert.

The provider connections are read-only snapshots. Nothing in the application changes a deployment, and nothing scans a dependency graph or discovers every paid vendor.

Environments are modelled with no working management surface.

Service corrections overwrite values. There is no who, what, before and after record beyond the decision log and row timestamps.

Not the parent brand, the shared platform, provider contracts, domains, trademarks, hosting accounts, credentials or any user data.

VoyantIQ retains a separately evolved Mission Control implementation in its platform repository. What transfers is this packaged standalone repository and its application-specific assets. Whether exclusivity means only that this Asset will not be sold again, or also restricts the seller's own related implementation, is settled in the agreement before completion rather than assumed from this page.