diff options
| author | Craig Jennings <c@cjennings.net> | 2026-05-26 07:36:51 -0500 |
|---|---|---|
| committer | Craig Jennings <c@cjennings.net> | 2026-05-26 07:36:51 -0500 |
| commit | b255a74441c936f8e27859d57402a15170dcd73a (patch) | |
| tree | 7f84e6b5c324dae2a943eee21320be41a31e9d8e /scripts | |
| parent | 4fac2a09e5bd395f4058f2e2f5a3e1dab662af87 (diff) | |
| download | rulesets-b255a74441c936f8e27859d57402a15170dcd73a.tar.gz rulesets-b255a74441c936f8e27859d57402a15170dcd73a.zip | |
docs(protocols): document .ai/project-scripts/ for project-owned scripts
A project script dropped into .ai/scripts/ gets wiped on the next startup, because that dir syncs from the template with rsync --delete. There was no documented home for a project's own scripts, the script-side counterpart to .ai/project-workflows/.
I added .ai/project-scripts/ to the Directory Architecture table and noted in startup.org that it sits outside the synced set, like project-workflows/. A script a workflow imports lives there. Naming: a Python module imported via sys.path needs an importable name (underscores), while a CLI-invoked script can stay kebab-case like the template tooling.
No mechanism change. Startup Phase A only rsyncs protocols.org, workflows/, and scripts/, so project-scripts/ is already sync-safe. This just documents it.
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions