Inicio · Capítulos · 14. Señales para visión artificial
En esta página
14.9.8 Zonas de datos y
persistencia
| DZ-01 |
RawImmutable |
Video, depth, IMU, force, audio y capture manifests. |
AppendThenSeal |
Longest |
| DZ-02 |
CalibrationAndScene |
Calibraciones y revisiones estáticas de escena. |
VersionedImmutable |
MatchDependentArtifacts |
| DZ-03 |
WorkingScratch |
Frames temporales, tensors y caches regenerables. |
Ephemeral |
HoursOrJobLifetime |
| DZ-04 |
DerivedArtifacts |
Pose, masks, contact graphs, phases, features y
classifications. |
ImmutableByDigest |
PolicyDriven |
| DZ-05 |
TransactionalMetadata |
Estados, índices, leases, revisiones, users y audit. |
Transactional |
ProjectLifetime |
| DZ-06 |
ModelCache |
Pesos, engines, manifests y calibración INT8. |
ImmutableByDigest |
PinnedPlusLRU |
| DZ-07 |
Telemetry |
Logs, metrics, traces, crash bundles y profiles. |
AppendOnlyWithCompaction |
Bounded |
| DZ-08 |
ExportAndSync |
Bundles, chunks, receipts y staging remoto. |
ImmutableUntilAcknowledged |
UntilVerifiedThenPolicy |
Reglas de
almacenamiento
- STO-01: Use NVMe for sustained capture and
analysis; microSD may remain boot media but is not the preferred
high-write artifact store.
- STO-02: Commit a media artifact by
write-to-staging, fsync according to profile, digest verification and
atomic rename.
- STO-03: Never expose a partially written object
under its final logical identifier.
- STO-04: SQLite WAL is permitted for local metadata
only on a local filesystem; backup must include a checkpoint or a
consistent backup API, not a copied main file separated from WAL
state.
- STO-05: Do not place the active SQLite database on
SMB/NFS/NAS unless the chosen database mode and locking semantics are
explicitly validated.
- STO-06: Large binary payloads never live as
unbounded BLOB columns in the primary metadata database.
- STO-07: Every artifact has digest, size, media
type, schema, producer and retention class.
- STO-08: Derived artifacts may be garbage-collected
only after reference-count and reproducibility checks.
- STO-09: Raw evidence deletion requires policy,
consent state, tombstone and derived-lineage impact analysis.
- STO-10: Disk free space is evaluated in bytes and
predicted time-to-full, not only percentage.
- STO-11: Snapshots and backups are verified by
restore tests and digest sampling.
- STO-12: Encryption keys and data backups are stored
separately; losing either must have a declared recovery outcome.
- STO-13: Crash consistency is tested with
power-loss/fault injection on representative storage.
- STO-14: The artifact store supports quarantine for
corrupt, unsigned or schema-invalid objects.
SQLite WAL permite concurrencia de lectores y escritor y mantiene un
archivo WAL como parte del estado persistente. Por ello, copiar
únicamente el archivo principal mientras existen conexiones activas no
constituye un backup correcto; el procedimiento debe usar
checkpoint/backup consistente y conservar la relación con WAL
[P49-R16].
Niveles de presión
| Normal |
Free space and write latency within profile |
Full capture and analysis. |
| Elevated |
Forecasted capacity below warning horizon |
Compact telemetry, evict regenerable cache, notify operator. |
| High |
Capacity below high watermark or write latency unstable |
Pause nonessential reprocessing and remote exports; preserve
capture. |
| Critical |
Raw capture cannot be guaranteed |
Stop accepting new attempts cleanly; never continue with silent
frame loss. |
| ReadOnlySafeMode |
Filesystem errors/corruption suspected |
Serve existing results, block writes, create incident bundle. |