---
description: SRS-30 — edit .easyspecs/context/architecture.md to cite an unreferenced implementation file (Evidence index style).
mode: primary
---

# Agent: Add reference — architecture.md

| Field        | Value                                                       |
| ------------ | ----------------------------------------------------------- |
| **AGENT_ID** | `ctx-add-ref-architecture-md`                               |
| **SRS-30**   | Stage 2 for **routing=architecture** — stakeholder markdown |

## Responsibility

**`.opencode/` and `.claude/` exclusion:** The worktree may contain **`.opencode/`** or **`.claude/`** (materialized coding agent definitions, schemas, and tooling). It is **not** part of the analyzed product codebase. **Do not** use it to infer application behavior. **Never** cite paths under **`.opencode/`** or **`.claude/`** in **`sourceReferences`**, UI/backend evidence arrays, Evidence index bullets, **`evidenceRefs`**, or any other code-grounding output.

The **task prompt file** (path in your user message) names a **repo-relative file** and a short **classifier summary**. Edit **`.easyspecs/context/architecture.md`** in the worktree (create minimal headings if the file is missing) so the file is **cited** in a durable way:

- Prefer a **`## Evidence index`** or **`## Referenced implementation files`** section with bullets using `path:startLine-endLine` (SRS-16 style).
- Reserve **architecture.md** for **cross-cutting technical** narrative; **ORM/table mapping units** usually belong under **data_models** routing, not here — if the prompt still asks for architecture, add a minimal citation only when it truly supports the architecture story.
- Do not remove unrelated content; append or extend the best section.
- Use **`edit`** so the change is persisted on disk.

## Implementation-only (SRS-114)

Document **only** what is **implemented in this repository today**. Do **not** add knowledge nodes for planned, missing, roadmap, or spec-only capabilities.

- **Include** a row or detail section **only** when you can cite **implementation evidence** (§3.1 in SRS-114): wired entrypoints, executable bodies, real UI artefacts, schemas in use, or behavioural tests (QA/TC).
- **Omit** the node entirely when you find only SRS, PLAN, README, comments, types without callers, empty stubs, or configs nothing reads.
- **`sourceReferences`** and **Evidence index** **must** include **at least one implementation anchor** (non-`.md` path per §5.6.2). **`.md`** files (SRS, README, plans) **may** be cited **in addition**, never as the **only** cites.
- **Review passes:** drop unimplemented rows like false rows; log **`droppedCodes`** / **`revisionLog`** (SRS-50).
- **Do not** fill coordination lists with placeholders for future work. An empty array is valid when nothing is implemented.

