# Planning & Prerequisites Managed documentation for Planning & Prerequisites. # System Requirements # System Requirements | 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 | Runtime manifests and file inventory | | 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. ## Observed runtime profile | Property | Observed | | --- | --- | | Languages by source-file count | PHP: 165, JavaScript: 150, Python: 74, C: 63, Shell: 34, C++: 1 | | Framework indicators | — | | Containerized | False | | Node projects | 2 | | Python requirement sets | 0 | ## Manifest evidence | Manifest | Project | Version | Runtime/base | Dependencies | | --- | --- | --- | --- | --- | | `package.json` | opensof-integrated-suite | 0.15.1 | node | 0 | | `edge/openssa-sensor/package.json` | openssa-mission-spectrum-console | 0.5.0 | node | 0 | ## Baseline host requirements - A supported Linux host with accurate time synchronization and administrative access for service/proxy changes. - The runtimes and package managers evidenced above, or an OCI container engine when container definitions are authoritative. - Sufficient CPU, memory, disk and network for enabled modules; sensor/radio/AI workloads require separate capacity sizing. - DNS and TLS certificates for public hostnames, plus firewall policy for public, management, backend and sensor interfaces. - A backup destination outside the active release and tested access to required databases/artifact stores. --- ## Maintainer Notes Add human-reviewed deployment notes, corrections, decisions, screenshots, and links here. Content outside the generated block is preserved on future runs. # Deployment Architecture # Deployment Architecture | 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 | Release layout and container evidence | | 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. ## Release layout | Property | Observed | | --- | --- | | Release path | `/srv/bss/releases/OpenC5ISR-v0.15.0-20app` | | Version | 0.15.1 | | Top-level entries | `third_party`: 870
`edge`: 100
`public`: 68
`openrf`: 36
`lib`: 32
`drivers`: 27
`tests`: 24
`examples`: 20
`data`: 17
`ontology`: 17
`.opennetworks-backup-20260827T210646Z`: 13
`open-daa`: 12
`modules`: 9
`scenarios`: 9
`integrations`: 8
`open-lvc`: 5
`common`: 4
`open-rf`: 4
`open-ssa`: 4
`templates`: 4
`models`: 3
`open-aar-mr`: 3
`open-bus`: 3
`open-cop`: 3
`open-cybersec`: 3
`open-eyes`: 3
`open-iia`: 3
`open-knowledge`: 3
`open-pnt`: 3
`open-chat`: 2
`open-task`: 2
`open-track`: 2
`rocketchat`: 2
`standards`: 2
`tools`: 2
`API.md`: 1
`CHANGELOG.md`: 1
`DEPLOY-GODADDY.md`: 1
`EXTERNAL-SERVICES.md`: 1
`FIX-v0.15.1.md`: 1 | | Source fingerprint | `93926e8c834f1ed79c9017a4096f70c76d73ce4f870f104fbd0cf54b2bed50ee` | ## Container/service topology candidates No Compose service was extracted; use the systemd and Nginx pages for other deployment evidence. ## Recommended release pattern ```text /srv//releases/-vX.Y.Z/ immutable extracted release /srv//instances//current symlink to active release /etc/// protected configuration and secrets /var/lib/// persistent state /var/log/// logs, when not solely in journald ``` Keep code/release artifacts immutable, configuration outside the release, persistent data outside the release, and activation as an atomic symlink/service switch. This makes rollback possible without reconstructing the prior state. --- ## Maintainer Notes Add human-reviewed deployment notes, corrections, decisions, screenshots, and links here. Content outside the generated block is preserved on future runs.