wangxuming/LWLT-AIBOT
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: record simplified password lifecycle

Browse Source
This commit is contained in:
inman committed 2026-09-02 11:23:02 +08:00
1 parent 029c8c6a59
commit ed456e6a5d
7 files changed
+62 -4
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

.project-docs/20-architecture/system-overview.md
+2 -1
View File
@@ -22,6 +22,7 @@ Authenticated manual or AgentBus input is routed through task-scoped AI/Shadow/A
- AI/Program parsing and ERP resolution/execution share the final operation contract but do not share authority.
- Platform envelope fields such as task ID, account identity, authorization revision, session, parser decision, confirmation, transport, and audit never enter the business operation.
- The product is one fixed internal organization scope with three roles. Administrators manage accounts and all 18 manual routes; team leads and users are owner-scoped for normal tasks and require explicit per-route grants. Team leads additionally receive a dedicated read-only, manual-task-only platform-operations dashboard.
- Account passwords are accepted when non-empty without an application-level length rule. First-login forced password changes are disabled; voluntary changes and administrator resets still revoke the relevant sessions, while the historical `must_change_password` column remains compatibility-only storage.
- The leadership dashboard is an aggregate-first projection across task, person, original input, final output, time, task type, and completion state. Its drill-through stays business-facing; technical payloads, internal identifiers, machine-shaped historical input, and technical failure text remain in separate authorized audit/engineering surfaces.
- Authorization is enforced in server and service paths, not by navigation visibility. A denied or unresolved non-admin business route stops before parsing, plugin dispatch, and ERP execution; creator authorization is rechecked at confirmation and browser claim.
- Creator and manual input-turn attribution remain durable while business input stays encrypted at rest. Routine removal is reversible archive/restore; physical purge is not an operator capability.
@@ -44,4 +45,4 @@ Authenticated manual or AgentBus input is routed through task-scoped AI/Shadow/A
## Last Updated
2026-09-01
2026-09-02