Field Intelligence
Secure access to the live NEXXUS field observation system.
This app uses Supabase Auth and the project publishable key. No database secret or service-role key is stored in the browser.
Create the NEXXUS workspace.
This creates the application workspace used by the field app. It is separate from the Supabase dashboard organization.
Build the first field assignment.
Create a location, its primary manager, and the 10-observation engagement.
Select the location you’re observing.
The next observation number is calculated from the live engagement record.
Capture the operation as it actually runs.
Neutral baseline. No manager labels. No hunting for a client theory. Observe, document, and let the evidence determine where NEXXUS looks next.
I am observing real operating conditions, not trying to prove a preexisting concern.
Scores are based on observable evidence; hypotheses belong in narrative.
A critical flag is for serious evidence-backed issues within NEXXUS scope—not a legal or regulatory conclusion.
Operating Conditions
Context is what makes repeated observations comparable.
Required purchases are stored separately from the NEXXUS professional fee and tied to this observation.
Core Observation
Score observable execution. Use N/A when the condition did not reasonably occur.
Diagnostic Narratives
The score summarizes. These prompts capture the operating story.
Review Before Submission
NEXXUS checks the evidence trail before the observation can close.
I have separated observable facts from hypotheses and have not altered a score to match a client expectation.
Observation synced.
This field record is now part of the live NEXXUS Standards Assurance evidence set.
This visit becomes evidence—not a verdict.
The dashboard can now combine this observation with later visits to determine consistency, identify signals, and guide targeted sampling.