PHAROS DATA ARK · 2026-10-29-01024f5b59
Build identity and support email
The System tab shows the source revision, branch, source fingerprint and
publication time. Publication time is recorded in UTC during web deployment and
displayed in the viewing device's timezone. A short revision identifies the last
Git checkpoint; the fingerprint also distinguishes local source changes.
/assets/build-info.json contains the full values. It is regenerated by
tools/write_build_info.py, not maintained by hand.
Support email… on that tab opens a local composer addressed to
[email protected]. Describe the failure and choose Add system diagnostics.
This uses the shared on-demand caretaker password pop-up. Collecting a report
does not enable Debug or change any network/service setting.
The bounded snapshot includes build/publication identity, status and resources,
OS/kernel, hardware, storage/mounts, failed services and timers, network links,
addresses/routes, wireless assignment, forwarding policy, recent service and
kernel errors, application events, portal Debug logs, library progress and source
failures. Browser context includes its version, language, timezone, recent UI
errors, current page without private URL fragments/query strings, and last known
status. Missing telemetry is recorded rather than requiring every service to work.
Recent logs are bounded, not the entire log history. Debug must already have been
enabled to contain the corresponding capture. No household files, message bodies,
credential stores, environment dumps, passwords, keys or tokens are collected.
Recognized secrets in log records are redacted. The report can still contain
private technical details such as network names and addresses: review it before
sharing. It is not published on the public content drive.
The composer has three numbered sections: describe the problem, add diagnostics,
and send using your email app. A basic browser/build report is available without
entering a password; the dialog explicitly labels it as basic until full system
diagnostics have been collected.
Choose Save diagnostics attachment, then Open email draft. The browser
starts downloading dataark-support-diagnostics.json; find that file in your
browser's downloads and attach it in your email app. Review the message and press
Send there. The ordinary email link cannot attach files and its message explicitly
asks you to attach the report rather than claiming it is already attached.
Other ways to send explains using webmail and offers **Save complete email
draft (.eml)**. That MIME file includes the JSON attachment and message context.
Some email apps open it as a saved message rather than a new draft, so opening or
importing it is a secondary route. Nothing is sent automatically. Without internet,
save the draft/report and send later. If the API is unreachable, a clearly marked
partial report preserves browser/build context for the failure.