Operational Procedures & Lifecycle

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

FortressAI Research Institute · Norwich, Connecticut

Patents: USPTO 19/460,960 · USPTO 19/096,071 — © 2026 Richard Gillespie

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:

1. Record the change (what, why, risk class).

2. Update the affected controlled document(s) — URS/FS/SDS/Config Spec.

3. Add/extend the Risk Assessment for any new function.

4. Re-run the relevant qualification stage; a schema addition or High/Critical

config change requires re-qualification.

5. 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

1. If a qualification check returns non-CALORIE, the release is blocked.

2. Reproduce the failure; the append-only audit trail + replay anchors localize it.

3. Fix, re-qualify, and record the deviation and its resolution.

4. A broken cell is rebuilt from a clean image and re-moored — never nursed in an

unknown state.

SOP-04 · Maintenance

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

1. Pause Franklin; stop the daemon.

2. Export the final substrate store and qualification receipts to the retention archive

(records remain re-verifiable via witness hashes after export).

3. Unmoor the cell from the federation mesh.

4. Securely erase secrets (franklin_local_wallet_key.toml, API-key files) only after

the operator has independently preserved any wallet they wish to retain.

5. 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 cosignature: pending — gaiaftcl wiki sign --section GAMP5.*