Idea detail
gs_07_link_code
reqlan rq/marketing_and_media/tutorials.rq:933
block
Summary
Audience: users with application source beside `reqs/` who completed gs_01 – 06.
Outcome: add a file reference from an idea to implementation; open the file from the requirement; see reverse scope when standing in code; recap the get-started loop into Concepts.
Runtime: 6 – 7 min.
Demo: base active. `reqs/product.rq` with linked ideas and `password_rules`. No `reqs/auth.rq` yet. No `src/` folder. Caret in `product.rq`. Explorer shows only `reqs/` and `.reqlan/`.
Related: any_file_scope context_scope reference referenced_files file
Attributes
| Key | Value |
|---|---|
| example | ```rq // reqs/auth.rq login_api { POST /login validates credentials and starts a session. Implementation: login.ts Rejects empty passwords per password_rules. } ``` ```ts // src/login.ts export async function login(email: string, password: string) { if (!password) throw new Error("empty password"); } ``` |
| script | SCR: New file `src/login.ts` — paste the stub from the example. New file `reqs/auth.rq` — type `login_api` block with file reference `Implementation: login.ts` and link to `password_rules`. VO: Requirements earn their keep when they touch reality. Point an idea at a file with a file reference — the path lives in brackets like any other link. SCR: Ctrl/Cmd-click `login.ts` inside `login_api` — land in `login.ts`. Brief pause on the opened tab. VO: Same navigation habit as idea links — the graph knows about workspace files, not only `.rq` sources. SCR: Sticky: "File refs only go one way?" Place caret inside `login.ts` on the empty-password guard. Open activity bar — show requirements referencing this file or neighbourhood reacting to non-`.rq` focus. VO: Context scope works on any workspace file, not only `.rq` sources. Stand in the implementation and related requirements should still surface — the reverse path. SCR: Optional five seconds: mention folder references like `interviews` on a slide — do not create live. VO: Folder references work the same way when assets span a directory. SCR: Recap montage (five seconds): seven episode titles stacked — Why · First idea · Link · Base · Activity bar · Ask · Point at code. VO: You now have the get-started loop: name ideas, link them, create a base, inspect the neighbourhood, ask the tools with a small slice, and stitch requirements to code. VO: Try this before you go: link one more source file your welcome flow actually depends on — a component, route, or test. SCR: End card: "Concepts · The building blocks, the extension map, then the CLI" — series handoff to concepts_series. |
| slides | { id title transition fade background brand-dark kicker Get started · 07 heading Point ideas at code asset logo notes Requirements earn their keep when they touch reality. }, { id create-files transition fade background brand-panel heading Create auth.rq and login.ts body reqs/auth.rq + src/login.ts stub — small and readable. notes Keep the demo tree minimal; one API idea and one implementation file. }, { id file-ref transition none background brand-panel heading File references asset file-link code_lang rq code Implementation: login.ts notes The path lives in brackets like any other link. Ctrl/Cmd-click to open. }, { id link-idea transition fade background brand-panel heading Link back to requirements code_lang rq code Rejects empty passwords per password_rules. notes Ideas and files share one graph — cross-link freely. }, { id reverse transition fade background brand-panel heading Stand in the implementation body Caret in login.ts. Activity bar shows related requirements. asset activity-bar notes Context scope works on any workspace file, not only .rq sources. }, { id misconception transition none background brand-contrast heading Not a one-way arrow body File refs from requirements. Scope from code back to requirements. notes The reverse path is the point — traceability in both directions. }, { id recap transition slide background brand-panel heading Get-started loop complete body Name · link · base · neighbourhood · small AI slice · stitch to code. notes Seven episodes — same discipline throughout. }, { id try-this transition fade background brand-dark heading Try this body Link one more source file your welcome flow depends on. fragments Concepts series next — name the building blocks notes When you are ready to put names to what you did, Concepts starts there. }, { id end transition fade background brand-dark heading Concepts next body The building blocks, the extension map, then the CLI. asset logo notes Next: names for the building blocks you just used. } |
Ancestor context
No ancestor chain recorded.
| Kind | Idea | Path | Snippet |
|---|---|---|---|
| file_reference | ./src/login.ts | reqlan rq/marketing_and_media/src/login.ts | login.ts |
| Kind | Idea | Path | Snippet |
|---|---|---|---|
| ideaset_member | get_started_series | reqlan rq/marketing_and_media/tutorials.rq | — |
| ideaset_member | slide_decks | reqlan rq/marketing_and_media/tutorials.rq | — |
| Kind | Idea | Path | Snippet |
|---|---|---|---|
| references | any_file_scope | any_file_scope | |
| references | concepts_series | concepts_series | |
| references | context_scope | context_scope | |
| references | file | file | |
| references | password_rules | password_rules | |
| references | reference | reference | |
| references | referenced_files | referenced_files |
Initialising graph…