ENOKQA

FAQ & Owner's Manual

Frequently Asked Questions

What is ENOKQA?

Your FITS-data portal for the McBride BCR — Point · Domain · Proof. It sees space (Leaflet + Deck.gl), reads FITS, and thinks with three Hugging Face agents (FITS vision, vector engine, A2A router).

How do I read a .fits file?

Open the portal, then press Load FITS (or drag a .fits file into the bottom pane). Headers are parsed as 2880-byte cards; 2D images render as a grayscale canvas. No plugins, no CDN.

How do I run the BCR engine?

One file, no mystery. selftest, inspect <pdf>, new --out audit.json, verify audit.json. Computed or NOT_RAN — never fabricated. Full reference in the Owner's Manual.

Is this portal live?

Staged and QA-green (17/17 code checks). Goes live with the Option A bundle at the site root plus its CSP header. If you're reading this page on ENOKQA.com, it's live.

Who do the guardrails protect?

You. Loopback-only services stay loopback. Keys live server-side. Draft-only stays draft. QA before done. The manual is the law.

Who is on the revenue team?

Three unnamed virtual employees, one evidence standard. ECXIBA (Business Analyst) inventories and sequences; ECXISE (Sales Engineer) builds ROI/sales motions; ECXIFE (Financial Engineer) runs financial models and the ledger gate — Tauric discipline: no figure without an artifact. All draft-only; all on the Command loopback.

The BCR console

Console: coming soon. Multi-Agent Control & Data Engine · Vector Stream & Agent Bus. The console will open on its own page once Google sign-in goes live.