# Platform Smoke Test

<!-- BOOKSTACK-DOCUMENT-RELEASE:BEGIN -->
# Platform Smoke Test

| Field | Value |
| --- | --- |
| Distribution | BSS — OpenC5ISR |
| Product | OpenC5ISR |
| Release | 0.15.1 |
| Deployment | `openc5isr.bss.dev` |
| Source | `/srv/bss/releases/OpenC5ISR-v0.15.0-20app` |
| Evidence | Reference smoke test plus detected health routes |
| Source fingerprint | `93926e8c834f1ed79c9017a4096f70c76d73ce4f870f104fbd0cf54b2bed50ee` |
| Status | Generated baseline — human review required |

> **Verification boundary:** This page combines platform design guidance with static evidence from the release. It does not prove that every detected interface is enabled, reachable, secure, or operational in the deployed environment.

## Objective

Prove the release is running, routed correctly, connected to required shared services and able to complete one representative transaction before a deeper demonstration.

## Prerequisites

- [ ] Release activated and rollback target known.
- [ ] DNS/TLS and time synchronization healthy.
- [ ] Test user/service identities available without exposing credentials.
- [ ] Representative dependencies and test data available.

## Candidate health routes

- No candidate health route detected; use verified local/public roots and primary APIs.

## Procedure

1. Record active release and service state.
2. Verify local backend response on each enabled instance.
3. Verify public HTTPS route for `openc5isr.bss.dev` and certificate.
4. Log in with a non-admin test user and verify expected edition/branding.
5. Exercise one read and one authorized write operation.
6. Verify the operation appears in the intended UI/API and audit/log trail.
7. Review logs for new errors and measure response time.

## Pass criteria

All intended services remain stable; public and local paths return expected results; authorization is correct; a representative transaction completes; and no critical error/security regression appears.
<!-- BOOKSTACK-DOCUMENT-RELEASE:END -->

---

## Maintainer Notes

<!-- BOOKSTACK-DOCUMENT-RELEASE:NOTES-BEGIN -->
Add human-reviewed deployment notes, corrections, decisions, screenshots, and links here. Content outside the generated block is preserved on future runs.
<!-- BOOKSTACK-DOCUMENT-RELEASE:NOTES-END -->