Framework Copy Manifest

Every file Sondely takes from TourCockpit (Ideaplaces/ideaplaces-tour-platform), what happens to it, which of its imports are cut, in which phase it is copied and where it lands in Sondely. After the copy the two products diverge; a TourCockpit fix reaches Sondely only when someone carries it across on purpose, by the procedure below.

As built on 7 November 2026. The copy lives in its own repository, CatalyzeUp/sondely-platform, whose root is the Next.js app, rather than a server/ folder in CatalyzeUp/sondely; read every server/ path on this page as the repository root. The base is TourCockpit commit 74e9a2a53 (74e9a2a53956731c46f707790e9ffae96fb9fafa, 7 November 2026, the head of develop that day), 230 commits after the f952d0eea this page was read at. framework-base.json at the repository root records the base and the copied files (on 8 November 2026: 84 copied and 19 written for Sondely, while about 120 files carry a copy header, the assistant and MCP files among them); it, not these tables, is meant to be the record of what was copied.

The imports in every table were read from the files at f952d0eea (git show f952d0eea:<path>), not inferred from names. The verdicts stand; line counts and imports may differ at 74e9a2a53. The plan this manifest serves is the migration overview; how the assistant pieces are rewritten for surveys is in Agent Layer.

How to read the tables

Target: same means the same path at the root of sondely-platform (src/lib/api/idempotency.ts lands at src/lib/api/idempotency.ts). The tables write it with the server/ prefix of the first plan. A different name is a rename, recorded in the file's header so the source is never lost. Keeping paths identical is deliberate: it is what makes a later port a plain diff.

Phases are the ones in the plan:

Global renames applied to every copied file

The renames are mechanical and applied in the strip commit, never in the copy commit (see the procedure), so git diff <copy commit> -- <file> always shows exactly what Sondely changed.

The copy procedure

1. Record the base once

A single file, framework-base.json at the repository root, is the record of where the framework came from. As built (abridged):

{
  "source": "https://github.com/Ideaplaces/ideaplaces-tour-platform",
  "commit": "74e9a2a53956731c46f707790e9ffae96fb9fafa",
  "copiedOn": "2026-11-07",
  "renames": { "Company": "Organization", "companyId": "organizationId", "UserCompany": "OrganizationMember", "UserRole": "MemberRole", "tp_session": "sondely_session" },
  "files": {
    "src/lib/api/idempotency.ts": { "from": "src/lib/api/idempotency.ts", "verdict": "copy-and-strip", "ported": [] },
    "src/lib/api/dispatch.ts": { "written": "sondely" }
  }
}

files holds one entry per copied file, written by the copy step, and marks the files written for Sondely with "written": "sondely". It is the machine-readable twin of this page.

2. Copy from the commit object, never from a working tree

TP=/path/to/ideaplaces-tour-platform
BASE=74e9a2a53956731c46f707790e9ffae96fb9fafa
git -C "$TP" show "$BASE:src/lib/api/idempotency.ts" > src/lib/api/idempotency.ts

git show <commit>:<path> reads the file as it was at the base, whatever branch or local change the TourCockpit checkout carries. A copy from a working tree would silently take someone's uncommitted edit.

3. Header on every copied file

The first lines of every copied file, before any import:

/**
 * @framework-source ideaplaces-tour-platform src/lib/api/errors.ts @ 74e9a2a53956731c46f707790e9ffae96fb9fafa
 * @framework-verdict copy-and-strip: the tour error codes and their messages removed; the envelope and the classing kept
 * @framework-ported (none)
 */

JSON files cannot hold a comment: their header lives in framework-base.json only. A YAML workflow or a Markdown agent file takes the same three tags as # or HTML comment lines.

A unit test, tests/unit/framework-headers.test.ts, reads framework-base.json and fails when a listed file lacks the header, when the header's source path disagrees with the JSON, or when a file under src/lib/{api,tenant,auth,mcp,assistant} carries no header and is not marked "written": "sondely" in the JSON. It does not need TourCockpit at test time. On 8 November 2026 the test walks src/lib/{api,tenant,auth} only, and the files copied for Sona (src/lib/assistant, src/lib/mcp) carry their headers but have no entry in framework-base.json: a gap between this rule and the repository, to close.

4. Two commits per group: copy, then strip

1. Copy commit: the files exactly as at the base, plus the header. It does not compile, and that is expected; it never lands alone on develop (the two commits travel in one pull request).
2. Strip commit: the global renames, the cuts named in the tables, the tour content removed. This commit is the Sondely divergence and the one a reviewer reads.

Groups follow the tables below (API, tenant, auth, logger, then the harness, then CI), so each pull request stays one concern.

