Tutorials

Why requirements as codeName the problem: chat dumps vs a graph of ideas.
Your first ideaOne-liners and blocks in a .rq file.
Link ideasBracket references and wikilinks — navigate a graph, not a scroll.
Your first baseCreate .reqlan — the boundary of one ideas graph.
Neighbourhood in the activity barLocal context in the active base, sync, hop depth, and copy-as-markdown.
Ask @reqlanFocused search and scoped AI context — not the whole graph in the prompt.
Point ideas at codeFile references and reverse context from source.
The ontologyName the nouns: idea, ideaset, file, base, reference, attribute, map.
Extension tourFive surfaces — one job each. A map, not a laundry list.
CLISame graph API — terminal, scripts, and CI on the shared .reqlan index.
Beyond one fileEight craft themes: imports, attributes, maps, tokens, comments, export, CLI/MCP, patterns.
Imports and ideasetsSplit ideas across files; from-import, namespace import, and ideasets.
Attributes without bloatOpt into status, tags, and plans — slim keys that drive a view.
Maps you chooseIdeas Summary as a cartographic cut — filter, focus, deepen on purpose.
Context and tokensCompose a neighbourhood slice. Do not paste the whole project by habit.
Comment referencesPoint code back at requirements with rq:[…] — same graph, other door.
Export the graph as HTMLStatic multi-page site from the same ideas — for reviews and stakeholders.
CLI and MCPSame graph API — terminal, CI, agents, and the editor.
Patterns that age wellDurable habits plus a non-software vignette — judgement over more syntax.
AssessmentPass the quiz, get a certificate