Files
LWLT-AIBOT/.project-docs/10-decisions/decision-index.md

4.8 KiB

Decision Index

Active Decisions

ID Decision Status Date Applies To Detail
DOC-001 .project-docs/ is the sole active project-memory system; feature tasks own task-scoped records and Integration Gate owns canonical memory. Active 2026-08-28 All repository work Governance
ARCH-001 AI parsers provide business semantics only; platform state, ERP resolution, execution evidence, and audit remain outside the business operation. Active 2026-08-28 Parser and execution architecture System entry
ROUTE-001 The machine registry is the authority for 19 parser routes; 18 remain available to the external Agent and three routes are Program-only. Active 2026-09-09 Manual and AgentBus intake Machine registry
RELEASE-001 Current artifacts, filenames, versions, and SHA-256 values are defined only by dist/release-manifest.json. Active 2026-08-28 Release and delivery Release manifest
SAFETY-001 Real ERP access/write, task mutation, extension reload, service restart, deployment, and external delivery require explicit task-scoped authorization. Active 2026-08-28 Operations and maintenance Governance
NETWORK-001 In the trusted internal deployment, AgentBus roster attachment URLs may resolve to internal/private addresses; HTTPS, credential rejection, DNS pinning, redirect validation, bounds, and digest checks remain. Active 2026-08-31 AgentBus attachment ingress Reply contract
AUTH-001 The fixed deployment scope uses administrator-managed admin, team_lead, and user accounts, explicit employee route grants, and assignee-bound AgentBus/browser/ERP execution. Active except clauses superseded by AUTH-002 and AUTH-004 2026-09-01 Authentication, authorization, audit, AgentBus workers, and operations oversight ADR
AUTH-002 ERP execution is serialized per immutable assigned account, and explicit owner force delete physically removes authorized tasks regardless of lifecycle state. Active except administrator task-access clauses superseded by AUTH-004 2026-09-03 ERP claim queues, executable events/results, and task removal ADR
AUTH-003 Team-lead summaries used a current-owner AgentBus route and separate encrypted outbox without granting task or ERP authority. Superseded in transport/activation by AUTH-005; retained for projection/privacy history 2026-09-07 Historical leader-summary AgentBus routing ADR
AUTH-004 Administrators are management-plane-only identities; team leads alone receive an assignee-based, cross-source operations dashboard while employee task operations remain owner-only. Active 2026-09-07 Administrator isolation, task APIs, database principals, and leadership oversight ADR
AUTH-005 Organization-wide leader summaries use one protected external Webhook, a future-only encrypted outbox, strict accepted-versus-delivered terminology, and terminal one-attempt failure semantics without changing normal AgentBus/task/ERP behavior. Active 2026-09-09 Leader-summary projection and external delivery ADR

Superseded And Reverted Decisions

ID Decision Resolution Date
DOC-LEGACY-001 Root task_plan.md, findings.md, and progress.md were the active project-memory system. DOC-001 2026-08-28
AUTH-001 (partial) Organization-wide ERP FIFO and archive-only operator removal. AUTH-002 2026-09-03
AUTH-001 / AUTH-002 (partial) Administrator task creation, task-wide reads, dashboard access, task transitions, and force-delete authority; manual-only leadership dashboard scope. AUTH-004 2026-09-07
AUTH-003 (transport and activation) Team-lead identity/channel activation, learned AgentBus/WeChat routing, and at-least-once task.summary frames. AUTH-005 2026-09-09
EXT-001 Central-service private-OSS and ECS Cloud Assistant orchestration for shared unpacked-extension updates. Server architecture reverted by explicit user decision; exact full implementation remains on codex/backup-extension-update-20260903-b2e33e2, while the active manually distributed plugin has advanced to 0.5.170. 2026-09-03

Decision Criteria

Create or update an ADR when a choice affects:

  • project positioning
  • architecture boundaries
  • public behavior
  • data model
  • long-term maintenance
  • user-facing workflow