project-discover-memory-index (Step2+3: Level-0 Memory + Level-1 Index Skeleton)

Overview

Output Directory (Standard Persistence)

.aisdlc/project/
  memory/
    structure.md
    tech.md
    product.md
    glossary.md
  components/
    index.md
  products/
    index.md

Note: Do not create

.aisdlc/project/contracts/**

at this stage; contract entries will be redirected via module page anchors.

Level-0: Memory Writing Constraints (Must be short)

General Hard Rules

• Only write stable entries and boundaries: Entry links > long explanatory texts
• Avoid one-time delivery of details: Detailed migration steps/detailed timing/field-level constraints are not written in project-level memory
• Links must be locatable: Prioritize links to specific files, specific jobs, specific command entries in the repository
• Gaps must be structured: Uniformly written to

  ## Evidence Gaps

memory/structure.md

Minimum Template

# 结构与入口（北极星）

## 项目形态
- 单体/多服务/Monorepo：<证据入口链接>

## 入口（可执行证据）
- 本地启动：<脚本/命令入口链接>
- 测试：<脚本/命令入口链接>
- 构建/发布：<CI job/脚本入口链接>

## 代码地图
- 组件地图：../components/index.md
- 业务地图（如有）：../products/index.md
- Ops 入口（如有）：../ops/index.md

## Evidence Gaps（缺口清单）
- 缺口：
  - 期望补齐到的粒度：
  - 候选证据位置：
  - 影响：

memory/tech.md

Minimum Template

# 技术栈与工程护栏

## 技术栈（稳定选择）
- 语言/框架：
- 数据库/缓存/消息：

## 质量门禁入口（可执行证据）
- lint：
- test：
- 安全扫描：

## NFR 入口
- 性能/可用性/成本/安全：../nfr.md（或外部权威链接）

## Evidence Gaps（缺口清单）
...

memory/product.md

Minimum Template

# 业务边界（稳定语义）

## In / Out
- In：
- Out：

## 业务地图入口
- ../products/index.md（如有）

## 术语入口
- ./glossary.md

## Evidence Gaps（缺口清单）
...

memory/glossary.md

Minimum Template

# 术语表（短）

| 术语 | 一句话定义 | 权威出处 |
|---|---|---|
| xxx | ... | <链接到模块页锚点/ADR/代码证据> |

Level-1: Index Skeleton (Map Layer) Constraints

Index Hard Rules (Verifiable)

• components/index.md

  and

  products/index.md

  only for navigation
• Prohibit the following content in the index:
  • Invariant summary
  • Fields/error codes/detailed processes
  • "To be filled/Not found/TODO/To be confirmed"
• The index uses checkboxes as a progress panel, but must not be used as a basis for completion judgment (completion only depends on whether the module page meets the standards)

components/index.md

Minimum Template (Including Dependency Graph)

# Components Index（地图层：只导航）

| module | priority | owner | code_entry | api_contract | data_contract | ops_entry | status |
|--------|----------|-------|------------|--------------|---------------|-----------|--------|
| auth | P0 | team-x | `src/auth/` | [api](./auth.md#api-contract) | [data](./auth.md#data-contract) | [ops](../ops/index.md) | - [ ] |

## Dependencies（direct only）

```mermaid
graph LR
  auth -->|API| user
  order -->|Event| billing

> **Maintenance Rule**: Only draw **direct dependencies** (first-level calls), do not draw transitive dependencies; edges mark interaction methods (API/Event/DB).

### `products/index.md` Minimum Template (Optional, but Recommended)

```markdown
# Products Index（业务地图：只导航）

> 建议收敛到 <= 6 个业务模块；这里不是功能清单。

| product | owner | entry | related_components | status |
|---|---|---|---|---|
| commerce | team-a | ./commerce.md | auth, order | - [ ] |

Red Flag List

• Memory is written as a "complete operation manual" (project-level memory must be short)
• "To be filled/Not found/TODO" appears in the index (gaps should be entered in the module page or Evidence Gaps of memory)
• Copy module details in the index (double writing will definitely cause drift)

Common Mistakes

• Write module page details first and then supplement the index (will induce index double writing)
• Turn Products into a function directory of more than 20 modules (the map becomes invalid)