Package layers models, config, storage, jobs, web, cli, held by tests/test_architecture.py with desk and pipeline as external trees and plugins/ limited to desk. roles.yaml is the default config, roledesk.db its own file, port 8790. create_app mounts pipeline.web.connect over Jobs(config.database); `roledesk job pull` drains a no-op pull and `roledesk db init` creates the file. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
31 lines
1.1 KiB
Markdown
31 lines
1.1 KiB
Markdown
# Rule:
|
|
|
|
Committed in main, branch deleted means the work is done. Having code uncommitted or committed in a branch or worktree means you failed to deliver. Pushing is not a thing we really care about.
|
|
|
|
# Rule:
|
|
|
|
MDs dont have hard wraps. IF you come across one make it soft wrapping
|
|
|
|
# Rule:
|
|
|
|
In documentations so not write bloat like:
|
|
|
|
> The obvious objection, answered before it's asked. "They just open a new session." Yes. **That's friction, not a wall, and it's meant to be.**
|
|
|
|
Instead, write more concise, more technical English, e.g. :
|
|
|
|
> One objection is that they just open a new session. Yet, this friction is by design because ...
|
|
|
|
Bad Example:
|
|
|
|
> **Could we verify them first to save the human a step?** Only if the receiving system will accept our verification. If it re-authenticates anyway we've added a step to save none — worth asking in a real deployment, not worth assuming.
|
|
|
|
Good example:
|
|
|
|
> We should only verify them first, if the receiving system will accept our verification? Otherwise it double work for the customer.
|
|
|
|
|
|
# Rule:
|
|
|
|
`desk` and `pipeline` are imported from ../news and never edited here.
|