@lotics/cli 0.318.20 → 0.318.22
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/AGENTS.md +2 -2
- package/dist/src/cli.js +22 -14
- package/docs/app_architecture.md +21 -19
- package/docs/building_an_app.md +1 -1
- package/docs/design.md +45 -47
- package/docs/document_templates.md +5 -3
- package/docs/first_build.md +4 -21
- package/docs/getting_started.md +1 -1
- package/docs/workflows.md +6 -4
- package/docs/working_in_a_workspace.md +10 -0
- package/package.json +1 -1
package/AGENTS.md
CHANGED
|
@@ -9,11 +9,11 @@ conventions are, and where the traps are.
|
|
|
9
9
|
| `lotics tools` · `lotics tools <name>` | The agent tool registry and one tool's full JSON Schema. |
|
|
10
10
|
| `lotics docs` · `lotics docs <area>[/<section>]` · `lotics docs [<area>] --grep <text>` | This CLI's references, carried inside it so each describes the binary answering. Capped at a page: a doc that does not fit hands back its opening and the addresses into it, so the next call is smaller than the last. A page the copy lacks — one the server added since this binary was built, which a refusal can cite — is read from the server's `docs` tool with this machine's credential, and so is every `--grep`, over the references the server serves. A custom-code app's SDK reference is `node_modules/@lotics/app-sdk/AGENTS.md` inside the app. |
|
|
11
11
|
| `lotics docs reference` · `lotics docs reference/<section>` | The keys of a table document and the components of an app tree: a table's fields keyed by alias, how a row of each table is recognised (`records`), and the apps stated over them. Every key, every field type with the config it needs, the rules, and a worked example. |
|
|
12
|
-
| `lotics docs design` · `lotics docs design/<section>` | Designing an app — the treatment each kind of row takes with the `reference` page stating its keys, the visual bar, and looking at what a write built. Opens on the
|
|
12
|
+
| `lotics docs design` · `lotics docs design/<section>` | Designing an app — the treatment each kind of row takes with the `reference` page stating its keys, the visual bar, and looking at what a write built. Opens on the visual bar; a finding names its section. |
|
|
13
13
|
| `lotics docs examples` · `lotics docs examples/<treatment>` | Each treatment worked through in an app of a complete workspace: the job, the props to read, where it is the wrong one, and the excerpt. |
|
|
14
14
|
| [docs/getting_started.md](./docs/getting_started.md) | What a workspace holds, and the one page to open for each job: building a workspace, changing an app, a rule on a table, a document, data and questions, a connected service, sharing. The first page an agent outside the product reads. |
|
|
15
15
|
| [docs/first_build.md](./docs/first_build.md) | A whole workspace built call by call — understand the work, tables with a check, the paper, the app (which apps, a treatment per kind of row, what the check refuses, who gets it), the owner's rows, pressing it — in one worked example. |
|
|
16
|
-
| [docs/app_architecture.md](./docs/app_architecture.md) | One factory's split into apps: each app's
|
|
16
|
+
| [docs/app_architecture.md](./docs/app_architecture.md) | One factory's split into apps, one per main entity: each app's list, who opens it and what its rows' pages hold. The rule is in first_build. |
|
|
17
17
|
| [docs/working_in_a_workspace.md](./docs/working_in_a_workspace.md) | The right means for each job once the apps exist: an app's act for a business operation, a record write for data entry, a query for a figure the business defines, a count for the rest. |
|
|
18
18
|
| [docs/building_an_app.md](./docs/building_an_app.md) | The SEQUENCE — clarify, tables, apps, prove, look — for an app stated as a tree and for a custom-code app. Read it once before starting an app. Looking is `lotics run screenshot_app '<json>' -o <dir>`, which saves each PNG and its text snapshot there. |
|
|
19
19
|
| [docs/cli_reference.md](./docs/cli_reference.md) | Per-command contracts, flags, exit codes, and gotchas — the detail `--help` compresses. |
|