also looking at this
fix: resolve source links through native drone docs
#40
56 files
+179
-159
| @@ -3,9 +3,9 @@ | ||
| 3 | 3 | The incident record functions retain verified owned collection sources, explicit operator pixel |
| 4 | 4 | declarations and append-only review history. Native Stacks accounts, tokens, permissions, Gates, |
| 5 | 5 | model-derived migrations and transactions provide the persistence and access checks described in |
| 6 | [incident access](https://github.com/stacksjs/drone/blob/main/docs/public-safety-access.md). The collection producer remains unsigned simulation. | |
| 6 | [incident access](public-safety-access.md). The collection producer remains unsigned simulation. | |
| 7 | 7 | |
| 8 | [Managed source datasets](https://github.com/stacksjs/drone/blob/main/docs/public-safety-managed.md) can explicitly publish private derivatives | |
| 8 | [Managed source datasets](public-safety-managed.md) can explicitly publish private derivatives | |
| 9 | 9 | from one admitted source after custody enrollment, without copying observation or review notes. |
| 10 | 10 | |
| 11 | 11 | ## Register a collection source |
| @@ -116,10 +116,10 @@ and noncanonical numeric identifiers are refused. Responses and errors remain pr | ||
| 116 | 116 | uncacheable. These models have no generated REST, search or generic dashboard exposure. |
| 117 | 117 | |
| 118 | 118 | The access deadline controls current reads and writes. It does not erase database pages, exported |
| 119 | files, backups or uncontrolled copies. [Retention custody](https://github.com/stacksjs/drone/blob/main/docs/public-safety-retention.md) provides explicit enrollment and hold review, | |
| 120 | without granting deletion authority. [Accepted local purge](https://github.com/stacksjs/drone/blob/main/docs/public-safety-purge.md) separately | |
| 119 | files, backups or uncontrolled copies. [Retention custody](public-safety-retention.md) provides explicit enrollment and hold review, | |
| 120 | without granting deletion authority. [Accepted local purge](public-safety-purge.md) separately | |
| 121 | 121 | controls active DB payload and registered files; uncontrolled copies remain excluded. The |
| 122 | [incident handover module](https://github.com/stacksjs/drone/blob/main/docs/public-safety-handover.md) binds recipient acknowledgement to a | |
| 122 | [incident handover module](public-safety-handover.md) binds recipient acknowledgement to a | |
| 123 | 123 | selected-source briefing and its original uncertainty. Sector/team assignments, an authorized |
| 124 | 124 | operator workspace and live observations remain in issue #23, |
| 125 | 125 | alongside hardware, jurisdiction/operator, interoperability and field qualification. |