Controlled pilot

Start with one team, one workflow, and named analysts.

The pilot is intended for teams ready to evaluate the complete workflow on real document-heavy work while staying inside the published technical boundaries.

1

Verify and request

Verify your work email, describe the team and environment, and list every analyst who would need access.

2

Human review

Daniel reviews the use case, environment, named users, support owner, and eligible installer. Approval is never automatic.

3

Individual verification

Each named analyst verifies their own email. Team approval alone does not unlock another person's download.

4

Audited access

Each verified member receives a seven-day entitlement with two five-minute URL issuances to the exact approved installer.

A useful pilot has

  • A named analyst champion
  • An organization-managed Windows environment
  • A DOCX-based workflow to evaluate
  • A support owner and escalation path

Plan for

  • Unaided installation from the guide
  • Import through XLSX export
  • One metadata-only in-app issue
  • A content-free first-week check-in

Current approved scope

A controlled Windows pilot, with the boundaries stated plainly.

Included

  • Windows desktop package
  • DOCX source documents
  • Predictions disabled
  • LocalDB or approved BYO SQL-auth
  • Controlled, named-user distribution

Not claimed

  • The installer is not Authenticode-signed.
  • The elite Windows shell and standard-user Windows 11 certification are not complete.
  • Two-machine and concurrent shared-database operation are outside the current proof scope.
  • No sector certification or direct ArcGIS integration is claimed.

Installer naming: the approved package is Observation Engine, but this candidate installs as Data Organization and downloads as DataOrgSetup.exe. Desktop rebranding is tracked separately.

Ready to propose a pilot?

Do not include document names, client information, credentials, or SQL details.

Request pilot access