create-mercato-app 0.10.1-develop.8029.1.ef1583a886 → 0.10.1-develop.8034.1.400508da51
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +35 -6
- package/agentic/guides/architecture.md +7 -5
- package/agentic/guides/template-tool.md +38 -0
- package/agentic/shared/AGENTS.md.template +1 -0
- package/agentic/shared/ai/harness/cases.json +1 -1
- package/dist/agentic/guides/architecture.md +7 -5
- package/dist/agentic/guides/module-facts.json +162 -162
- package/dist/agentic/guides/module-facts.v2.json +162 -162
- package/dist/agentic/guides/modules/agent_orchestrator/index.md +1 -1
- package/dist/agentic/guides/modules/ai_assistant/index.md +1 -1
- package/dist/agentic/guides/modules/api_docs/index.md +1 -1
- package/dist/agentic/guides/modules/api_keys/index.md +1 -1
- package/dist/agentic/guides/modules/attachments/index.md +1 -1
- package/dist/agentic/guides/modules/audit_logs/index.md +1 -1
- package/dist/agentic/guides/modules/auth/index.md +1 -1
- package/dist/agentic/guides/modules/availability/index.md +1 -1
- package/dist/agentic/guides/modules/business_rules/index.md +1 -1
- package/dist/agentic/guides/modules/carrier_inpost/index.md +1 -1
- package/dist/agentic/guides/modules/cart/index.md +1 -1
- package/dist/agentic/guides/modules/catalog/index.md +1 -1
- package/dist/agentic/guides/modules/channel_apns/index.md +1 -1
- package/dist/agentic/guides/modules/channel_discord/index.md +1 -1
- package/dist/agentic/guides/modules/channel_expo/index.md +1 -1
- package/dist/agentic/guides/modules/channel_fcm/index.md +1 -1
- package/dist/agentic/guides/modules/channel_gmail/index.md +1 -1
- package/dist/agentic/guides/modules/channel_imap/index.md +1 -1
- package/dist/agentic/guides/modules/channel_resend/index.md +1 -1
- package/dist/agentic/guides/modules/channel_ses/index.md +1 -1
- package/dist/agentic/guides/modules/channel_smtp/index.md +1 -1
- package/dist/agentic/guides/modules/checkout/index.md +1 -1
- package/dist/agentic/guides/modules/communication_channels/index.md +1 -1
- package/dist/agentic/guides/modules/configs/index.md +1 -1
- package/dist/agentic/guides/modules/content/index.md +1 -1
- package/dist/agentic/guides/modules/currencies/index.md +1 -1
- package/dist/agentic/guides/modules/customer_accounts/index.md +1 -1
- package/dist/agentic/guides/modules/customer_groups/index.md +1 -1
- package/dist/agentic/guides/modules/customers/index.md +1 -1
- package/dist/agentic/guides/modules/dashboards/index.md +1 -1
- package/dist/agentic/guides/modules/data_sync/index.md +1 -1
- package/dist/agentic/guides/modules/design_system/index.md +1 -1
- package/dist/agentic/guides/modules/devices/index.md +1 -1
- package/dist/agentic/guides/modules/dictionaries/index.md +1 -1
- package/dist/agentic/guides/modules/directory/index.md +1 -1
- package/dist/agentic/guides/modules/documents/index.md +1 -1
- package/dist/agentic/guides/modules/ecommerce/index.md +1 -1
- package/dist/agentic/guides/modules/entities/index.md +1 -1
- package/dist/agentic/guides/modules/eudr/index.md +1 -1
- package/dist/agentic/guides/modules/events/index.md +1 -1
- package/dist/agentic/guides/modules/feature_toggles/index.md +1 -1
- package/dist/agentic/guides/modules/forms/index.md +1 -1
- package/dist/agentic/guides/modules/gateway_autopay/index.md +1 -1
- package/dist/agentic/guides/modules/gateway_stripe/index.md +1 -1
- package/dist/agentic/guides/modules/gateway_tpay/index.md +1 -1
- package/dist/agentic/guides/modules/generators/index.md +1 -1
- package/dist/agentic/guides/modules/inbox_ops/index.md +1 -1
- package/dist/agentic/guides/modules/integrations/index.md +1 -1
- package/dist/agentic/guides/modules/messages/index.md +1 -1
- package/dist/agentic/guides/modules/notifications/index.md +1 -1
- package/dist/agentic/guides/modules/onboarding/index.md +1 -1
- package/dist/agentic/guides/modules/payment_gateways/index.md +1 -1
- package/dist/agentic/guides/modules/perspectives/index.md +1 -1
- package/dist/agentic/guides/modules/phone_calls/index.md +1 -1
- package/dist/agentic/guides/modules/planner/index.md +1 -1
- package/dist/agentic/guides/modules/portal/index.md +1 -1
- package/dist/agentic/guides/modules/progress/index.md +1 -1
- package/dist/agentic/guides/modules/promotions/index.md +1 -1
- package/dist/agentic/guides/modules/push_notifications/index.md +1 -1
- package/dist/agentic/guides/modules/query_index/index.md +1 -1
- package/dist/agentic/guides/modules/record_locks/index.md +1 -1
- package/dist/agentic/guides/modules/resources/index.md +1 -1
- package/dist/agentic/guides/modules/sales/index.md +1 -1
- package/dist/agentic/guides/modules/scheduler/index.md +1 -1
- package/dist/agentic/guides/modules/search/index.md +1 -1
- package/dist/agentic/guides/modules/security/index.md +1 -1
- package/dist/agentic/guides/modules/seeds/index.md +1 -1
- package/dist/agentic/guides/modules/shipping_carriers/index.md +1 -1
- package/dist/agentic/guides/modules/sso/index.md +1 -1
- package/dist/agentic/guides/modules/staff/index.md +1 -1
- package/dist/agentic/guides/modules/storage_s3/index.md +1 -1
- package/dist/agentic/guides/modules/sync_akeneo/index.md +1 -1
- package/dist/agentic/guides/modules/sync_excel/index.md +1 -1
- package/dist/agentic/guides/modules/system_status_overlays/index.md +1 -1
- package/dist/agentic/guides/modules/telemetry/index.md +1 -1
- package/dist/agentic/guides/modules/tillio/index.md +1 -1
- package/dist/agentic/guides/modules/translations/index.md +1 -1
- package/dist/agentic/guides/modules/warranty_claims/index.md +1 -1
- package/dist/agentic/guides/modules/webhooks/index.md +1 -1
- package/dist/agentic/guides/modules/wms/index.md +1 -1
- package/dist/agentic/guides/modules/workflows/index.md +1 -1
- package/dist/agentic/guides/reference-module-facts.json +1 -1
- package/dist/agentic/guides/template-tool.md +38 -0
- package/dist/agentic/guides/upstream/manifest.json +1 -1
- package/dist/agentic/shared/AGENTS.md.template +1 -0
- package/dist/agentic/shared/ai/harness/cases.json +1 -1
- package/dist/index.js +1453 -345
- package/dist/templates/__fixtures__/templates.json +126 -0
- package/dist/templates/compat.ts +281 -0
- package/dist/templates/fetch-templates.ts +177 -0
- package/dist/templates/finalize.ts +238 -0
- package/dist/templates/resolve-template.ts +255 -0
- package/dist/templates/template-step.ts +149 -0
- package/dist/templates/templates.test.ts +1357 -0
- package/dist/templates/types.ts +77 -0
- package/package.json +3 -3
- package/template/AGENTS.md +1 -0
package/README.md
CHANGED
|
@@ -12,10 +12,11 @@ yarn setup
|
|
|
12
12
|
|
|
13
13
|
`yarn setup` needs Node 24, Yarn 4 (`corepack enable`) and a running Docker engine. It checks Docker, starts PostgreSQL, Redis and Meilisearch from the app's `docker-compose.yml`, waits until they are healthy, then installs dependencies, migrates and initializes the database and starts the dev server. It copies `.env.example` to `.env` only when `.env` is missing and never overwrites it, so re-running is safe. Running PostgreSQL, Redis and Meilisearch yourself? Point `.env` at them and use `yarn setup --no-infra` (no Docker calls at all).
|
|
14
14
|
|
|
15
|
-
|
|
15
|
+
To start from a working app instead of the bare scaffold, create it from an [app template](https://modules.openmercato.com/templates) or from any GitHub repository that holds a standalone app:
|
|
16
16
|
|
|
17
17
|
```bash
|
|
18
|
-
npx create-mercato-app my-
|
|
18
|
+
npx create-mercato-app my-crm --template crm
|
|
19
|
+
npx create-mercato-app my-portal --template some-agency/b2b-portal#v1.0.0
|
|
19
20
|
npx create-mercato-app my-marketplace --app-url https://github.com/some-agency/ready-app-marketplace
|
|
20
21
|
```
|
|
21
22
|
|
|
@@ -37,6 +38,8 @@ npx create-mercato-app <app-name> [options]
|
|
|
37
38
|
|--------|-------------|
|
|
38
39
|
| `--app <name>` | Bootstrap an official Open Mercato ready app from `open-mercato/ready-app-<name>` |
|
|
39
40
|
| `--app-url <url>` | Bootstrap a ready app from a GitHub repository URL |
|
|
41
|
+
| `--template <slug \| owner/repo>[#ref]` | Create the app from an app template: a slug listed at [modules.openmercato.com/templates](https://modules.openmercato.com/templates) or any GitHub repository. See [App Templates](#app-templates) |
|
|
42
|
+
| `--keep-name` | With `--template`, keep the template's `package.json` `name` |
|
|
40
43
|
| `--preset <id>` | Select the `classic`, `empty`, `crm`, or `wms` starter without prompting |
|
|
41
44
|
| `--agents <list>` | Set up `claude-code`, `codex`, `cursor`, a comma-separated subset, `all`, or `none` without prompting |
|
|
42
45
|
| `--skip-agentic-setup` | Skip the interactive agentic setup wizard |
|
|
@@ -56,8 +59,11 @@ npx create-mercato-app <app-name> [options]
|
|
|
56
59
|
# Create a new app using the public npm registry
|
|
57
60
|
npx create-mercato-app my-store
|
|
58
61
|
|
|
59
|
-
# Create an
|
|
60
|
-
npx create-mercato-app my-
|
|
62
|
+
# Create an app from a listed app template
|
|
63
|
+
npx create-mercato-app my-crm --template crm
|
|
64
|
+
|
|
65
|
+
# Create an app from a GitHub repository at a tag
|
|
66
|
+
npx create-mercato-app my-portal --template some-agency/b2b-portal#v1.0.0
|
|
61
67
|
|
|
62
68
|
# Create an app from an external GitHub-hosted ready app
|
|
63
69
|
npx create-mercato-app my-marketplace --app-url https://github.com/some-agency/ready-app-marketplace
|
|
@@ -87,16 +93,37 @@ npx create-mercato-app my-store --agents claude-code,codex --experimental-hooks-
|
|
|
87
93
|
npx create-mercato-app my-store --init-git
|
|
88
94
|
```
|
|
89
95
|
|
|
96
|
+
## App Templates
|
|
97
|
+
|
|
98
|
+
An app template is a GitHub repository with a complete standalone app at its root. Listed templates are at [modules.openmercato.com/templates](https://modules.openmercato.com/templates). To save your own app as a template, use [create-mercato-template](https://github.com/open-mercato/create-mercato-template).
|
|
99
|
+
|
|
100
|
+
```bash
|
|
101
|
+
npx create-mercato-app <app-name> --template <slug | owner/repo>[#ref] [--keep-name]
|
|
102
|
+
```
|
|
103
|
+
|
|
104
|
+
- A slug is looked up in the template index (`templates.json`). `owner/repo` also works for a repository that is not listed, and for a private one when `GITHUB_TOKEN` is set. `#ref` is a branch, tag or commit.
|
|
105
|
+
- The CLI picks one commit and prints it before anything is downloaded: `Template: owner/repo@<sha> (<state>)`. The state is `verified`, `not verified`, `not listed, not verified` or `catalog status unknown, not verified` (the index could not be read). A `#ref` that points to another commit than the listed one prints `not verified, no catalog facts for <sha>`.
|
|
106
|
+
- A template on hold is refused with its reason, and there is no override. An unmaintained template works and prints its reason.
|
|
107
|
+
- The CLI warns and continues when the template is built on another Open Mercato line than the latest stable one (both lines are shown), and when it registers `@open-mercato/enterprise` modules on every start, which need an Open Mercato Enterprise license. A dependency on that package with its modules behind a flag such as `OM_ENABLE_ENTERPRISE_MODULES` (as in the stock scaffold) prints nothing; when `src/modules.ts` cannot be read, the CLI says the license may be needed but could not be confirmed.
|
|
108
|
+
- `--template` cannot be combined with `--app`, `--app-url`, `--modules`, `--module-picker`, `--agents`, `--experimental-hooks-validator` or a `--preset` other than `classic`. The module picker and the agentic setup wizard are not offered. `--registry` and `--verdaccio` do not apply: the app keeps the registry settings of its own `.yarnrc.yml`.
|
|
109
|
+
- The app is copied as it is, with three changes: the `package.json` `name` becomes the app name (unless `--keep-name`), `package.json` gets an `openMercatoTemplate` field with the repository, ref and commit, and the root `mercato-template.json` is removed.
|
|
110
|
+
- If the import fails, the CLI removes the directory it created.
|
|
111
|
+
- The next steps depend on the scripts in the created app's `package.json`. With `setup` and `infra:up` (apps scaffolded since `yarn setup` starts Docker), they are `yarn setup` and the `yarn setup --no-infra` alternative for your own services, like a normal scaffold; `cp .env.example .env` and the env keys come first only when the template declares keys. With `setup` but no `infra:up`, they are `cp .env.example .env`, the env keys, `docker compose up -d` (or a note to start PostgreSQL, Redis and Meilisearch yourself) and `yarn setup`. With neither, they are `cp .env.example .env`, the env keys, `yarn install`, `yarn initialize` and `yarn dev`.
|
|
112
|
+
|
|
113
|
+
Set `OM_TEMPLATES_URL` to read another index, for example a local copy. It must be an `https` URL, or `http` on `localhost`, `127.0.0.1` or `[::1]`.
|
|
114
|
+
|
|
90
115
|
## Ready App Behavior
|
|
91
116
|
|
|
92
117
|
- `--app <name>` resolves to `open-mercato/ready-app-<name>` and fetches the exact tag `v<create-mercato-app version>`
|
|
93
118
|
- `--app-url <url>` only supports GitHub repository URLs in v1 and honors `/tree/<ref>` when present
|
|
94
119
|
- `--app` and `--app-url` are mutually exclusive
|
|
95
120
|
- `--skip-agentic-setup` skips only the interactive agentic setup wizard
|
|
96
|
-
- Imported ready apps are copied as raw source snapshots: the CLI does not rewrite dependency versions, package names, or application source files
|
|
121
|
+
- Imported ready apps are copied as raw source snapshots: the CLI does not rewrite dependency versions, package names, or application source files. `--template` makes the three changes listed under [App Templates](#app-templates)
|
|
97
122
|
- Imported ready apps skip the interactive agentic setup wizard; if you want agentic tooling later, run `yarn mercato agentic:init` inside the generated app
|
|
98
123
|
- `--agents` is only supported for bare scaffolds; use `yarn mercato agentic:init` after importing a ready app
|
|
99
124
|
- Imported ready apps must not contain `.template` files; the scaffold fails closed if template files are found
|
|
125
|
+
- When `open-mercato/ready-app-<name>` does not exist, the `--app` error points to app templates
|
|
126
|
+
- Every import (`--app`, `--app-url` and `--template`) is inspected before the app directory is created: the download is at most 64 MiB, the archive holds at most 10,000 entries and 128 MiB unpacked, and only files and directories are allowed. A link, a special file, an absolute path or a `..` segment stops the import and names the path
|
|
100
127
|
|
|
101
128
|
## Standalone AI Harness
|
|
102
129
|
|
|
@@ -275,9 +302,11 @@ The standalone dev splash also exposes a GitHub publishing panel after `yarn dev
|
|
|
275
302
|
|
|
276
303
|
## After Importing A Ready App
|
|
277
304
|
|
|
305
|
+
For an app created with `--template`, follow the next steps the CLI prints. They match the scripts the app has: `yarn setup` for an app with `setup` and `infra:up`, the services first and then `yarn setup` for an older `setup`, otherwise the steps below. The env keys the template declares are listed with them.
|
|
306
|
+
|
|
278
307
|
1. Navigate to your app directory:
|
|
279
308
|
```bash
|
|
280
|
-
cd my-
|
|
309
|
+
cd my-app
|
|
281
310
|
```
|
|
282
311
|
|
|
283
312
|
2. Install dependencies:
|
|
@@ -1,10 +1,10 @@
|
|
|
1
1
|
# Standalone Architecture and Discovery
|
|
2
2
|
|
|
3
|
-
|
|
3
|
+
Choose ownership, locate module surfaces, and keep generated discovery correct.
|
|
4
4
|
|
|
5
5
|
## Context Ownership and Scattering
|
|
6
6
|
|
|
7
|
-
|
|
7
|
+
Load precise context through these layers:
|
|
8
8
|
|
|
9
9
|
| Layer | Owns | Loading rule |
|
|
10
10
|
|---|---|---|
|
|
@@ -15,9 +15,9 @@ The harness is intentionally layered so an agent can assemble precise context wi
|
|
|
15
15
|
| `om-framework-context` output | Exact installed instructions, source/types, and bounded search results | Last-mile escalation after app call sites, facts, and concept guides cannot answer the question. |
|
|
16
16
|
| External `open-mercato/skills` | SDLC and delivery workflows | Select independently only when the requested lifecycle needs one. |
|
|
17
17
|
|
|
18
|
-
Match area, work units, and delivery independently
|
|
18
|
+
Match area, work units, and delivery independently; de-duplicate paths and skills. Split business tasks into entity, command, API, admin UI, public capture, CRM extension, event, and provider units; give each only its owning area and contract. Do not preload all module facts, skill references, upstream guides, or installed package source.
|
|
19
19
|
|
|
20
|
-
|
|
20
|
+
Facts identify existing identifiers and surfaces; exact installed source shows how this version implements or types the contract. Source is read-only evidence, never a writable escape hatch.
|
|
21
21
|
|
|
22
22
|
## Ownership Decision
|
|
23
23
|
|
|
@@ -40,7 +40,7 @@ src/modules.ts enabled modules and supported overrides
|
|
|
40
40
|
node_modules/@open-mercato/*/ exact installed packages, read-only
|
|
41
41
|
```
|
|
42
42
|
|
|
43
|
-
Do not copy
|
|
43
|
+
Do not copy installed modules to learn them. Generated facts and the context resolver expose exact installed source without widening the writable surface.
|
|
44
44
|
|
|
45
45
|
## Canonical Module Shape
|
|
46
46
|
|
|
@@ -93,6 +93,8 @@ The app root governs writable locations and safety. The compatibility snapshot g
|
|
|
93
93
|
|
|
94
94
|
For creation, publication, and continued repository development of one app module, read `.ai/guides/module-tool.md`.
|
|
95
95
|
|
|
96
|
+
To save an app template or create an app from one, read `.ai/guides/template-tool.md`.
|
|
97
|
+
|
|
96
98
|
## Package and Bootstrap Boundaries
|
|
97
99
|
|
|
98
100
|
- Import public package exports; do not reach through monorepo-only relative paths or app-generated registries from a package.
|
|
@@ -0,0 +1,38 @@
|
|
|
1
|
+
# Save and Create App Templates
|
|
2
|
+
|
|
3
|
+
An app template is a GitHub repository with a complete standalone app at its root. Use [create-mercato-template](https://github.com/open-mercato/create-mercato-template#readme) to save this app as one, and `create-mercato-app --template` to create a new app from one. A template is code only: the committed files of one commit. The database, configuration made in the UI, uploads, `.env` files, Git history and registry credentials are never saved. Move anything the next app needs into code (seeds, setup scripts) and commit it first.
|
|
4
|
+
|
|
5
|
+
Save a reviewed snapshot from the app root:
|
|
6
|
+
|
|
7
|
+
```bash
|
|
8
|
+
npx create-mercato-template prepare --out ../my-template
|
|
9
|
+
```
|
|
10
|
+
|
|
11
|
+
It reads the committed `HEAD` offline, runs no app code and never changes the app. `--out` must be a new or empty directory outside the app. Uncommitted changes are listed but not exported unless `--include-uncommitted` is given. The result is `<out>/tree` and `<out>/report.json` with a `snapshotId`. An error finding (a secret, a symlink, a database dump, a missing `yarn.lock`) stops it: fix the source, commit, and run `prepare` again. Use `--allow-file <path>` or `--keep-env <KEY>` only when the user confirms that file or value may be shared. Show the user the report before publishing: errors, warnings, emptied env keys, the module list, uncommitted files and every image path, because images are not scanned and the user must inspect them.
|
|
12
|
+
|
|
13
|
+
Publish only after the user approves the repository name, the visibility and the reviewed `snapshotId`:
|
|
14
|
+
|
|
15
|
+
```bash
|
|
16
|
+
npx create-mercato-template publish --from ../my-template --repo your-name/my-template --private --expect <snapshotId>
|
|
17
|
+
```
|
|
18
|
+
|
|
19
|
+
It needs `gh auth login` and never reads or prints a token. Visibility is always explicit (`--public` or `--private`); never choose it for the user. `--expect` is required with `--json` and without a terminal. It pushes exactly the snapshot as one commit, marks the repository as a template and adds its topics. It never force-pushes. After a failed GitHub step, rerun the printed command with `--resume`. With `--json`, read the exit code: 0 done, 1 a check failed or publication was refused, 2 usage, 3 GitHub auth missing, 4 a GitHub step failed.
|
|
20
|
+
|
|
21
|
+
To list the template in the catalog:
|
|
22
|
+
|
|
23
|
+
```bash
|
|
24
|
+
npx create-mercato-template describe --from ../my-template
|
|
25
|
+
```
|
|
26
|
+
|
|
27
|
+
It prints the catalog YAML and the CONTRIBUTING link. Listing is a pull request the user opens in `open-mercato/modules`; neither tool opens it.
|
|
28
|
+
|
|
29
|
+
Create a new app from a template outside this app's directory:
|
|
30
|
+
|
|
31
|
+
```bash
|
|
32
|
+
npx create-mercato-app my-app --template your-name/my-template
|
|
33
|
+
npx create-mercato-app my-crm --template crm
|
|
34
|
+
```
|
|
35
|
+
|
|
36
|
+
`--template` takes a curator slug or `owner/repo`, optionally with `#ref`; a private repository needs `GITHUB_TOKEN`. Before the download it prints `owner/repo@<sha>` and whether that commit is verified, and it refuses a template on hold. The new app gets the app name in `package.json` (unless `--keep-name`), an `openMercatoTemplate` field with the repository, ref and commit, and no `mercato-template.json`. Then follow the printed next steps, which match the app's scripts: `yarn setup` when it has `setup` and `infra:up`; `docker compose up -d` then `yarn setup` when it has only `setup`; otherwise `yarn install`, `yarn initialize`, `yarn dev`. The declared env keys are listed before the start commands. Imports get no agentic setup; run `yarn mercato agentic:init` inside the new app when wanted.
|
|
37
|
+
|
|
38
|
+
If `npx create-mercato-template` is not available from npm yet, run it from GitHub: `npx --package github:open-mercato/create-mercato-template create-mercato-template --help`. Without process execution, report that capability gap instead of claiming a snapshot or a publication.
|
|
@@ -73,6 +73,7 @@ Open every matched work-unit skill before selection.
|
|
|
73
73
|
| Route | Work unit | Skill/context |
|
|
74
74
|
|---|---|---|
|
|
75
75
|
| `architecture` | Find, scaffold a module starter, publish, or link an app module | `.ai/guides/module-tool.md`; find: `om-find-module`; new code loads `om-module-scaffold` |
|
|
76
|
+
| `architecture` | Save this app as an app template, or create an app from one | `.ai/guides/template-tool.md` |
|
|
76
77
|
| `architecture` | Explain/choose module, UMES, package, eject | architecture; `om-help` for an unresolved or comparative choice across these mechanisms |
|
|
77
78
|
| `module-data` | Business slice or multi-seam domain/API/command fix | MUST load `om-module-scaffold` + its exact `.ai/skills/om-module-scaffold/references/business-one-shot-blueprints.md` key, which resolves units inside the slice, not ownership — an ownership/capability outline adds `architecture` |
|
|
78
79
|
| `spec-pr` | Spec/plan | Axis 3; phases+integration coverage (`integration-coverage`); no domain routes |
|
|
@@ -1,10 +1,10 @@
|
|
|
1
1
|
# Standalone Architecture and Discovery
|
|
2
2
|
|
|
3
|
-
|
|
3
|
+
Choose ownership, locate module surfaces, and keep generated discovery correct.
|
|
4
4
|
|
|
5
5
|
## Context Ownership and Scattering
|
|
6
6
|
|
|
7
|
-
|
|
7
|
+
Load precise context through these layers:
|
|
8
8
|
|
|
9
9
|
| Layer | Owns | Loading rule |
|
|
10
10
|
|---|---|---|
|
|
@@ -15,9 +15,9 @@ The harness is intentionally layered so an agent can assemble precise context wi
|
|
|
15
15
|
| `om-framework-context` output | Exact installed instructions, source/types, and bounded search results | Last-mile escalation after app call sites, facts, and concept guides cannot answer the question. |
|
|
16
16
|
| External `open-mercato/skills` | SDLC and delivery workflows | Select independently only when the requested lifecycle needs one. |
|
|
17
17
|
|
|
18
|
-
Match area, work units, and delivery independently
|
|
18
|
+
Match area, work units, and delivery independently; de-duplicate paths and skills. Split business tasks into entity, command, API, admin UI, public capture, CRM extension, event, and provider units; give each only its owning area and contract. Do not preload all module facts, skill references, upstream guides, or installed package source.
|
|
19
19
|
|
|
20
|
-
|
|
20
|
+
Facts identify existing identifiers and surfaces; exact installed source shows how this version implements or types the contract. Source is read-only evidence, never a writable escape hatch.
|
|
21
21
|
|
|
22
22
|
## Ownership Decision
|
|
23
23
|
|
|
@@ -40,7 +40,7 @@ src/modules.ts enabled modules and supported overrides
|
|
|
40
40
|
node_modules/@open-mercato/*/ exact installed packages, read-only
|
|
41
41
|
```
|
|
42
42
|
|
|
43
|
-
Do not copy
|
|
43
|
+
Do not copy installed modules to learn them. Generated facts and the context resolver expose exact installed source without widening the writable surface.
|
|
44
44
|
|
|
45
45
|
## Canonical Module Shape
|
|
46
46
|
|
|
@@ -93,6 +93,8 @@ The app root governs writable locations and safety. The compatibility snapshot g
|
|
|
93
93
|
|
|
94
94
|
For creation, publication, and continued repository development of one app module, read `.ai/guides/module-tool.md`.
|
|
95
95
|
|
|
96
|
+
To save an app template or create an app from one, read `.ai/guides/template-tool.md`.
|
|
97
|
+
|
|
96
98
|
## Package and Bootstrap Boundaries
|
|
97
99
|
|
|
98
100
|
- Import public package exports; do not reach through monorepo-only relative paths or app-generated registries from a package.
|