also looking at this
fix: resolve source links through native drone docs
#40
56 files
+179
-159
| @@ -1,6 +1,6 @@ | ||
| 1 | 1 | # Owned public-safety collection |
| 2 | 2 | |
| 3 | Issue [#23](https://github.com/stacksjs/drone/issues/23) requires coordinated search, fire and disaster observation, incident annotations, operator review, team handover, enforced access/privacy/retention and runtime handling of communications, incident boundaries and resources. The collection and runtime foundation connects to authenticated source, observation, review and managed retention APIs. Separately accepted local purge is disabled by default. Recipient-confirmed incident coordination handover and the [authorized read and command workspace](https://github.com/stacksjs/drone/blob/main/docs/public-safety-workspace.md) connect persisted records to [live synthetic execution and deliberate source admission](https://github.com/stacksjs/drone/blob/main/docs/public-safety-execution.md). Sector/team assignments and operational qualification remain required work. | |
| 3 | Issue [#23](https://github.com/stacksjs/drone/issues/23) requires coordinated search, fire and disaster observation, incident annotations, operator review, team handover, enforced access/privacy/retention and runtime handling of communications, incident boundaries and resources. The collection and runtime foundation connects to authenticated source, observation, review and managed retention APIs. Separately accepted local purge is disabled by default. Recipient-confirmed incident coordination handover and the [authorized read and command workspace](public-safety-workspace.md) connect persisted records to [live synthetic execution and deliberate source admission](public-safety-execution.md). Sector/team assignments and operational qualification remain required work. | |
| 4 | 4 | |
| 5 | 5 | The four explicit observation purposes are search and rescue, fire observation, disaster assessment and lawful police observation. There is no identity recognition, automatic person pursuit, detention or enforcement action. Purpose authority and retention are explicit declarations, not established legal authority. All fixtures are synthetic and physical outputs remain inhibited. |
| 6 | 6 | |
| @@ -43,7 +43,7 @@ Replay re-executes the pinned `owned-public-safety-collection-v1` deterministic | ||
| 43 | 43 | |
| 44 | 44 | - Extend native authenticated incident membership/roles to managed exports and future team event paths. Declared offline actor strings are insufficient. |
| 45 | 45 | - Extend explicit enrollment and hold review to managed files, redacted views and removal of controlled evidence copies. Current API access denies expiry and revocation; offline files do not enforce deletion. |
| 46 | - [Recipient-confirmed incident coordination](https://github.com/stacksjs/drone/blob/main/docs/public-safety-handover.md) binds assignment, source and expiry to atomic acceptance and audit. Sector/team assignments remain later work. Incident responsibility and vehicle control remain separate. | |
| 46 | - [Recipient-confirmed incident coordination](public-safety-handover.md) binds assignment, source and expiry to atomic acceptance and audit. Sector/team assignments remain later work. Incident responsibility and vehicle control remain separate. | |
| 47 | 47 | - Qualify shared team collection and partial searched/unsearched support beyond the current single-owner synthetic execution. |
| 48 | 48 | - Measured visible/thermal calibration, timing/heading/georeferencing, communications, legal/jurisdiction/operator qualification, real team operations, external firmware integration and bench/HIL/vehicle campaigns. |
| 49 | 49 | |
| @@ -51,16 +51,16 @@ All three issue acceptance requirements remain open until their complete softwar | ||
| 51 | 51 | |
| 52 | 52 | ## Authenticated coordination |
| 53 | 53 | |
| 54 | The persisted [incident access API](https://github.com/stacksjs/drone/blob/main/docs/public-safety-access.md) uses native Stacks accounts, tokens, | |
| 54 | The persisted [incident access API](public-safety-access.md) uses native Stacks accounts, tokens, | |
| 55 | 55 | permissions, Gates and generated models for scoped incident membership, closure and paginated |
| 56 | audit. The [source and review module](https://github.com/stacksjs/drone/blob/main/docs/public-safety-records.md) retains complete verified collection | |
| 56 | audit. The [source and review module](public-safety-records.md) retains complete verified collection | |
| 57 | 57 | sources, explicit supported-pixel observations and append-only reviewer declarations under the same |
| 58 | native access rules. [Retention custody](https://github.com/stacksjs/drone/blob/main/docs/public-safety-retention.md) adds explicit inventory-bound | |
| 58 | native access rules. [Retention custody](public-safety-retention.md) adds explicit inventory-bound | |
| 59 | 59 | enrollment, minimal expired custody status and append-only hold decisions. Collection artifacts keep |
| 60 | 60 | their separate unsigned simulator evidence boundary. |
| 61 | [Accepted local purge](https://github.com/stacksjs/drone/blob/main/docs/public-safety-purge.md) removes only explicitly accepted active DB payload | |
| 61 | [Accepted local purge](public-safety-purge.md) removes only explicitly accepted active DB payload | |
| 62 | 62 | and registered private namespace entries, with a minimized custody receipt. It excludes offline |
| 63 | 63 | copies, historical diagnostics, backups and media residuals. The incident handover tracer |
| 64 | preserves source-bound uncertainty. The [authorized workspace](https://github.com/stacksjs/drone/blob/main/docs/public-safety-workspace.md) | |
| 64 | preserves source-bound uncertainty. The [authorized workspace](public-safety-workspace.md) | |
| 65 | 65 | combines persisted records, human commands and live synthetic execution. |
| 66 | 66 | Sector/team responsibility and full operational qualification remain in issue #23. |