Idea detail
faq_drift
reqlan rq/site/site.rq:387
block
done
Summary
The FAQ includes this question: How do you keep `.rq` files from drifting once the code moves on?
`.rq` files are code. They are the source of truth. They are not a document.
Specify material work as an idea first.
Implementation and tests point back with rq-comments per code_comment_references and testing.
A check requires each test to serve a requirement.
Agents see only the ideas that attach to the files they touch.
Mark a replaced idea deprecated and point to the new idea.
The indexer flags missing references like a compile check.
Copy lives in faq.ts ( item id `drift` ) per copy and faq_page.
The sidebar nests this question as a same-page child per sidebar_nav.
Navigation
Attributes
Ancestor context
No ancestor chain recorded.
Outbound references
| Kind | Idea | Path | Snippet |
|---|---|---|---|
| references | code_comment_references | reqlan rq/development/core.rq | code_comment_references |
| references | testing | reqlan rq/development/core.rq | testing |
| file_reference | "../../site/src/content/faq.ts" | site/src/content/faq.ts | faq.ts |
| references | copy | reqlan rq/site/site.rq | copy |
| references | faq_page | reqlan rq/site/site.rq | faq_page |
| references | sidebar_nav | reqlan rq/site/site.rq | sidebar_nav |
| file_reference | "../../site/src/content/nav.ts" | site/src/content/nav.ts | nav.ts |
| file_reference | "../../site/src/content/faq.test.ts" | site/src/content/faq.test.ts | faq.test.ts |
| comment_link | faq_drift | reqlan rq/site/site/src/content/faq.test.ts | // rq:faq_drift |
| comment_link | faq_drift | reqlan rq/site/site/src/content/faq.ts | // rq:faq_drift |
| comment_link | faq_drift | reqlan rq/site/site/src/content/nav.ts | // rq:faq_drift |
Inbound references
Unresolved references
| Kind | Idea | Path | Snippet |
|---|---|---|---|
| None | |||
Local graph
Initialising graph…