Starting an integration means copying the same mechanical files by hand #58

New Issue

2026-09-21T07:18:18Z

cgalo5758 commented

2026-09-21 07:18:18 +00:00

What a person cannot do today

Start an integration from a command. Every one is hand-built from the guide, and the same mechanical surface is retyped each time: the package tree with the front-door adapter and its capability hooks, the query-generator configuration with its schema paths, a first migration that creates the schema, its three roles and their grants with a mirrored down, workflow and web stubs, the line that registers the integration, and a seed directory for the test stack.

What they should be able to do

Generate that surface from a slug, then write only what is specific to the service being integrated.

Why it matters

The mechanical parts are where a hand-built integration goes wrong quietly: a missing grant, a down migration that does not mirror its up, a schema path one level off. Two integrations have now been built against the guide, so a generator can encode what they agree on rather than guess.

Where

A generator under the repository's scripts, with templates that mirror the structure docs/building-an-integration.md describes.

Done when

One command produces a tree that compiles, registers and migrates with nothing else edited, and the guide points at it as the starting point.

Migrated from status/issues.md at b7a0e15

## What a person cannot do today Start an integration from a command. Every one is hand-built from the guide, and the same mechanical surface is retyped each time: the package tree with the front-door adapter and its capability hooks, the query-generator configuration with its schema paths, a first migration that creates the schema, its three roles and their grants with a mirrored down, workflow and web stubs, the line that registers the integration, and a seed directory for the test stack. ## What they should be able to do Generate that surface from a slug, then write only what is specific to the service being integrated. ## Why it matters The mechanical parts are where a hand-built integration goes wrong quietly: a missing grant, a down migration that does not mirror its up, a schema path one level off. Two integrations have now been built against the guide, so a generator can encode what they agree on rather than guess. ## Where A generator under the repository's scripts, with templates that mirror the structure [`docs/building-an-integration.md`](https://git.coopcloud.tech/wiki-cafe/member-console/src/commit/b7a0e15/docs/building-an-integration.md) describes. ## Done when One command produces a tree that compiles, registers and migrates with nothing else edited, and the guide points at it as the starting point. Migrated from status/issues.md at b7a0e15

cgalo5758 added the

kind

enhancement

area/integrations area/meta labels 2026-09-21 07:18:18 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: wiki-cafe/member-console#58