Control system sequencing
Interlock and phase logic expressed as requirements — semantics, not just ladder rungs.
View showcaseTyped examples of reqlan in real workflows — short summaries here, full requirement snippets on each page.
Interlock and phase logic expressed as requirements — semantics, not just ladder rungs.
View showcaseRequirements that explain how one file relates to another without importing implementation details.
View showcaseA boundary file that links modules without pulling in their internals.
View showcasePlans and build steps linked back to requirements the agent should satisfy.
View showcaseTrace controls to standards and show coverage in the graph.
View showcaseHardcoded doc strings across the repo, unified by semantic search and refs.
View showcaseStatus and file refs show what is done, in progress, or missing.
View showcaseTests linked to what they prove — semantics above assertion strings.
View showcaseCustom @fields carry domain metadata without changing core syntax.
View showcaseConnect dependent but unrelated systems — firmware timing and backend SLA.
View showcaseCatch an idea in context and route it into tracked work.
View showcaseLink requirements to markdown or exported HTML wiki pages.
View showcaseDon't store records, config values, or inventories in .rq — point at the source of truth.
View showcaseExplore the requirement graph visually — filter, scope, export.
View showcase