Operational Procedures & Lifecycle¶

Document reference: GFTCL-SOP-001 · Framework: GAMP 5 Category 5 · EU Annex 11

The standard operating procedures and lifecycle controls for the operational phase: day-to-day operation, change control, incident handling, maintenance, periodic review, and decommissioning.

SOP-01 · Routine operation¶

The substrate runs autonomously. Routine operator interaction is inspection:

gaiaftcl franklin status                 # cadence, tunables, paused state
gaiaftcl franklin show-state             # substrate-wide state projection
gaiaftcl substrate health observations   # health predicate observations
gaiaftcl substrate healing history       # self-healing actions

Pause / resume the sovereign cycle for maintenance:

gaiaftcl franklin pause      # writes ~/.gaiaftcl/franklin_paused.flag
gaiaftcl franklin resume     # removes the flag

SOP-02 · Change control¶

Every change to the system is a controlled change:

Record the change (what, why, risk class).
Update the affected controlled document(s) — URS/FS/SDS/Config Spec.
Add/extend the Risk Assessment for any new function.
Re-run the relevant qualification stage; a schema addition or High/Critical config change requires re-qualification.
Re-baseline: a passing run seals a new MQ receipt (Validation Summary).

The repository's pre-commit audit gates (data-integrity, security, doctrine) are an automated change-control guardrail — a non-conforming change cannot commit.

SOP-03 · Incident & deviation handling¶

If a qualification check returns non-CALORIE, the release is blocked.
Reproduce the failure; the append-only audit trail + replay anchors localize it.
Fix, re-qualify, and record the deviation and its resolution.
A broken cell is rebuilt from a clean image and re-moored — never nursed in an unknown state.

SOP-04 · Maintenance¶

Trigger	Action
macOS upgrade	Re-run IQ (component + schema integrity)
Toolchain (Swift) update	Rebuild + full 156-test suite
Schema addition (new V###)	Regenerate the Schema Catalog; re-qualify
CLI surface change	Regenerate the CLI Reference
Backup verification	Restore test + replay re-verification (quarterly)

SOP-05 · Periodic review¶

At a defined interval (recommended quarterly) confirm: qualification gates still pass on the current baseline; the RTM shows full coverage; configuration items are unchanged or changes were controlled; backups restore and replay clean; no open deviations. Record the review outcome.

SOP-06 · Decommissioning & data retention¶

Pause Franklin; stop the daemon.
Export the final substrate store and qualification receipts to the retention archive (records remain re-verifiable via witness hashes after export).
Unmoor the cell from the federation mesh.
Securely erase secrets (franklin_local_wallet_key.toml, API-key files) only after the operator has independently preserved any wallet they wish to retain.
Record the decommissioning and the retention location of the archived records.

Retention: append-only records and sealed receipts are retained for the regulated retention period; their integrity is checkable at any later date.

Cross-references: Validation Plan & Summary · Security, Backup & Recovery · Configuration Specification.

Federation-cosigned

This page's source is sealed in the GaiaFTCL federation manifest — page SHA-256 d59b15402b9acbc1…, manifest witness a090592e0609adc8…, signed 2026-06-02T18:58:22Z by cell gaiaftcl-mac-cell. Verify with gaiaftcl wiki sign --all and compare wiki-all-signatures.json.