# Cutover history

Append-only log of structural changes to the Edge repo set. Each entry records a discrete migration or cutover event with date, operator, and evidence.

## 2026-05-27 — GitLab → GitHub canonical cutover

* **Operator**: `@nkap360`
* **Baseline tagged**: `v1.1.0` on `github.com/NKAP360-dev/edge-app` at SHA `16d7b77`
* **Reference plan**: source [`CUTOVER_PLAN.md`](https://github.com/NKAP360-dev/edge-governance/blob/main/CUTOVER_PLAN.md) + [`CUTOVER_DONE.md`](https://github.com/NKAP360-dev/edge-governance/blob/main/CUTOVER_DONE.md)

### What is now true

| Statement                                | Evidence                                                                                                              |
| ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------- |
| GitHub is the canonical source of truth  | [`LEGACY_VS_FUTURE.md`](https://github.com/NKAP360-dev/edge-governance/blob/main/LEGACY_VS_FUTURE.md)                 |
| Canonical baseline tagged `v1.1.0`       | Tag `v1.1.0` at SHA `16d7b77`                                                                                         |
| History is scrubbed (0 verified secrets) | [`SECRETS_AUDIT_2026-05-27.md`](https://github.com/NKAP360-dev/edge-governance/blob/main/SECRETS_AUDIT_2026-05-27.md) |
| CI/CD pipelines configured on `main`     | `.github/workflows/ci.yml` + `release.yml` on canonical                                                               |
| Dependabot active                        | `.github/dependabot.yml` on canonical                                                                                 |
| Internal/audit docs moved to governance  | `imported-from-app/`                                                                                                  |
| Bank-readiness assessment recorded       | [Banking Readiness overview](/banking-readiness/overview.md)                                                          |

### Cutover sequence executed

```mermaid
flowchart LR
    T0[T-0<br/>Freeze announce] --> T15[T+15<br/>Freeze GitLab]
    T15 --> T20[T+20<br/>Final sync]
    T20 --> T50[T+50<br/>Switch SoT]
    T50 --> T80[T+80<br/>Remove app duplicates]
    T80 --> T100[T+100<br/>GitLab archive]
    T100 --> T110[T+110<br/>Migration guide]
    T110 --> T130[T+130<br/>Smoke + DONE]
```

### Open follow-ups (not cutover-blocking)

* 30 Dependabot alerts pending triage (Gate 02).
* CI run on the merge commit failed (root cause: `edge-workflows` reusable repo not yet populated) — Gate 03.
* Smoke-test job for `/health` not yet added (Gate 05).
* Incident-response drill cadence not yet scheduled (Gate 07).
* `pocketbase/pb_data/data.db` still tracked as a binary blob; refactor per [`DATA_DB_STRATEGY.md`](https://github.com/NKAP360-dev/edge-governance/blob/main/DATA_DB_STRATEGY.md) (Gate 10 in Phase 2).

### Reversibility window

The cutover was **reversible for 7 days** after the DONE stamp. The window expired on 2026-06-03 without rollback being exercised. GitLab archive is now read-only forever.

***

## 2026-05-28 — Docs migration to GitBook

* **Operator**: `@nkap360`
* **Outcome**: All long-form docs moved to GitBook (`docs.edge.nyami.fr`) synced from `edge-governance/docs/`. Each repo's README slimmed to a one-pager that points to GitBook.
* **Diagrams**: ASCII art converted to Mermaid throughout.
* **Source SoT**: this `docs/` folder, edited via either GitBook UI or direct commit.

Future cutover events append below this section in chronological order.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.edge.nyami.fr/banking-readiness/cutover-history.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.