Scope and verification
Source and date
This documentation was prepared from read-only exploration of the authenticated SciShield local application on 12 November 2026. The observed footer version is v3.10.3.20261103.2621. The application base URL was http://earth.127.0.0.1.nip.io:8083.
The account identifies itself as Twila T Burris and has Bruxner Lab Group, Demuth Lab, and Jared Lab menu sections. Most lab-level examples use Bruxner Lab Group. Numeric record IDs, names, contact information, dates, and counts are local dataset examples.
Inspected screens
| Screen | Inspected route | Screenshot |
|---|---|---|
| Home | /frontpage_panel |
Home |
| Lab profile | /raft/group_page/19939/view |
Profile |
| Compliance dashboard | /raft/group_page/19939/lab_compliance |
Dashboard |
| Members | /raft/group_page/19939/users |
Members |
| Spaces | /raft/group_page/19939/group-spaces |
Spaces |
| Requirements | /node/19939/requirements |
Requirements |
| My Training | /raft/training/trainingRecords |
Training |
| Course Directory | /raft/training/courses |
Courses |
| Classroom sessions | /node/53168/sessions |
Sessions |
| My Equipment | /raft/equipment/my_equipment |
Equipment |
| Equipment detail | /node/151105 |
Asset detail |
| Lab Inspection Log | /node/19939/view/lab_inspections |
Inspections |
| Self Inspection Log | /raft/group_page/19939/self_inspections |
Self inspections |
| Lab forms | /raft/group_page/19939/forms |
Forms |
| Biological summary | /raft/group_page/19939/biologicals |
Biologicals |
| Rad Summary | /raft/group_page/19939/radTab |
Radiological |
| Organizational SOPs gateway | /raft/scisure/sops/organizational |
SOPs |
| Document Library | /raft/research_tools/document_library |
Library |
| SDS Search, including Advanced | /raft/research_tools/SDS |
SDS |
| Important Contacts | /raft/research_tools/important_contacts |
Contacts |
| Account profile | /raft/my_account/profile |
Account |
| Messages | /raft/my_account/messaging |
Messages |
| ObservNow | /ObservNow |
Observation |
| Incident form | /raft/incident-management/incident-report/create |
Incident |
Some routes redirect to canonical /node/… or /user/… pages. The table records the inspected entry route, not a portability guarantee.
What verification means here
Screen headings, visible data columns, labels, navigation destinations, filters, empty states, and 24 application screenshots were inspected. Steps leading to untested actions are explicitly described as entry points or intended next steps in their guide.
No reports, registrations, messages, enrollments, certifications, orders, inventory changes, permissions, profile changes, uploads, or deletions were submitted. Successful end-to-end mutation workflows are therefore not claimed.
Unverified areas
The documentation does not claim complete coverage of administrator or inspector roles, chemical inventory management, application source architecture, login/SSO, account recovery, course assessments, scheduled classroom registration, inspection detail/finding resolution, form creation fields, biological material editing, PI certification, radiological order/use/disposal forms, SOP editing, knowledge-base contents, health questionnaires, or vaccination records.
Several of those areas have visible links, documented in context. A visible link verifies an entry point; it does not verify the downstream workflow.
Observed environment issues
- ObservNow selectors and labels did not fully populate.
- The inbox displayed an empty table while the home page showed messages.
- The Document Library was empty and its document type selector was disabled.
- Profile editing linked to a separate local HTTPS service on port 5301.
- A radioactive license date differed by one day between summary screens.
- A finalized inspection could still show unresolved findings.
These observations are not root-cause diagnoses. See Troubleshooting.
Screenshots and publication
Screenshots contain the records visible in the provided authenticated development session, including names and contact information. The Node server defaults to the loopback interface. Before hosting for an audience, review the examples and apply the access controls appropriate for that audience.
The raw capture evidence JSON is retained locally for maintainers; the documentation server does not expose it. It contains extracted screen text and links, without session cookies or authentication tokens.