30 lines
2.0 KiB
Markdown
30 lines
2.0 KiB
Markdown
# 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](../../AGENTS.md) |
|
|
| 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](../../README.md) |
|
|
| ROUTE-001 | The machine registry is the authority for 18 parser routes; the two passenger-list routes are Program-only. | Active | 2026-08-28 | Manual and AgentBus intake | [Machine registry](../../control-plane/src/business-routes.ts) |
|
|
| 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](../../dist/release-manifest.json) |
|
|
| 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](../../AGENTS.md) |
|
|
| 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](../../agent设计规范/agentbus-reply-contract.md) |
|
|
|
|
## Superseded Decisions
|
|
|
|
| ID | Decision | Superseded By | Date |
|
|
|---|---|---|---|
|
|
| DOC-LEGACY-001 | Root `task_plan.md`, `findings.md`, and `progress.md` were the active project-memory system. | DOC-001 | 2026-08-28 |
|
|
|
|
## 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
|