Idea detail
con_01_ontology
reqlan rq/marketing_and_media/tutorials.rq:1087
block
Summary
Audience: viewers who finished get-started ( or equivalent ) and want shared vocabulary without repeating the install loop.
Outcome: define each core ontology noun in one sentence; place base as graph boundary ( including nesting ); distinguish attribute_body from optional `@` metadata; name cartographic_map as a chosen cut, not a mandatory dump.
Runtime: 10 – 12 min.
Demo: `reqlan-tutorials-demo` at get-started end state — `.reqlan/` present; `reqs/product.rq`, `reqs/auth.rq`, `src/login.ts`; caret starts on `welcome_flow` in `product.rq`.
Related: idea ideaset file base base_detail reference attribute attribute_body cartographic_map referenced_files configuration base_nesting multi_base_environment
Attributes
| Key | Value |
|---|---|
| example | ```rq // reqs/auth.rq — one noun per beat in the recording fixture auth_core ( login_api, session_policy ) login_api { POST /login validates credentials and starts a session. Implementation: login.ts Bound by session_policy and password_rules. @status in-progress @tags ( auth ) } session_policy { Sessions expire after thirty minutes of inactivity. } ``` |
| script | SCR: Title card — Concepts · 01 · The building blocks. Brand palette. Quiet list of seven names fades in one at a time. VO: You already wrote ideas, linked them, created a base, inspected the neighbourhood, and asked the tools. Now let's put names to the things you used, so you and your teammates talk about them the same way. One name per beat. SCR: Open `reqs/product.rq`. Highlight `welcome_flow` one-liner and block side by side. VO: First: the idea. An idea is a named handle plus prose — one thing you care about. A one-liner is already an idea. A block gives the body more room. You do not type `@body` — the first unmarked prose inside a block simply is the body. SCR: Open `reqs/auth.rq`. Soft zoom on the auth_core ideaset paren list. VO: Next: the ideaset. An ideaset groups idea names inside parentheses. It lists membership — a light way to say "these belong together", not a second syntax to learn. SCR: Explorer: click `auth.rq` in the tree. Brief file-tab chrome — path visible, ideas inside. VO: Next: the file. A `.rq` file holds ideas and is itself a group of them — the file is part of the graph, not just a spot on disk. When imports arrive in Advanced, files stay clear about where each name lives. SCR: Explorer: expand `.reqlan/`. Whiteboard overlay or dashed box: `project/.reqlan/` vs `packages/lib/.reqlan/` — do not live-switch repos on camera. VO: Next: the base. A base is the boundary of one graph of ideas. A folder is a base only when it owns a `.reqlan` folder. Nested bases are separate graphs; the parent index stops at the child boundary. Day-to-day you work in one active base — nested trees are for larger projects, not day-two homework. SCR: Split editor: bracket link `session_policy` beside file reference `login.ts`. Optional three-second flash of `// rq:password_rules` in `login.ts` — no deep dive. VO: Next: the reference. A reference links an idea to another idea, a file, a folder, or a symbol. Square brackets are the same habit you already used in get-started. A non-`.rq` file you point at still shows up in the index — a neighbour, not an orphan. SCR: Cursor on `@status` and `@tags` inside `login_api`. Do not open settings panels. VO: Next: the attribute. Attributes are optional metadata you opt into — status, tags, plans, your own keys. They are not the main prose. And one thing to keep straight: `.reqlan/config.json` is not the same place as your editor settings — graph memory and editor preferences live apart. SCR: Ideas Summary → Graph tab, already centred on `welcome_flow` with hop depth 1. Pan once; close. VO: Last: the map. Ideas Summary shows a focused map view of the graph — filtered, centred, depth-limited — built around the question you have right now. It is not a picture of everything at once. Advanced goes deeper on map craft. SCR: New scratch file `reqs/scrap-ontology.rq` — type seven one-line definitions live. VO: Try this: on a scrap page, write one sentence for each name — idea, ideaset, file, base, reference, attribute, and map. Use your own words; if a sentence needs a second clause, the idea is still fuzzy. SCR: End card — "Next: where these live in the extension." Logo + site link from phonebook. VO: Next episode shows where each of these appears across the extension. |
| slides | { id title transition fade background brand-dark kicker Concepts · 01 heading The building blocks body Names for the things you already used — one per beat. asset logo notes Now let's name the things you used, so you and your teammates talk about them the same way. }, { id idea transition none background brand-panel heading Idea body Named handle plus prose. One-liner or block — both are ideas. code_lang rq code welcome_flow { New users land on a welcome screen… } notes The first free text is the body attribute. You do not type @body. }, { id ideaset transition fade background brand-panel heading Ideaset body Parentheses group names into a namespace container. code_lang rq code auth_core ( login_api, session_policy ) notes A lightweight module boundary — not a second syntax world. }, { id file transition fade background brand-panel heading File body A .rq file stores ideas and implicitly forms an ideaset. code_lang txt code reqs/auth.rq → login_api · session_policy · auth_core notes The file is part of the ontology, not merely a disk path. }, { id base transition none background brand-panel heading Base body Graph boundary. Owns .reqlan. Nested bases are separate graphs. code_lang txt code reqlan-tutorials-demo/.reqlan/ · packages/lib/.reqlan/ notes Day-to-day you live in one active base. Parent index stops at child boundary. }, { id reference transition fade background brand-panel heading Reference body Links ideas, files, folders, and symbols. Non-.rq files stay in the index. code_lang rq code Bound by session_policy · Implementation: login.ts notes Square brackets are the habit you already felt in get-started. }, { id attribute transition fade background brand-panel heading Attribute body Optional @ metadata you opt into — not the main prose. code_lang rq code @status in-progress · @tags ( auth ) notes Base config and extension settings are different scopes — do not conflate them. }, { id map transition fade background brand-panel heading The map body A focused map view — filtered, centred, depth-limited. asset montage-ide notes A view you build around one question. Advanced goes deeper on map craft. }, { id try-this transition fade background brand-dark heading Try this body On scrap-ontology.rq, one sentence per name — in your own words. fragments Next — Extension tour notes If a sentence needs a second clause, the idea is still fuzzy. } |
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 | concepts_series | reqlan rq/marketing_and_media/tutorials.rq | — |
| ideaset_member | slide_decks | reqlan rq/marketing_and_media/tutorials.rq | — |
| references | concepts_series_brief | reqlan rq/marketing_and_media/tutorials.rq | con_01_ontology |
| Kind | Idea | Path | Snippet |
|---|---|---|---|
| references | attribute | attribute | |
| references | attribute_body | attribute_body | |
| references | base | base | |
| references | base_detail | base_detail | |
| references | base_nesting | base_nesting | |
| references | cartographic_map | cartographic_map | |
| references | configuration | configuration | |
| references | file | file | |
| references | idea | idea | |
| references | ideaset | ideaset | |
| references | multi_base_environment | multi_base_environment | |
| references | phonebook | phonebook | |
| references | reference | reference | |
| references | referenced_files | referenced_files | |
| references | session_policy | session_policy |
Initialising graph…