mosaicstack/stack
1
0
Fork 1
Code Issues 248 Pull Requests 7 Actions Packages Projects Releases 15 Wiki Activity

Move old docs into _old_structure dir. Create blank GETTING_STARTED.md document

Browse Source
This commit is contained in:
Jason Woltje
2026-08-10 14:53:21 -05:00
parent 1655b1579a
commit cd4409abc3
273 changed files with 278 additions and 247 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/_old_structure/tess/M5-MIGRATION-CUTOVER.md
+12
View File
@@ -0,0 +1,12 @@
# TESS-MIG-001 — Cutover Procedure
This procedure is evidence-bound. It does not authorize a production cutover until the M5 qualification gate records the required validation.
1. Confirm the gateway has the explicitly registered `runtime.hermes` adapter (`apps/gateway/src/agent/agent.module.ts`) and provider reachability evidence (`apps/gateway/src/agent/hermes-runtime-reachability.e2e.test.ts`).
2. Query the normalized runtime capability surface, not a Hermes API directly. Confirm the session capabilities required for the operation are advertised.
3. Query the transitional matrix through `RuntimeProviderService.transitionalCapabilityMatrix` (`apps/gateway/src/agent/runtime-provider-registry.service.ts`). Kanban, skills, memory, tools, and cron must remain `unsupported`; stop rather than route those operations through Hermes.
4. Route new memory activity through the Mosaic operator-memory plugin path; there is no landed Hermes memory import.
5. Use `InteractionCoordinationService` (`apps/gateway/src/coord/interaction-coordination.service.ts`) for orchestration handoff. The interaction agent does not take configured orchestrator authority.
6. Record the qualification evidence and only then update an external deployment/channel binding through its separately authorized operational process.
No claim here authorizes bulk transcript copying, data-schema migration, or enabling an unsupported transitional capability.