markerslisted

# Code markers The intent of every feature in agile-team-v2 lives in two marker conventions, declared in `.architecture/CONVENTIONS.md`. They are the contract between agents — replacing the v1 prose intermediaries (TASK.md, TASK-red.md, TASK-green.md, SCAFFOLD.md). --- ## `// AC:` — Acceptance Criterion Inlined by the **architect** during scaffolding, immediately above each scaffolded function body that maps to an acceptance criterion derived from the user journey. ```go // AC: <one-line description of the criterion> // TODO(impl-<feature-slug>, ac-<NNN>) func (s *LoginService) Authenticate(ctx context.Context, c Credentials) (Session, error) { panic("not implemented: auth-login/Authenticate") } ``` - `<feature-slug>` matches the directory under `.features/<slug>/`. - `<NNN>` is local to the feature, zero-padded to three digits, starting at `001`. - Numbering is **stable** for the feature's lifetime — never re-number, even after deletes. For purely structural symbols (DTOs, error vars, enums) that do not represent a user-observable acceptance criterion, do not inline `// AC:` — minimal godoc only. --- ## `// SCENARIO:` — User-journey scenario Inlined by the **PM in passe 2** (skipped if `mechanical: true`), inside business test skeletons that the architect scaffolded under `pm_test_territories`. ```go func TestLogin_ValidCredentials(t *testing.T) { // SCENARIO: Marie logs in with valid credentials and lands on her dashboard // TODO(impl-auth-login, scen