5. Carrying a TourCockpit fix across later

The two products diverge, and that is the design: nothing syncs automatically. A fix is ported when someone decides it matters for Sondely.

1. Find what changed upstream for a copied file:

   git -C "$TP" log --oneline 74e9a2a53..origin/develop -- src/lib/api/idempotency.ts
   

2. Read the fix as a diff against the base, not against Sondely: git -C "$TP" show <fix sha> -- <path>.
3. Reproduce it first: a failing test in Sondely that shows the defect, per the engineering standard. If the defect does not exist in Sondely (the strip removed the code it lived in), stop: nothing to port.
4. Apply by hand or with git apply on the Sondely file. Because the path and the copy commit are kept, git diff <copy commit> -- <file> shows what Sondely changed, and the upstream hunk usually lands cleanly next to it.
5. Append to the header and the JSON: @framework-ported <sha> 2026-12-01 idempotency: a replay answers the stored content type, and the same line in files[...].ported.
6. Never move the base. commit in framework-base.json stays 74e9a2a53 for ever; a port is recorded per file. Moving the base would claim every file matches a newer TourCockpit, which is false.

A drift report (a script listing, for every entry in framework-base.json, the upstream commits since the base and whether each is already in ported) is a reasonable later convenience. It is inferred, not built.

src/lib/api (32 files)

Summary: 10 copy as is, 15 copy and strip, 7 leave behind.

src/lib/tenant (7 files)

src/lib/logger.ts

src/lib/auth (34 files)

Summary: 8 copy as is, 12 copy and strip, 1 later phase, 13 leave behind.

src/lib/mcp (12 files) and the routes that serve it

All MCP files are copied in P6. What each one becomes is in Agent Layer.

Route files outside src/lib that come with P6: src/app/mcp/route.ts (cut @/lib/assistant/asker-on-crew), src/app/oauth/{authorize,register,revoke,token}/route.ts, src/app/oauth/consent/{page.tsx,actions.ts}, src/app/.well-known/oauth-authorization-server/[[...issuer]]/route.ts, src/app/.well-known/oauth-protected-resource/[[...resource]]/route.ts. Same target paths under server/.

src/lib/assistant (115 files)

Phases P6 to P8b; the survey rewrite of each piece is described in Agent Layer. Files renamed because they carry the persona or the word company are marked in Target.

The write path and its tools

Refusals

The turn, the prompt and the drawer

Organizations (TourCockpit's companies)

Help, changelog, tool index, mail

WhatsApp and voice

Summary for the assistant directory, counted by file including the two generated JSON indexes: 44 copy as is, 40 copy and strip, 12 later phase, 19 leave behind. By lines, 19,100 of its 22,900 lines are copied in some form (5,300 as is, 13,800 copied and stripped), 2,200 are left behind and 1,550 wait for a later phase. The plan's estimate that about a third of the assistant code is reusable is about what survives: the copy and strip files keep their mechanism and lose their tour wording, and how many of their 13,800 lines remain is known only after the strip.

Services and support files outside the listed directories

The copied directories import these. Each comes with the phase of its first importer.

Prisma models that come along

From prisma/schema.prisma at the base. Every model with a company becomes organization scoped and joins TENANT_MODELS, so the tenant isolation and coverage tests cover it. Sondely's own models are in Data Model.

Row-level security comes with the models: 45 TourCockpit migrations enable RLS, with policies on current_setting('app.tenant_id'). Sondely's first migration writes the same policy for every organization-scoped table rather than copying the 45 migrations, whose tables are tour tables.

Test harness

CI workflows and scripts

Workflows live at the repository root (.github/workflows/), where GitHub reads them, and replace Sondely's current ci.yml, deploy.yml and deploy-prod.yml as each phase lands. TourCockpit runs on the IdeaPlaces nous runner pool; Sondely's jobs move to CatalyzeUp's own self-hosted runner (labels self-hosted, catalyzeup-linux, as used by catalyzeup-docs; that it can carry Postgres and Playwright jobs is inferred). Ideaplaces/discord-ci-status is used from another organization's repository, which needs the action to be readable from CatalyzeUp (inferred, check before relying on it).

Repository agents

TourCockpit's agents live in .claude/agents/. Each copy is renamed, its paths and spec links pointed at Sondely and these docs, and its incident history kept only where the rule still applies.

What this manifest does not cover

• The translation catalogs and scripts (i18n/, scripts/i18n/): Translation.
• The route handlers under src/app/api/v1/: none is copied. Sondely's routes are written new on the copied plumbing (API Routes).
• UI components under src/components/: chosen screen by screen in Frontend Screens.
• Infrastructure (Postgres server, Key Vault, container apps): Infrastructure.