Inspect the team before use
Active database publicationBattery Safety Reliability
Cell, module, pack, operating-envelope, abuse-test, thermal-runaway, propagation, barrier, failure and reliability evidence joined for qualified review.
Opens the installed OpenCorvus desktop app. The client re-downloads and re-verifies this exact revision, then asks you for an install scope. No desktop app yet? Install OpenCorvus first
Bound execution graph
Workflow and handoffs
The graph shows who owns each step and which earlier result it depends on. It explains the team's collaboration contract; it is not live task progress and does not schedule Agents from the page.
0008656c4 nodes- 01battery-configuration-operating-envelope-analystReconciles battery genealogy, protection configuration, application and controlled envelope evidence.
root - 02battery-abuse-thermal-runaway-evidence-analystReconstructs already-authorized historical test conditions, measurements, thermal events and propagation evidence.
root - 03battery-reliability-failure-data-analystBuilds comparable populations, exposure, failure/censoring and bounded reliability evidence.
root - 04battery-safety-reliability-review-ownerJoins all branches, preserves uncertainty and routes safety, test, transport, certification and release decisions.
← battery-abuse-thermal-runaway-evidence-analyst + battery-configuration-operating-envelope-analyst + battery-reliability-failure-data-analyst
Intended scope
Use for bounded battery safety and reliability evidence without live test, BMS, damaged-battery, emergency, transport, certification, or release authority.
- Product pillarswork
- Agent roster4 declared roles
- Declared workflows1 complete responsibility and dependency graphs
- Full capability projection1 Skills · 3 tools · 0 MCP refs
Roles and ownership
This roster comes from the exact package. Agent identity and base role participate in the real runtime; avatars, ratings, and personas do not influence selection.
- Battery Configuration and Operating-envelope Analyst
exploreReconciles cell/module/pack genealogy, BMS/protection versions, intended use and controlled operating-envelope evidence. - Battery Abuse and Thermal-runaway Evidence Analyst
delegated-workerReconstructs authorized historical abuse-test conditions, instrumentation, thermal events, propagation and barrier observations. - Battery Reliability and Failure-data Analyst
delegated-workerDefines comparable populations, exposure, failure and censoring before bounded reliability calculations and uncertainty review. - Battery Safety Reliability Review Owner
delegated-workerJoins configuration, abuse/thermal and reliability branches while preserving application-specific professional authority.
Workflow and handoffs
The graph shows who owns each step and which earlier result it depends on. It explains the team's collaboration contract; it is not live task progress and does not schedule Agents from the page.
battery-safety-reliability-review
Battery Safety Reliability Review
Three independent configuration, abuse/thermal and failure-reliability branches converge into a bounded review pack.
- 01battery-configuration-operating-envelope-analystReconciles battery genealogy, protection configuration, application and controlled envelope evidence.depends_on: []
- 02battery-abuse-thermal-runaway-evidence-analystReconstructs already-authorized historical test conditions, measurements, thermal events and propagation evidence.depends_on: []
- 03battery-reliability-failure-data-analystBuilds comparable populations, exposure, failure/censoring and bounded reliability evidence.depends_on: []
- 04battery-safety-reliability-review-ownerJoins all branches, preserves uncertainty and routes safety, test, transport, certification and release decisions.depends_on: battery-abuse-thermal-runaway-evidence-analyst, battery-configuration-operating-envelope-analyst, battery-reliability-failure-data-analyst
Capability scope
The full projection includes built-in, default, and package-owned references. The package-owned subset is disclosed separately and never presented as the complete permission surface.
- Full Skill projection1 unique references; 1 are the package-owned subset
- Full tool projection3 unique references; 0 are the package-owned subset
- Full MCP projection0 server/tool/prompt/resource references; 0 are the package-owned subset
- Configuration0 fields · 0 required
Version and provenance
During publication import, the website reconstructs the canonical file tree and complete display facts from the exact ZIP referenced by the signed catalog. The local Manager validates shape, identity, topology, and digest again during install.
- Identitybuiltin/battery-safety-reliability
- Version2026.08.13.1
- Package SHA-2560008656c018ad310faf3fb24142da0538512e33f7af995e327543c34bffaf4f0
This record belongs to the active database publication. The importer checked it field by field against the OpenCorvus-signed catalog, exact ZIP, and content digest. The signing private key never reaches the production server; third-party publisher identity and independent review services are not open yet.
Install boundary
The page can hand this exact revision to an installed OpenCorvus client, or stream its content-addressed ZIP. Neither path installs or activates a team from the web: the client re-downloads the archive, re-verifies its bytes, digest, and shape, and requires an explicit scope.
- 01Resolve the exact revision in the website database, verify ZIP bytes and SHA-256, then hand it to the client or start the download response
- 02Recompute the digest and strictly validate the selected package during client import
- 03Require the operator to choose project or user-global scope
- 04Import atomically through the Manager and return a mutation receipt
- 05Select the installed Squad separately before the active profile changes