reflect on yak usage with qwen3.6-35B

AGENTS.md

@@ -3,6 +3,38 @@
 This project has a *zero defects policy*. 
 When you are unsure about something, ALWAYS ask the user.
 
+# Repository structure
+
+This is an Elixir monorepo with two parts:
+
+```
+firehose/
+├── app/                    # Phoenix application (OTP app: :firehose)
+│   ├── lib/firehose/       # Application logic
+│   ├── lib/firehose_web/   # Web layer (controllers, live views, components)
+│   ├── lib/firehose/blogs/ # Blog definitions (engineering, release notes)
+│   ├── priv/blog/          # Markdown posts
+│   └── mix.exs
+├── blogex/                 # Blogex library (multi-blog engine)
+│   ├── lib/
+│   └── mix.exs
+├── mise.toml               # Runtime versions (Elixir, Erlang, Node)
+└── Makefile                # make (test, check) 
+```
+
+Two blogs are configured:
+
+| Blog | Route | Description |
+|------|-------|-------------|
+| Engineering | `/blog/engineering` | Main blog | 
+| Release Notes | `/blog/releases` | What's new in an app |
+
+# Permissions
+
+ALWAYS ask the user for permission when you want to add a fallback, or are unsure something work. The user can perform exploratory testing.
+
+We have a zero defects policy, so never continue when there are errors, warnings or test failures, even when they are pre-existing. ALWAYS report these to the user and discuss an action plan with root cause analysis. (see TDD below).
+
 # Planning
 
 we use  `yx` for planning run yx --help to see options. Invoke when the user wants to make a plan, work on something for a plan or mentions 'yak' or 'yaks'.